[prev in list] [next in list] [prev in thread] [next in thread] 

List:       quagga-users
Subject:    [quagga-users 14408] bgpd Failing to Advertise IPv6 Prefix w/1.0.20160315
From:       Mark Kamichoff <prox () prolixium ! com>
Date:       2016-08-30 6:49:14
Message-ID: 20160830064914.GA1618 () prolixium ! com
[Download RAW message or body]

Hi - 

I'm seeing some weird behavior in Quagga's bgpd related to local route
advertisements for some IPv6 prefixes, specifically with 1.0.20160315-1.

For example, I'm attempting to advertise a prefix that's bound to a
local bridge interface to an IBGP peer via a network statement.  Some
show commands in bgpd indicate it's being advertised, but it never gets
sent to the peer.

Zebra sees the connected route fine:

(trident:23:28:PDT)% sudo vtysh -c "show ipv6 route 2620:6:200f:1::/64" -d zebra
Routing entry for 2620:6:200f:1::/64                                            
  Known via "connected", distance 0, metric 0, vrf 0, best, fib
  * directly connected, lxcbr0

(trident:23:28:PDT)% 

I put it in my config (some context shown):

router bgp 395460
 bgp router-id 10.3.4.68
 bgp bestpath as-path multipath-relax
 timers bgp 4 12
 neighbor 2620:6:2000:104::46 remote-as 395460
 neighbor 2620:6:2000:104::46 description bazooka.prolixium.com.
 neighbor 2620:6:2000:104::46 update-source 2620:6:2000:104::47
 no neighbor 2620:6:2000:104::46 activate
!
 address-family ipv6
 network 2620:6:200f:1::/64 <---------------- added this
 neighbor 2620:6:2000:104::46 activate
 neighbor 2620:6:2000:104::46 next-hop-self
 neighbor 2620:6:2000:104::46 soft-reconfiguration inbound
 exit-address-family
 exit
!

I verify that bgpd should be sending the route:

(trident:23:30:PDT)% sudo vtysh -c "show ipv6 bgp 2620:6:200f:1::/64" -d bgpd       
BGP routing table entry for 2620:6:200f:1::/64
Paths: (1 available, best #1, table Default-IP-Routing-Table)
  Advertised to non peer-group peers:
  2620:6:2000:104::46 2620:6:2000:ffff::5e
  Local
    :: from :: (10.3.4.68)
      Origin IGP, metric 0, localpref 100, weight 32768, valid, sourced, local, best
      Last update: Mon Aug 29 23:23:34 2016

(trident:23:30:PDT)% 

But it never gets sent:

(trident:23:30:PDT)% sudo vtysh -c "show bgp nei 2620:6:2000:104::46 \
advertised-routes"|grep 2620:6:200f:1::/64 (trident:23:31:PDT)% 

Debugging bgpd with all the flags doesn't show any matches for
2620:6:200f:1::/64 when I hard clear the peer.  Restarting bgpd doesn't
help things.

I've run tcpdump and don't see this prefix on the wire to the
2620:6:2000:104::46 peer.

In the past I've seen issues like this with Quagga and had to add an
"override-capability" flag for the peer when dealing with IPv6.
However, this doesn't seem to do the trick anymore.

Now.. the fun part is this works fine if I downgrade to 0.99.23.1-1:

(trident:23:41:PDT)% sudo vtysh -c "show bgp nei 2620:6:2000:104::46 \
                advertised-routes"|grep 2620:6:200f:1::/64
*> 2620:6:200f:1::/64
(trident:23:41:PDT)% 

Thoughts?  Bug?

- Mark

-- 
Mark Kamichoff
prox@prolixium.com
http://www.prolixium.com/

_______________________________________________
Quagga-users mailing list
Quagga-users@lists.quagga.net
https://lists.quagga.net/mailman/listinfo/quagga-users


[prev in list] [next in list] [prev in thread] [next in thread]