mirror of
https://git.proxmox.com/git/mirror_frr
synced 2025-07-06 02:05:55 +00:00
3fdb2079f6
The flag for telling BGP that a route is expected to be installed first before notifying a peer was always being set upon receipt of a path that could be accepted as bestpath. This is not correct: imagine that you have a peer sending you a route and you have a network statement that covers the same route. Irrelevant if the network statement would win the flag on the dest was being set in bgp_update. Thus you could get into a situation where the network statement path wins but since the flag is set on the node, it will never be announced to a peer. Let's just move the setting of the flag into bgp_zebra_announce and _withdraw. In _announce set the flag to TRUE when suppress-fib is enabled. In _withdraw just always unset the flag as that a withdrawal does not need to wait for rib removal before announcing. This will cover the case when a network statement is added after the route has been learned from a peer. Signed-off-by: Donald Sharp <sharpd@nvidia.com> |
||
|---|---|---|
| .. | ||
| r1 | ||
| r2 | ||
| r3 | ||
| test_bgp_suppress_fib.py | ||