From: Daniel Walton <[email protected]> back to back route refreshes can set BGP_INFO_ATTR_CHANGED on the first route refresh but then clear it on the second
Signed-off-by: Daniel Walton <[email protected]> --- bgpd/bgp_route.c | 4 ---- 1 file changed, 4 deletions(-) diff --git a/bgpd/bgp_route.c b/bgpd/bgp_route.c index ab81b72..cebf1a7 100644 --- a/bgpd/bgp_route.c +++ b/bgpd/bgp_route.c @@ -2181,8 +2181,6 @@ bgp_update_rsclient (struct peer *rsclient, afi_t afi, safi_t safi, && attrhash_cmp (ri->attr, attr_new)) { - bgp_info_unset_flag (rn, ri, BGP_INFO_ATTR_CHANGED); - if (bgp_debug_update(peer, p, 1)) zlog_debug ("%s rcvd %s/%d for RS-client %s...duplicate ignored", peer->host, @@ -2420,8 +2418,6 @@ bgp_update_main (struct peer *peer, struct prefix *p, struct attr *attr, if (!CHECK_FLAG (ri->flags, BGP_INFO_REMOVED) && attrhash_cmp (ri->attr, attr_new)) { - bgp_info_unset_flag (rn, ri, BGP_INFO_ATTR_CHANGED); - if (CHECK_FLAG (bgp->af_flags[afi][safi], BGP_CONFIG_DAMPENING) && peer->sort == BGP_PEER_EBGP && CHECK_FLAG (ri->flags, BGP_INFO_HISTORY)) -- 1.9.1 _______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
