I have set up BGP on two routers using qugga. When I down the interface that holds the IP block that I am advertising zerba removes the route from its table but bgpd keeps advertising it. I can see that it is still advertised via the neighboring BGP tables as well as the
show ip bgp nei 172.16.14.1 ad command from the router that is doing the advertising. This interface holds the full route that is being advertised so there is no aggregation.
As anyone run into this before ... it seems to fundamentally break the main functionality of a routing protocol...
So in the router I have the following for a BGP table.
so-rt1# show ip bgp BGP table version is 0, local router ID is 172.16.14.1 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, r RIB-failure, S Stale, R Removed Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path *> 0.0.0.0 126.96.36.199 200 0 5555 i * 188.8.131.52/24 172.16.14.2 0 100 0 i *> 0.0.0.0 0 32768 i Total number of prefixes 2
For the 184.108.40.206/24 network, which I announce, the directly connect route (the last entry) is the route that is preferred. If I shutdown the interface that holds 220.127.116.11/24 not only is the directly connected route not removed from the BGP table, it is still the preferred route. So after shutting down that interface, the BGP table stays exactly the same.
Zebra is aware that the directly connected 18.104.22.168/24 route is no longer there. I see it with
show ip route while the interface is up and the entry is gone when I shut it down. So the problem I think is that the BGP table is somehow not getting the updates I believe it should from zebra.