#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-port s2 vx2 -- set interface vx2 type=vxlan option:remote_ip=172.16.4.1 option:key=flow ofport_request=22 sh ovs-ofctl add-flow s2 'in_port=22,tun_id=1,actions=output:1' sh ovs-ofctl add-flow s2 'in_port=1,actions=set_field:2->tun_id,output:22’ I was hoping that packets incoming to OVS would match against the VXLAN port flows, however it seems as if OVS always chooses the first VXLAN port for all VXLAN packets On Wed, Sep 24, 2014 at 3:34 AM, Ben Pfaff <b...@nicira.com> wrote: > 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 you configure the ports? > -- *Jaime Pillora |* Chief Software Architect web: lumanetworks.com email: ja...@lumanetworks.com mobile: +61 (0) 422 171 218
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
