Repository navigation
Fix next-hop encap action in VXLAN - #770
Merged
Merged
Conversation
hardikharti
force-pushed
the
vxlan-encap-fix
branch
2 times, most recently
from
October 22, 2026 23:15
e8a8e8b to
18bcd11
Compare
Contributor
|
Can you pls add in description on how and what was tested on this PR? |
hardikharti
force-pushed
the
vxlan-encap-fix
branch
from
October 23, 2026 18:20
18bcd11 to
396bc3a
Compare
sonikajindal
approved these changes
Oct 23, 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
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.
Fix VXLAN next-hop encap actions and tunnel TTL modes in saiserver.
Also fixed a bug to copy the TTL from the inner IP header for the outer header
Testing: These fixes are for header correction during encapsulation. They are covered by unit tests.
Full end-to-end testing details will be added once the decap fix PR is raised.
Sanity tests passed successfully.