This repository was archived by the owner on Mar 16, 2026. It is now read-only.
Firewall should not enforce first as for the underlay#120
Open
majst01 wants to merge 1 commit into
Open
Conversation
This was referenced Jan 23, 2025
Contributor
Author
|
Similar frr issue: FRRouting/frr#16095 |
mwennrich
approved these changes
Jan 24, 2025
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 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.
Description
It turns out that adding
no bgp enforce-first-asto the VRF BGP Instances is not enough to create a stable working firewall upon first start, it still requires afrr reloadsometimes. We observed that after the reload, this entry was added to the underlay section as well. So do this always.