Thanx for the quick reply. Got that, but I still haven't solved my
problem though.
Is there any way to group the packet flow without sacrificing the L2
lookup?
I think that the flows to multiple ports (i.e. ovs-ofctl add-flow br0
in_port=3,actions=output:1,2)
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 <el05...@mail.ntua.gr>
wrote:
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
something
like
#ovs-ofctl add-flow br0
tun_id=1,idle_timeout=0,priority=1,actions=set_tunnel:1,normal
(I want normal action in order to preserve L2 lookups)
The rule is created but there are no packets "caught". They always
"fall
into" to the default rule.
Am i doing something wrong? I, also, noticed a message NXST_FLOW
reply
(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
is
considered to be a property of the port itself and the tun_id is
zeroed.
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
