[P4-dev] a packet lopping problem in bmv2
antonin at barefootnetworks.com
Fri Nov 17 11:31:46 EST 2017
This is probably not an issue with bmv2 but with your setup.
Usually the most common issue is that something else outside of bmv2 is
trying to forward your packets. You may want to make sure that when the
simple_switch process is not running, *the sender and receiver machines
cannot talk to each other*.
Make sure that ens35 and ens38 are not bridged and make sure that IP
forwarding is disabled in your Ubuntu machine.
On Thu, Nov 16, 2017 at 8:37 PM, Bian Jason <imaginezz at outlook.com> wrote:
> Hi everyone,
> I ‘m a beginner in p4. I’m trying to test the forwarding efficiency of
> I use Ubuntu 16 in Vmware , and the host machine is Windows10. I plug two
> network card in the host machine, and use Vmware’s bridge mode mapped
> these to NIC to Ubuntu. And I also use another two machine as a sender and
> a receiver.
> Then, I start bmv2 use command
> ` sudo simple_switch -i 1 at ens35 -i 2 at ens38 --thrift-port 9090 --nanolog
> ipc:///tmp/bm-0-log.ipc --device-id 0 p4app/app.json --log-console`
> And deliver the flow table to it.
> Next, I send a UDP packet from sender to receiver, and the receiver get
> the packet successfully.
> But bmv2 began to constantly send the one data packet I sent just now.
> When I checked the log file, I observed a packet sent from port one to
> port two, and then it was sent back to port two, thus beginning a loop.
> I wander know what’s wrong with the bmv2, is it a bug?
> BUPT FNL
> P4-dev mailing list
> P4-dev at lists.p4.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the P4-dev