So I’m now using option:key=1 and 2 instead of key=flow. I’m attempting to
tag 1 -> 2 with VNID 2, and 2 -> 1 with VNID 1.
*** Setting VXLAN 1 -> 2
ovs-vsctl set bridge s1 protocols=OpenFlow13
ovs-vsctl add-port s1 vx1 -- set interface vx1 type=vxlan
option:remote_ip=localhost option:key=1 ofport_
Sorry, I should have clarified, 172.16.4.1 is a dummy UDP server reflecting
packets back to the sender (since localhost wasn’t working). Indeed VXLAN
packets are arriving on the dummy server, though they’re not being accepted
back by OVS. I was hoping to specify the VNID in flows as it much more
dy
#switch 1
sh ovs-vsctl add-port s1 vx1 -- set interface vx1 type=vxlan
option:remote_ip=172.16.4.1 option:key=flow ofport_request=11
sh ovs-ofctl add-flow s1 'in_port=11,tun_id=2,actions=output:1'
sh ovs-ofctl add-flow s1 'in_port=1,actions=set_field:1->tun_id,output:11'
#switch 2
sh ovs-vsctl add
On Wed, Sep 24, 2014 at 11:07:06AM +1000, Jaime Pillora wrote:
> #switch 1
> sh ovs-vsctl add-port s1 vx1 -- set interface vx1 type=vxlan
> option:remote_ip=172.16.4.1 option:key=flow ofport_request=11
> sh ovs-ofctl add-flow s1 'in_port=11,tun_id=2,actions=output:1'
> sh ovs-ofctl add-flow s1 'in_
On Mon, Sep 22, 2014 at 11:13:45AM +1000, Jaime Pillora wrote:
> I???ve added a VXLAN ports to vx1,2 to bridges s1,2 and it seems only the
> first VXLAN port I create works. Is this a bug or am I only able to use one
> VXLAN port for each OVS instance?
It's probably a configuration error. How did
I’ve added a VXLAN ports to vx1,2 to bridges s1,2 and it seems only the
first VXLAN port I create works. Is this a bug or am I only able to use one
VXLAN port for each OVS instance?
Jaime
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch
