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

Forwarding policy #228

Closed
orion-belt opened this issue Mar 22, 2022 · 3 comments
Closed

Forwarding policy #228

orion-belt opened this issue Mar 22, 2022 · 3 comments

Comments

@orion-belt
Copy link

https://github.com/travelping/upg-vpp/blob/master/upf/upf_forward.c#L250

Here we already have fib index so ip look up is not required and you can directly send to rewrite node.

vnet_buffer (b)->sw_if_index[VLIB_TX] =
	rpath->frp_fib_index;
next = UPF_FORWARD_NEXT_IP_LOOKUP;

I tried similar approach and it worked.

@sergeymatov
Copy link
Contributor

Direct jump to ip-rewrite chain won't fit the approach if we have dynamic table of custom routes and there is a need to perform a lookup for some particular traffic. In other words - there is a need to do a lookup in our use case

@sergeymatov
Copy link
Contributor

There is a possibility to perform different lookup (like VPP FIB is already doing) based on route path type. Dedicated node and required operations for ip.adj or VLIB_TX can be done in respect to route path containing in the policy.
Later we will do this

@orion-belt
Copy link
Author

Thanks a lot @sergeymatov for you information.
Mapping to ip_adj during pre-configuration of policy, will avoids look up for every packet.

LBO

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

No branches or pull requests

2 participants