[ovs-discuss] Issues on basic switching functionality

Johannes Giani johannes.giani at googlemail.com
Tue Dec 1 18:14:38 UTC 2015


We have problems setting up the ovs. Although we read a lot of tutorials in the internet we couldn’t get an answer to our specific question:

We run ovs as virtualized inside virtual box. It has 1 physical adapter bridged to the controller (floodlight). Getting this configured wasn’t the problem:

ovs-vsctl add-br br0
ovsvsctl set-controller br0 tcp:192.168.2.100

We added 2 other virtual nics to the vm appliance which are in host-only mode. In the host those adapters are configured as follows and belong to the same network:

vboxnet0  Link encap:Ethernet  HWaddr 0a:00:27:00:00:00  
          inet addr:192.168.56.1  Bcast:192.168.56.255  Mask:255.255.255.0
          inet6 addr: fe80::800:27ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2270 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:116531 (116.5 KB)

vboxnet1  Link encap:Ethernet  HWaddr 0a:00:27:00:00:01  
          inet addr:192.168.56.2  Bcast:192.168.56.255  Mask:255.255.255.0
          inet6 addr: fe80::800:27ff:fe00:1/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2385 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:138827 (138.8 KB)

These adapters are available in the vm as eth2 and eth3 - so i added those interfaces as ports to the switch

ovs-vsctl add-port eth2
ovs-vsctl add-port eth3

Now the problem: When I ping from one virtual host interface to the other, it won’t work - Although 2 new hosts are now recognized by the controller:

amc8 at amc8-sw1:~$ ping -I vboxnet0 192.168.56.2
PING 192.168.56.2 (192.168.56.2) from 192.168.56.1 vboxnet0: 56(84) bytes of data.
From 192.168.56.1 icmp_seq=1 Destination Host Unreachable
From 192.168.56.1 icmp_seq=2 Destination Host Unreachable
From 192.168.56.1 icmp_seq=3 Destination Host Unreachable

amc8 at amc8-sw1:~$ ping -I vboxnet1 192.168.56.1
PING 192.168.56.1 (192.168.56.1) from 192.168.56.2 vboxnet1: 56(84) bytes of data.
From 192.168.56.2 icmp_seq=10 Destination Host Unreachable
From 192.168.56.2 icmp_seq=14 Destination Host Unreachable
From 192.168.56.2 icmp_seq=15 Destination Host Unreachable

We would be very thankful if you can tell us what we are doing wrong.

Kind regards,

Johannes Giani


(NOTE: the other switch that appear runs at another machine (mininget) and should not cause the problem - already tested)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20151201/1959675f/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot from 2015-12-01 18_20_35.png
Type: image/png
Size: 157940 bytes
Desc: not available
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20151201/1959675f/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot from 2015-12-01 18_24_33.png
Type: image/png
Size: 179820 bytes
Desc: not available
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20151201/1959675f/attachment-0005.png>


More information about the discuss mailing list