My configuration is just like:
redhat openvswitch 1.4.0
ubuntu openvswitch 1.20
I found If I add a flow on the side of redhat, it will work:
ovs-ofctl add-flow br-tun priority=2,in_port=2,actions=normal
Note: port 2 is the gre port to unbuntu.
strange stuff is : This rule does not work on ubuntu side. I mean I don't need to add a such rule on ubuntu side, and even if I add a rule such as on ubuntu:
ovs-ofctl add-flow br-tun priority=2,in_port=2,actions=drop, it will not block the gre traffic.
After that: I decide to upgrade my openvswitch to latest one 1.4.1 on ubuntu side. This way, all the default settings by our agents and quantum server are enough and correct.
And one more issue for our agent:
ovs-ofctl del-flow br-tun priority=1,xx=yy will not work. According to ovs-ofctl man page, we need --strict if priority keyword is in match.
My configuration is just like:
redhat openvswitch 1.4.0
ubuntu openvswitch 1.20
I found If I add a flow on the side of redhat, it will work: 2,in_port= 2,actions= normal
ovs-ofctl add-flow br-tun priority=
Note: port 2 is the gre port to unbuntu.
strange stuff is : This rule does not work on ubuntu side. I mean I don't need to add a such rule on ubuntu side, and even if I add a rule such as on ubuntu: 2,in_port= 2,actions= drop, it will not block the gre traffic.
ovs-ofctl add-flow br-tun priority=
After that: I decide to upgrade my openvswitch to latest one 1.4.1 on ubuntu side. This way, all the default settings by our agents and quantum server are enough and correct.
And one more issue for our agent:
ovs-ofctl del-flow br-tun priority=1,xx=yy will not work. According to ovs-ofctl man page, we need --strict if priority keyword is in match.