[ovs-discuss] vlan problem

Jesse Gross jesse at nicira.com
Thu Nov 29 16:44:20 UTC 2012


On Thu, Nov 29, 2012 at 3:34 AM, 春祥 王 <wchunx416 at yahoo.cn> wrote:

> Hi all,
>     I have 2 kvm installed on my host machine,vm1 and vm2.I used
> Ubuntu12.04 LTS 64bit for testing.
> host ip(eth1) 192.168.0.190
> vm1 ip           192.168.0.33
> vm2 ip           192.168.0.44
> ovs-vsctl add-br br0
> ovs-vsctl add-port br0 eth1
> ifconfig eth1 0
> ifconfig br0 192.168.0.190 netmask 255.255.255.0 up
> route add default gw 192.168.0.1
> echo nameserver 8.8.8.8 >> /etc/resolv.conf
>
> add tap0(interface for vm1) and tap1(interface for vm2) to br0 with tag10
> and tag20
> ovs-vsctl add-port tap0 br0 tag=10
> ovs-vsctl add-port tap1 br0 tag=20
>
> ovs-vsctl show
> f5db2e94-7ce7-425e-88dc-9303273bda89
>     Bridge "br0"
>         Port "eth1"
>             Interface "eth1"
>         Port "tap1"
>             tag: 20
>             Interface "tap2"
>         Port "tap0"
>             tag: 10
>             Interface "tap1"
>         Port "br0"
>             Interface "br0"
>                 type: internal
>     ovs_version: "1.4.0+build0"
> the vms cannot ping each other,and cannot ping my host (192.168.0.190),the
> gateway(192.168.0.1) and the external network.
> next,
> ovs-vsctl set port eth1 trunks=10,20
> problem was not solved,and the host cannot access external network.
>
> ovs-vsctl remove port eth1 trunks 10,20
> ovs-vsctl set port eth1 trunks=0,10,20
> the result is the same with the original situation.
>
> I tried to set eth1 an tap0 tag=10,and tap1 tag=20,vm1 can access external
> network but host and vm2 cannot.
>
> I want to make vm1 and vm2 into differert vlan,and both of them can access
> the external network,but I failed.
>

Did you read the vlan section of the FAQ?:
http://openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=blob_plain;f=FAQ;hb=HEAD
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20121129/35254669/attachment-0001.html>


More information about the discuss mailing list