[ovs-discuss] Grouping GRE interfaces' flow with tun_id
el05682 at mail.ntua.gr
Wed Jun 22 01:46:12 UTC 2011
Thanx for the quick reply. Got that, but I still haven't solved my
Is there any way to group the packet flow without sacrificing the L2
I think that the flows to multiple ports (i.e. ovs-ofctl add-flow br0
skip this lookup.
I was thinking to add a fake bridge, remove the tag value,
and add the ports there. Would this provided the desired result?
Are there other alternatives?
On Mon, 20 Jun 2011 20:09:51 -0700, Jesse Gross wrote:
> On Mon, Jun 20, 2011 at 8:05 PM, el05682 <el05682 at mail.ntua.gr>
>> While the connectivity works fine I was considering to add a flow
>> based on
>> the gre key. I actually
>> want to group the ifaces with the same gre key so I was thinking
>> #ovs-ofctl add-flow br0
>> (I want normal action in order to preserve L2 lookups)
>> The rule is created but there are no packets "caught". They always
>> into" to the default rule.
>> Am i doing something wrong? I, also, noticed a message NXST_FLOW
>> (xid=0x4) when I run dump-flows.
>> Is it related to the problem?
> You need to set the key on the port to be "flow", otherwise the key
> considered to be a property of the port itself and the tun_id is
More information about the discuss