[ovs-discuss] Q: network(s) isolation

Alexey I. Froloff raorn at altlinux.org
Tue Apr 13 12:15:19 UTC 2010


On Fri, Apr 09, 2010 at 01:08:12AM -0700, Justin Pettit wrote:
> > Am I right?
> That all looks correct to me!
It doesn't seem to work.

This is my current configuration, made with vconfig(8) and
brctl(8) (with vswitchd and brcompatd running):

# brctl show
bridge name     bridge id               STP enabled     interfaces
vnetbr3145      0000.001a648982e2       no              eth1.3145
vnetbr3146      0000.001a648982e2       no              eth1.3146
vnetbr3147      0000.001a648982e2       no              eth1.3147
public          0000.001a648982e0       no              eth0
virbr0          0000.002320dbf544       no              
# ovs-vsctl list-br
vnetbr3145
vnetbr3146
vnetbr3147
public
virbr0
# ip li
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue 
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
4: gre0: <NOARP> mtu 1476 qdisc noop 
5: sit0: <NOARP> mtu 1480 qdisc noop 
6: public: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue 
7: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue 
8: eth1.3145 at eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue 
9: vnetbr3145: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue 
10: eth1.3146 at eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue 
11: vnetbr3146: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue 
12: eth1.3147 at eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue 
13: vnetbr3147: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue 

Now, trying recreate this configuration with ovs-vsctl(8):

# ovs-vsctl add-br vnetbr3145
# ovs-vsctl add-port vnetbr3145 eth1 tag=3145
# ovs-vsctl add-br vnetbr3146
# ovs-vsctl add-port vnetbr3146 eth1 tag=3146
ovs-vsctl: cannot create a port named eth1 because a port named eth1 already exists on bridge vnetbr3145

Now I'm totally confused...  And by the way, how will I see tagged VLAN
packages on eth1 interface since VLAN tags may be filtered by hardware (see
vconfig(8) manual page)?

-- 
Regards,    --
Sir Raorn.   --- http://thousandsofhate.blogspot.com/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20100413/0c0c05dc/attachment.sig>


More information about the discuss mailing list