On Sat, May 12, 2012 at 7:01 PM, yong sheng gong <email address hidden> wrote:
> My configuration is just like:
> redhat openvswitch 1.4.0
>
Did you install this yourself, or are you using the built-in OVS in the
Linux kernel (this is the default). If the latter, then this won't work,
as the in-kernel version of OVS does not have tunnel support.
> 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.
>
Interesting. Did you run into this in practice? I don't see a call to
delete_flows() that actually specifies a value for priority, but it
certainly seems worth fixing as one could be added in the future. Want to
file a bug and submit a patch?
On Sat, May 12, 2012 at 7:01 PM, yong sheng gong <email address hidden> wrote:
> My configuration is just like:
> redhat openvswitch 1.4.0
>
Did you install this yourself, or are you using the built-in OVS in the
Linux kernel (this is the default). If the latter, then this won't work,
as the in-kernel version of OVS does not have tunnel support.
> 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.
>
Interesting. Did you run into this in practice? I don't see a call to
delete_flows() that actually specifies a value for priority, but it
certainly seems worth fixing as one could be added in the future. Want to
file a bug and submit a patch?