Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update rt_netlink.c - END.DT6 SEG6_LOCAL_VRFTABLE #17977

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

zhutang
Copy link

@zhutang zhutang commented Feb 2, 2025

END.DT6 should use SEG6_LOCAL_VRFTABLE, not SEG6_LOCAL_TABLE

END.DT6 should use SEG6_LOCAL_VRFTABLE, not SEG6_LOCAL_TABLE

Signed-off-by: zhutang <[email protected]>
Copy link
Contributor

@cscarpitta cscarpitta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please provide more information.

What is the reason behind this change? What are you trying to achieve here? If you are trying to fix an issue, what is the issue?

@zhutang
Copy link
Author

zhutang commented Feb 4, 2025

Please provide more information.

What is the reason behind this change? What are you trying to achieve here? If you are trying to fix an issue, what is the issue?

yes, I am trying to fix an issue.

based on [iproute2-next v1 1/1] seg6: add support for vrftable attribute in End.DT4/DT6 behaviors, and seg6: add support for the SRv6 End.DT4 behavior, I think End.DT4/DT6 leverages a VRF device in order to force the routing
lookup into the associated routing table using the "vrftable" attribute, so End.DT6 should use SEG6_LOCAL_VRFTABLE in netlink msg to kernel, not SEG6_LOCAL_TABLE.

however, topotest bgp_srv6l3vpn_to_bgp_vrf failed after rt_netlink.c is changed, I am checking the reason of this fail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants