I see, thanks, got it working using patches and a single tunnel bridge, which
are then connected to all customer bridges, like this:
ovs-vsctl del-br br1
ovs-vsctl add-br br1 -- set bridge br1 other_config:hwaddr=f6:8d:91:7b:99:01
other_config:disable-in-band=true
ovs-vsctl add-port br1 gre1 -- set Interface gre1 ofport_request=1 type=gre
options:remote_ip=flow options:key=flow
ovs-ofctl add-flow br1 "in_port=LOCAL
actions=set_tunnel:1,set_field:10.20.9.42->tun_dst,output:1,set_field:10.20.2.42->tun_dst,output:1"
ip addr add 10.200.0.1/24 dev br1
ovs-vsctl add-port br1 patch1-2 -- set Interface patch1-2 ofport_request=2
type=patch options:peer=patch2-1
ovs-ofctl add-flow br1 "in_port=2
actions=set_tunnel:2,set_field:10.20.9.42->tun_dst,output:1,set_field:10.20.2.42->tun_dst,output:1"
ovs-ofctl add-flow br1 "in_port=1 tun_id=2 actions=output:2"
ovs-vsctl add-port br1 patch1-3 -- set Interface patch1-3 ofport_request=3
type=patch options:peer=patch3-1
ovs-ofctl add-flow br1 "in_port=3
actions=set_tunnel:3,set_field:10.20.9.42->tun_dst,output:1,set_field:10.20.2.42->tun_dst,output:1"
ovs-ofctl add-flow br1 "in_port=1 tun_id=3 actions=output:3"
ovs-vsctl del-br br2
ovs-vsctl add-br br2 -- set bridge br2 other_config:hwaddr=f6:8d:91:7b:99:02
other_config:disable-in-band=true
ovs-vsctl add-port br2 patch2-1 -- set Interface patch2-1 type=patch
options:peer=patch1-2
ip addr add 10.201.0.1/24 dev br2
On 06/02/2014, at 19.04.07, Jesse Gross <je...@nicira.com> wrote:
> You can't create multiple tunnels with the exact same configuration -
> otherwise there is no way to determine which port should get packets
> on receive.
>
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
