Dear all,
according to [1] by default ovs inserts some hidden flows that can create
loops in particular conditions.

I am experiencing the same problem using ovs with the DPDK datapath and
then, after configuring the controller through the command

ovs-vsct --no-wait set-controller br0 tcp:127.0.0.1:8000

I use the following commands in order to remove the hidden flows

ovs-vsct --no-wait set-controller br0 connection-mode=out-of-band
ovs-vsct --no-wait set-controller br0 other-config:disable-in-band=true

At this point, through "ovs-vsctl show" I see that the bridge does not have
any controller set

ovs-vsctl show
aa3dee91-dfa7-4109-acac-4746534e1786
    Bridge "br0"
        Controller "other-config:disable-in-band=true"
        Port "br0"
            Interface "br0"
                type: internal
        Port "dpdk0"
            Interface "dpdk0"
                type: dpdk
        Port "dpdk1"
            Interface "dpdk1"
                type: dpdk
       Port "vm_port1"
            Interface "vm_port1"
        Port "vm_port2"
            Interface "vm_port2"

Instead, the flow table of the switch is the following:

ovs-ofctl dump-flows br_0 --protocol=OpenFlow12
OFPST_FLOW reply (OF1.2) (xid=0x2):
 cookie=0x0, duration=5.038s, table=0, n_packets=663, n_bytes=57732,
priority=0 actions=NORMAL


Do you have any idea about why this is happening?
When I do not use the DPDK datapath, everything works fine and with the
previous commands I am able to remove the hidden flows.

Thank you very much in advance.

Regards,

Mauricio V,
Ivano C,


[1] http://openvswitch.org/pipermail/discuss/2015-March/017029.html
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

Reply via email to