Hi Satya,
A node on ip4-local will process packets which have a destination IPv4
address that is local to VPP. Usually these are addresses configured on a
VPP interface but they can also be addresses in a NAT pool or any other
address which has a local path in the FIB. If those are the only packets
you want your node to process, then ip4-local should work. Otherwise, if
you want to process packets which VPP will forward elsewhere, you might
want to use the ip4-unicast arc and set runs_after to
"ip4-full-reassembly-feature".
-Matt
On Wed, Aug 12, 2020 at 6:16 AM Satya Murthy <satyamurthy1...@gmail.com>
wrote:
> Hi,
>
> We have a query on one of the requirements we have.
>
> 1. We would like to tap all the ip4 packets into our custom graph node.
> 2. But, we want to tap the ip packets only after reassembly is completed,
> if fragments are received.
>
> I was looking at ip-local feature arc, if this works for our requirement
> or not. But, I am not 100% sure, if the reassembly restriction will be met
> by registering our feature in ip4-local feature arc as below.
>
> VNET_FEATURE_INIT (our_custom_feature, static) =
> {
> .arc_name = "ip4-local",
> .node_name = "our-custom-node",
> .runs_before = VNET_FEATURES("ip4-local-end-of-arc"),
> };
>
> If this does not work, can you please let us know any pointers on how to
> achieve this.
>
> Thanks & Regards,
> Murthy
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17211): https://lists.fd.io/g/vpp-dev/message/17211
Mute This Topic: https://lists.fd.io/mt/76144894/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
