[Edited Message Follows]

Hi Experts,
We implemented a PLUGIN, this plugin reads packets from physical interface and 
sends to memif.
We implemented this approach to get RAW packets to our application.
The memif other end is our application, it takes necessary action.
The packet flow would be

Devie-Input --> OUR Plugin --> Memif --> Our application.(Plugin filters the 
packets and send to memif or Bond-input.)
or
Devie-Input --> OUR Plugin --> bond-input --> VPP processing.

Our plugin is working with only physical interface. Now we are trying to make 
this work with Bonded Interface, its not working with bonded interface.
If we disable bond-input for that physical interface and only enable our plugin 
it will work fine. But we needed BondedInterface support for LACP. So we can't 
just avoid BondedInterface.
Our feature arc is
VNET_FEATURE_INIT (ipgw_ent, static) =
{
.arc_name = "device-input",
.node_name = "ravi_plugin",
.runs_before = VNET_FEATURES ("ethernet-input"),
};

I tried placing different arcs for my plugin, its not working. Can you please 
suggest how can our plugin to make it work for logical interfaces.
Like if we want to make it work for BondedInterface.1100? which arc we should 
choose, we need raw packets to our application.
Any mechanism which can provide RAW PACKET reading from VPP also works fine.
Any pointers are very big help.

//Ravi.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#19793): https://lists.fd.io/g/vpp-dev/message/19793
Mute This Topic: https://lists.fd.io/mt/84233170/21656
Mute #plugin:https://lists.fd.io/g/vpp-dev/mutehashtag/plugin
Mute #memif:https://lists.fd.io/g/vpp-dev/mutehashtag/memif
Mute #bondedinterface:https://lists.fd.io/g/vpp-dev/mutehashtag/bondedinterface
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to