> And you might not want to enable reassembly in the input feature arc, unless
> you want every fragment arriving on that interface to be reassembled.
> Independently of packet being to your feature plugin or not.
>
> Hi Ole, yes we are checking for ip fragmented packet in our plugin and if
>
On Thu, Jun 6, 2019 at 09:06 AM, Ole Troan wrote:
>
> And you might not want to enable reassembly in the input feature arc,
> unless you want every fragment arriving on that interface to be
> reassembled. Independently of packet being to your feature plugin or not.
>
>
Hi Ole, yes we are check
Yes, that’s one way to do it... See also Ole’s comment... D.
From: vpp-dev@lists.fd.io On Behalf Of
prashan...@gmail.com
Sent: Thursday, June 6, 2019 12:22 PM
To: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] undefined symbol: ip4_reass_node
Thanks a lot Dave and Ole for your reply.
I am new to
Thanks a lot Dave and Ole for your reply.
I am new to VPP framework using VPP version 18.04, Yes I need to send all ip
fragments to ip4 reassembly node.
As you suggested.
> for asking the framework for a static and/or dynamic graph arc from
> to “ip4-reassembly”.
Does that mean adding ip4_rea
lists.fd.io On Behalf Of
> prashan...@gmail.com
> Sent: Thursday, June 6, 2019 11:51 AM
> To: vpp-dev@lists.fd.io
> Subject: [vpp-dev] undefined symbol: ip4_reass_node
>
> I am trying to use ip4_reass_node
> for that
> static vlib_node_registration_t ip4_reass_node;
> changed
, June 6, 2019 11:51 AM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] undefined symbol: ip4_reass_node
I am trying to use ip4_reass_node
for that
static vlib_node_registration_t ip4_reass_node;
changed to
extern vlib_node_registration_t ip4_reass_node;
Also
VLIB_REGISTER_NODE (ip4_reass_node, static
I am trying to use ip4_reass_node
for that
static vlib_node_registration_t ip4_reass_node;
changed to
extern vlib_node_registration_t ip4_reass_node;
Also
VLIB_REGISTER_NODE (ip4_reass_node, static) = {
to
VLIB_REGISTER_NODE (ip4_reass_node) = {
Also
Enabled the feature on interface
ret = vnet_fe