-
Notifications
You must be signed in to change notification settings - Fork 338
vpp: Handle routes using link local nexthop #1680
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
base: master
Are you sure you want to change the base?
Conversation
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
dypet
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
hi @saiarcot895 , please help with review and merge. thanks! |
|
/azp run |
|
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command. |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azpw run |
|
/AzurePipelines run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azpw run |
|
/AzurePipelines run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
hi @saiarcot895 , the PR has been approved. Please take another look and help with merge. |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
why
When we add a route, the current code doesn't provide interface to vl_api_ip_route_add_del but only provides nexthop address. It works with if the nexthop address is unique. However, in link-local case, the nexthop address is not unique and only valid with the egress interface. vpp fails to find the correct nexthop and interface.
what this PR does
SAI provides SAI_NEXT_HOP_ATTR_ROUTER_INTERFACE_ID. We can get the egress interface from this attribute and provide it to vpp in the vl_api_ip_route_add_del. This removes the ambiguity in the link-local case.