Hello,
I am using OpenVswitch version 1.1.1.
I have a bridge configuration consisted by multiple EoGRE tunnels.
Here is an example output of ovs-vsctl list Interface (ommiting what I
consider as irrelevant info)
admin_state : up
name : "gre5"
ofport : 5
options : {key="4", remote_ip="10.0.0.5"}
other_config : {}
status : {tunnel_egress_iface="eth0",
tunnel_egress_iface_carrier=up}
type : gre
admin_state : up
name : "gre2"
ofport : 2
options : {key="1", remote_ip="10.0.0.2"}
other_config : {}
status : {tunnel_egress_iface="eth0",
tunnel_egress_iface_carrier=up}
type : gre
admin_state : up
name : "gre4"
ofport : 4
options : {key="4", remote_ip="10.0.0.4"}
other_config : {}
status : {tunnel_egress_iface="eth0",
tunnel_egress_iface_carrier=up}
type : gre
admin_state : up
name : "gre1"
ofport : 1
options : {key="1", remote_ip="10.0.0.1"}
other_config : {}
status : {tunnel_egress_iface="eth0",
tunnel_egress_iface_carrier=up}
type : gre
admin_state : up
name : "gre3"
ofport : 3
options : {key="1", remote_ip="10.0.0.3"}
other_config : {}
status : {tunnel_egress_iface="eth0",
tunnel_egress_iface_carrier=up}
type : gre
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?
Lastly, can you propose me different ways to achieve this grouping
using OpenVswitch?
I would, strongly, prefer a solution without Vlans!
Thank you very much,
Emmanouil
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss
