Do not configure bgp l3 on BGWs - #158
Merged
Merged
Conversation
On BGWs we already skip SVI creation (by passing is_bgw=True to add_binding_host_to_config(), but we also don't want to advertise the l3 networks from there. Therefore we skip the gateway config alltogether and with that also ignore the bgp vrf network/aggregate config.
toanju
approved these changes
Aug 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
On BGWs we already skip SVI creation (by passing is_bgw=True to add_binding_host_to_config(), but we also don't want to advertise the l3 networks from there. Therefore we skip the gateway config alltogether and with that also ignore the bgp vrf network/aggregate config.