Le 06/07/2015 09:50, Martin Winter a écrit :
It seems we have a bad commit in git master.Commit c99f348 “*: add VRF ID in the API message header” is the bad commit. It seems (at least) direct connected next hops in received BGP routes show up as inaccessible with “ebgp-multihop” configured. (It works without the ebgp-multihop) (in this example: 172.16.1.0/24, which is announced from the directly connected BGP neighbor with a connected next hop of 192.168.1.1) dut# show ip bgp BGP table version is 0, local router ID is 192.168.1.101 Status codes: s suppressed, d damped, h history, * valid, > best, = multipath, i internal, r RIB-failure, S Stale, R Removed Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path * 172.16.1.0/24 192.168.1.1 0 0 501 i *> 192.168.1.0 0.0.0.0 0 32768 i Total number of prefixes 2 dut# show ip bgp 172.16.1.0/24 BGP routing table entry for 172.16.1.0/24 Paths: (1 available, no best path) Not advertised to any peer 501 192.168.1.1 (inaccessible) from 192.168.1.1 (192.168.1.1) Origin IGP, metric 0, localpref 100, valid, external Last update: Sun Jul 5 21:47:03 2015 dut# show ip route 192.168.1.1 Routing entry for 192.168.1.0/24 Known via "connected", distance 0, metric 0, vrf 0, best * directly connected, eth1 Here is how the issue can be reproduced:
I've reproduced the issue. I'm investigating. Note that if I start bgpd before zebra, there is no issue. Regards, Nicolas _______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
