From: Ben Pfaff Date: Fri, 27 Jul 2012 04:55:57 +0000 (-0700) Subject: FAQ: Add another question about VLAN interaction with controllers. X-Git-Tag: sliver-openvswitch-1.8.90-0~48^2~165 X-Git-Url: http://git.onelab.eu/?p=sliver-openvswitch.git;a=commitdiff_plain;h=f0a0c1a6ef2c09c3aed2a4077878be002ccf7cd4 FAQ: Add another question about VLAN interaction with controllers. I'm pretty sure I've seen this one more than once. Signed-off-by: Ben Pfaff --- diff --git a/FAQ b/FAQ index 91f400700..bdd96ce91 100644 --- a/FAQ +++ b/FAQ @@ -408,6 +408,24 @@ A: The configuration for VLANs in the Open vSwitch database (e.g. via controller. This will only be suitable for some situations, though. +Q: I configured ports on a bridge as access ports with different VLAN + tags, like this: + + ovs-vsctl add-br br0 + ovs-vsctl set-controller br0 tcp:192.168.0.10:6633 + ovs-vsctl add-port br0 eth0 + ovs-vsctl add-port br0 tap0 tag=9 + ovs-vsctl add-port br0 tap1 tag=10 + + but the VMs running behind tap0 and tap1 can still communicate, + that is, they are not isolated from each other even though they are + on different VLANs. + +A: Do you have a controller configured on br0 (as the commands above + do)? If so, then this is a variant on the previous question, "My + OpenFlow controller doesn't see the VLANs that I expect," and you + can refer to the answer there for more information. + Controllers -----------