VxLAN kernel routes for VNET_ROUTE_TUNNEL #2092
Open
Conversation
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
bveerannamsft
commented
Oct 30, 2025
bveerannamsft
commented
- This PR proposes a design to add kernel routes for the prefixes defined in VNET_ROUTE_TUNNEL
- These kernel routes are required for any CPU originated/destined packets
- This is an enhancement to the VxLAN HLD
Collaborator
|
/azp run |
|
No pipelines are associated with this pull request. |
bveerannamsft
force-pushed
the
vxlan_routes_hld
branch
from
878dfe9 to
c2c6401
Compare
Collaborator
|
/azp run |
|
No pipelines are associated with this pull request. |
Collaborator
|
/azp run |
|
No pipelines are associated with this pull request. |
prsunny
reviewed
Nov 24, 2025
| # 1 Revision | ||
| | Rev | Date | Author | Change Description | | ||
| |:---:|:-----------:|:------------------:|-----------------------------------| | ||
| | 0.1 | | Bharath Veeranna | Initial version | |
|
|
||
| However, the VM having IP 20.0.0.3 is behind a VTEP 200.200.200.3 having VNI 2000. SONiC does not have any kernel routes and interfaces configured for VNI 2000. Any traffic destined to 20.0.0.3 will be dropped in the kernel since there are no routes or interfaces configured for VxLAN 2000. | ||
|
|
||
| Moreover, if the CPU port is set to Egress mode in the NPU, the packets sent from the CPU are directed to the egress pipeline. Hence, the kernel has to form the packets with appropriate VxLAN headers before placing the packet in the egress pipeline. To encap the packets with VxLAN headers, the kernel should have the VxLAN interface and routes configured. |
Contributor
There was a problem hiding this comment.
please remove this section about CPU port in 'egress mode'. This can be confusing and deviating the original intent. The line above is sufficient
|
|
||
| The diagram below shows the flow for the route creation: | ||
|
|
||
|  |
Contributor
There was a problem hiding this comment.
I cannot see the diagram. As discussed, could you please provide a highlevel flow diagram
| ## 7.3 Config Manager | ||
| A new config manager called VnetMgr will be added which will handle kernel routes programming for `VNET_ROUTE_TUNNEL`. | ||
|
|
||
| ### VnetMgr |
Contributor
There was a problem hiding this comment.
Please add a section for VnetOrch and capture what changes would be needed or removed by having VnetMgr
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.