On Tue, May 16, 2017 at 12:07:38PM +0800, ychen wrote: > I can reproduce this problem with the script supported by vguntaka in both > ovs version 2.5 and ovs version 2.6. > > 1. Add bridge > > ovs-vsctl add-br br0 > > > > 2. Add vm port > > ovs-vsctl add-port br0 tap0 – set interface tap0 type=internal > > > > ip netns add ns0 > > ip link set dev tap0 netns ns0 > > ip netns exec ns0 ip link set dev tap0 up > > ip netns exec ns0 ip addr add dev tap0 1.1.1.2/24 > > ip netns exec ns0 ip route add default via 1.1.1.1 > > ip netns exec ns0 ip neigh add 1.1.1.1 lladdr 00:00:00:00:11:11 dev tap0 > > > > 3. Send packet > > Ip netns exec ns0 ping 2.2.2.2 > > > > 4. Add flows (make sure packet is always sending) > > while true > > do > > ovs-ofctl add-flow br0 > "priority=200,table=123,idle_timeout=1,in_port=1,actions=controller" > > ovs-ofctl add-flow br0 > "priority=200,table=123,idle_timeout=1,in_port=2,actions=controller" > > ovs-ofctl add-flow br0 > "priority=200,table=123,idle_timeout=1,in_port=3,actions=controller" > > ovs-ofctl add-flow br0 > "priority=200,table=123,idle_timeout=1,in_port=4,actions=controller" > > ovs-ofctl del-flows br0 > > done > > > > waiting about 1 minute or 2 minute, there is error “OFPT_ERROR (xid=0x4): > OFPFMFC_BAD_COMMAND” printed in console.
Thanks for working on debugging this. Can you get a backtrace from GDB, or an error report from valgrind? _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
