When the router is restarted for an image update the BGP daemon leaks routes. The configured prefix list does not take effect immediately and leaks prefixes that it receives from one peer to other peers without filtering based on the prefix list that is set. This probably happens because the BGP daemon starts before the configuration is fully loaded. If you have many BGP peers and in general a big configuration the configuration load on startup can take a significant time (3 minutes). During this time the BGP daemon is already started and it seems to ignore the prefix list until the configuration is fully loaded. This behavior exists since vyatta (I reported this also to vyatta at that time). I am not sure if this happens at every reboot or only on reboot after image update because usually I only reboot for an update. Someone who knows how the configuration is loaded (on normal reboot and on a reboot after update) may know this. I guess a solution would be to start the BGP process only after the configuration is fully loaded. This may also fix https://phabricator.vyos.net/T2003
Description
Description
Details
Details
- Version
- 1.2.6
- Is it a breaking change?
- Unspecified (possibly destroys the router)
Related Objects
Related Objects
Event Timeline
Comment Actions
This has come up multiple times before, see https://phabricator.vyos.net/T1698 for the solution.
Comment Actions
@Robot82
It will be by default in the new BGP implementation.
https://github.com/vyos/vyos-1x/blob/current/data/templates/frr/bgp.frr.tmpl#L5