[VRF] Set unreachable default route to isolate user Vrf and default Vrf #2943
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
In cases where there is no next hop found in the user VRF in the software dataplane, the default behavior of the kernel switches to looking up the default VRF. This behavior is inconsistent with some ASICs. To address this, we need to set an unreachable policy-based route to prevent this scenario: ip route add table 10 unreachable default metric 4278198272 This commit will append this configuration during VRF creation and removal."
gord1306
force-pushed
the
isolation_vrf
branch
from
2290cec to
d38299a
Compare
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.
What I did
Set unreachable default route to isolate user Vrf and default Vrf
Why I did it
In cases where there is no next hop found in the user VRF in the software dataplane, the default behavior of the kernel switches to looking up the default VRF. This behavior is inconsistent with some ASICs.
How I verified it
Details if related
To address this, we need to set an unreachable policy-based route to prevent this scenario ref:
ip route add table 10 unreachable default metric 4278198272