I put an assert just to be sure that virtio-input got a frame with the
ETH_INPUT_FRAME_F_SINGLE_SW_IF_IDX
flag.
Attaching to process 324596
[New LWP 324612]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7fc5c21cf1dc
Looks like I found the issue:
it happens when ethernet-node gets a frame with flag
ETH_INPUT_FRAME_F_SINGLE_SW_IF_IDX but they're actually packets from
different interfaces (from virtio-node but some of them are l2 and some of
them are l3). virtio-input doesn't set this flag, but I thought maybe
Hello folks,
I'm experiencing a weird issue. I'm running a current master with linux-cp
plugin enabled.
I create a loopback interface, set it as BVI for a bridge, and create a lcp
for the loop. Almost everywhere it's working just fine. Usually, the trace
looks like this:
virtio-input ->
