[ovs-discuss] How to make multiple VLANs on one NIC?

신용진 akayong at gmail.com
Fri May 28 01:49:53 UTC 2010


> It sounds like you wanted to do this:
>         ovs-vsctl add-br xenbr2
>         ovs-vsctl add-port xenbr2 eth2
>         ovs-vsctl add-port xenbr2 xenbr2.100 vlan=100
>         ovs-vsctl add-port xenbr2 xenbr2.200 vlan=200
>
> This will make eth2 a trunk port.  Any packets on vlan 100 will be
> switched to xenbr2.100 with the vlan stripped off.  Any packets on vlan
> 100 will be switched to xenbr2.200 with the vlan stripped off.


Yes, This is what I exactly wanted.

However, when I follow that, 
It says,

" ovs-vsctl: Port does not contain a column whose name matches "vlan""

So I tried like

        ovs-vsctl add-br xenbr2
        ovs-vsctl add-port xenbr2 eth2
        ovs-vsctl add-port xenbr2 xenbr2.100 tag=100
        ovs-vsctl add-port xenbr2 xenbr2.200 tag=200

it works, without any error messages.
However, I could not set IP to xenbr2.100 or xenbr2.200?
And I could not find the device xenbr2.100 and xenbr2.200 in "ifconfig -a"

I only can find it in "Port" table and "Interface" Table.


Thanks in advance.

-----Original Message-----
From: Ben Pfaff [mailto:blp at nicira.com] 
Sent: Friday, May 28, 2010 1:09 AM
To: �ſ���
Cc: discuss at openvswitch.org
Subject: Re: [ovs-discuss] How to make multiple VLANs on one NIC?

On Thu, May 27, 2010 at 10:45:26PM +0900, �ſ��� wrote:
> Firstly, I made a real bridge as xenbr2.
> 
> Then, I made a fake bridge as xenbr2.100 with tagging 100.
> 
> And I attached eth2 to xenbr2.100 with tagging 100.
> 
>  
> 
> And I did same thing to another server
> 
>  
> 
> Then, both server can communicate each other with tagging information.
> 
>  
> 
> However, I want to make another vlan, such as 200, 300 and so on.
> 
>  
> 
> So I made another fake bridge as xenbr2.200 with tagging 200
> 
> And I tried attach eth2 to xenbr2.200 with tagging 200. 
> 
> With ovs-vsctl add-port xenbr2.200 eth2 tag=200
> 
>  
> 
> But it says, 
> 
> ovs-vsctl: cannot create a port named eth2 because a port named eth2
> already exists on bridge xenbr2.100

It sounds like you wanted to do this:
        ovs-vsctl add-br xenbr2
        ovs-vsctl add-port xenbr2 eth2
        ovs-vsctl add-port xenbr2 xenbr2.100 vlan=100
        ovs-vsctl add-port xenbr2 xenbr2.200 vlan=200

This will make eth2 a trunk port.  Any packets on vlan 100 will be
switched to xenbr2.100 with the vlan stripped off.  Any packets on vlan
100 will be switched to xenbr2.200 with the vlan stripped off.





More information about the discuss mailing list