I responsed earlier!
Hi,
Why can't you just add your plugin to run after ethernet-input and enable it on
all physical interfaces so that you can avoid spanning.
For your approach, are you sure you added your node to run after span-input and
correctly placed on a feature-arc?pls run "show vlib
> On 19 Nov 2019, at 08:36, Muthukumar Sivaperumal
> wrote:
>
> Hi Team,
>
> We are trying to implement a plugin to process all packets on virtual
> interface.
> We are doing span from physical interface to virtual interface on vpp,by
> running plugin arc node with
Hi Team,
We are trying to implement a plugin to process all packets on virtual
interface.
We are doing span from physical interface to virtual interface on vpp,by
running plugin arc node with interface-output.
We are facing some problems.
Could you please help us to resolve the issue by
Why can't you just add your plugin to run after ethernet-input and enable it
on all physical interfaces so that you can avoid spanning.
For your approach, are you sure you added your node to run after span-input and
correctly placed on a feature-arc?pls run "show vlib graph" it will tell you
Sivaperumal ;
vpp-dev@lists.fd.io
Subject: RE: [vpp-dev] VPP New plugin intergation
Does “show interface VirtualEthernet0/0/0 features” show your output feature?
You might try “trace add dpdk-input 10” and “show trace” to see what’s
happening to packet received on GigabitEthernet0/8/0
...@veryxtech.com
Sent: Wednesday, November 20, 2019 9:04 AM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] VPP New plugin intergation
Hi Team,
We are trying to implement a plugin to process all packets on virtual
interface.
We are doing span from physical interface to virtual interface on vpp
Hi Team,
We are trying to implement a plugin to process all packets on virtual
interface.
We are doing span from physical interface to virtual interface on vpp,by
running plugin arc node with interface-output.
We are facing some problems.
Could you please help us to resolve the issue by
