[ovs-discuss] Problems setting up VxLAN

Gurucharan Shetty shettyg at nicira.com
Thu Feb 20 15:29:39 UTC 2014


On Wed, Feb 19, 2014 at 2:19 PM, Dominic Curran <gigamuffin at gmail.com> wrote:
> Hi
>
> I'm running OVS on top of Ubuntu 13.10.  I have installed OVS and built the
> tip of the latest master (as of yesterday).
>
> I'm trying to setup VXLAN between two machines.
>
>
> The two machines can ping each other on their DHCP assigned addresses.
>
> On M1 I setup:
> $ sudo ovs-vsctl add-br br1
> $ sudo ifconfig br1 192.168.0.101 netmask 255.255.255.0
> $ sudo ovs-vsctl add-port br1 vx -- set interface vx type=vxlan
> options:remote_ip=192.168.0.102 options:key=40
This won't work.
Assuming eth1 of M1 is connected to eth1 of M2:
Keep the IP address on eth1 and not on br1.

Or do something like this on M1
ovs-vsctl add-br br1
ovs-vsctl add-port br1 eth1
ifconfig br1 192.168.0.101 netmask 255.255.255.0

ovs-vsctl add-br br-int
ovs-vsctl add-port br-int vx -- set interface vx type=vxlan
options:remote_ip=192.168.0.102 options:key=40

Similar on M2

#on M1
ifconfig br-int 1.2.3.4/24

#on M2
ifconfig br-int 1.2.3.5/24

Now, you can ping 1.2.3.5 from M1 over a vxlan tunnel, provided that
your kernel module supports vxlan tunnels.

>
> On M2 I setup:
> $ sudo ovs-vsctl add-br br1
> $ sudo ifconfig br1 192.168.0.102 netmask 255.255.255.0
> $ sudo ovs-vsctl add-port br1 vx -- set interface vx type=vxlan
> options:remote_ip=192.168.0.101 options:key=40
>
> $ sudo ovs-vsctl show
> 7057857a-0df2-49bb-85e6-8e0f27c237d4
>     Bridge "br1"
>         Port "br1"
>             Interface "br1"
>                 type: internal
>         Port vx
>             Interface vx
>                 type: vxlan
>                 options: {key="40", remote_ip="192.168.0.101"}
>     ovs_version: "2.1.90"
>
> The pings fail from either side.  e.g.:
> $ ping 192.168.0.101
> PING 192.168.0.101 (192.168.0.101) 56(84) bytes of data.
> From 192.168.0.102 icmp_seq=1 Destination Host Unreachable
>
> Any ideas ?
> The bridge br1 I created doesnt have a port for a physical NIC (e.g. eth0).
> Should it have ?
What you have right now is that
>
> Doing tcpdump on br1 just showns ARP requests for 192.168.0.101.
>
> thanks
> dom
>
>
> _______________________________________________
> discuss mailing list
> discuss at openvswitch.org
> http://openvswitch.org/mailman/listinfo/discuss
>



More information about the discuss mailing list