-
Notifications
You must be signed in to change notification settings - Fork 3.4k
egressgw: set ifindex for egress interface in IPv6 policy entry #38961
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
Conversation
17c3535
to
f60e8df
Compare
This pull request has been automatically marked as stale because it |
f60e8df
to
a670b80
Compare
/test |
(it's too late to do this for IPv4 unfortunately, without adding a new map entry format. I'll add a follow-up issue in case anyone is interested in implementing those bits.) |
a670b80
to
9bb9095
Compare
/test |
Looks like the changes ran into the complexity issue. Holding off the review for now
|
Enable the EGW datapath on the gateway node to obtain the ifindex of the egress interface from the EGW policy entry, instead of needing a FIB lookup. We can make this change for IPv6 as the policy entry format is not fix yet - IPv4 will require a v2 of the map. No change in behavior, as the agent still pushes down 0 as the ifindex value (see the change in updateEgressRules6()). The needed controlplane changes follow in a subsequent patch. Signed-off-by: Julian Wiedmann <jwi@isovalent.com>
For CEGPs that select the egress interface by name (`interface` parameter) or by default-route, also push the interface ifindex down into the datapath. This avoids custom routing setup for forwarding EGW traffic to the correct network interface. Signed-off-by: Julian Wiedmann <jwi@isovalent.com>
9bb9095
to
66e5f88
Compare
Pull request was converted to draft
This pull request has been automatically marked as stale because it |
This pull request has not seen any activity since it was marked stale. |
While we can still touch the IPv6 policy entry format without worrying about compatibility, take the opportunity to add support for pushing down the ifindex of the egress interface (#36151).
This avoids the usability annoyance of adding custom routes on the gateway node, as described in #30488.