From 241241f55a1277635e2011eac1d18ef7549b2e74 Mon Sep 17 00:00:00 2001 From: Ben Pfaff Date: Wed, 6 Feb 2013 09:12:59 -0800 Subject: [PATCH] FAQ: Expand on how one would implement VLAN handling via flows. Signed-off-by: Ben Pfaff --- FAQ | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/FAQ b/FAQ index 1f8c94c09..aacd6de9f 100644 --- a/FAQ +++ b/FAQ @@ -798,8 +798,16 @@ A: The configuration for VLANs in the Open vSwitch database (e.g. via You can use "normal switching" as a component of your OpenFlow actions, e.g. by putting "normal" into the lists of actions on ovs-ofctl or by outputting to OFPP_NORMAL from an OpenFlow - controller. This will only be suitable for some situations, - though. + controller. In situations where this is not suitable, you can + implement VLAN handling yourself, e.g.: + + - If a packet comes in on an access port, and the flow table + needs to send it out on a trunk port, then the flow can add + the appropriate VLAN tag with the "mod_vlan_vid" action. + + - If a packet comes in on a trunk port, and the flow table + needs to send it out on an access port, then the flow can + strip the VLAN tag with the "strip_vlan" action. Q: I configured ports on a bridge as access ports with different VLAN tags, like this: -- 2.20.1