From: Ben Pfaff Date: Fri, 18 Oct 2013 17:29:19 +0000 (-0700) Subject: FAQ: Add Q&A about bridge compatibility. X-Git-Tag: sliver-openvswitch-2.0.90-1~7^2~36 X-Git-Url: http://git.onelab.eu/?a=commitdiff_plain;h=900dc97c75d4cf61a010e7951d84088437415274;p=sliver-openvswitch.git FAQ: Add Q&A about bridge compatibility. Signed-off-by: Ben Pfaff --- diff --git a/FAQ b/FAQ index 99e6107eb..b81ee6c35 100644 --- a/FAQ +++ b/FAQ @@ -198,6 +198,25 @@ A: Tunnel virtual ports are not supported, as described in the actions. On Linux kernels before 2.6.39, maximum-sized VLAN packets may not be transmitted. +Q: What happened to the bridge compatibility feature? + +A: Bridge compatibility was a feature of Open vSwitch 1.9 and earlier. + When it was enabled, Open vSwitch imitated the interface of the + Linux kernel "bridge" module. This allowed users to drop Open + vSwitch into environments designed to use the Linux kernel bridge + module without adapting the environment to use Open vSwitch. + + Open vSwitch 1.10 and later do not support bridge compatibility. + The feature was dropped because version 1.10 adopted a new internal + architecture that made bridge compatibility difficult to maintain. + Now that many environments use OVS directly, it would be rarely + useful in any case. + + To use bridge compatibility, install OVS 1.9 or earlier, including + the accompanying kernel modules (both the main and bridge + compatibility modules), following the instructions that come with + the release. Be sure to start the ovs-brcompatd daemon. + Terminology -----------