zebra: Add an explicit warning/notice when noprefixroute flag is used
#16288
Conversation
This file contains 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
Since 10.0 release we ignore the routes to be installed into the RIB with `noprefixroute` flag. That causes routes to be resolved via the wrong interfaces. Especially if resolve via default route is enabled (enabled by default since 10.0). NetworkManager is the one network manager that causes this issue and we need to say it loudly when the prefix is not installed and why. Signed-off-by: Donatas Abraitis <[email protected]>
|
@Mergifyio backport dev/10.1 stable/10.0 |
🟠 Waiting for conditions to match
|
|
I'm about 75% of the way through a fix for this problem. Can we hold off on this? |
donaldsharp
requested changes
Jul 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #16101