X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=FAQ;h=7181484ef83b620f170ea52cc0f8a899a301a3fe;hb=3442636d01d2a73a557952ad9140de07418c28c2;hp=7df4e90e9daed0eb36a8d3bdf17103ff8b567159;hpb=ac12b4cb480a1295b9628d87e7414e85e32c668d;p=sliver-openvswitch.git diff --git a/FAQ b/FAQ index 7df4e90e9..7181484ef 100644 --- a/FAQ +++ b/FAQ @@ -27,7 +27,7 @@ A: Open vSwitch is a production quality open source software switch Q: What virtualization platforms can use Open vSwitch? A: Open vSwitch can currently run on any Linux-based virtualization - platform (kernel 2.6.18 and newer), including: KVM, VirtualBox, Xen, + platform (kernel 2.6.32 and newer), including: KVM, VirtualBox, Xen, Xen Cloud Platform, XenServer. As of Linux 3.3 it is part of the mainline kernel. The bulk of the code is written in platform- independent C and is easily ported to other environments. We welcome @@ -146,12 +146,15 @@ A: The following table lists the Linux kernel versions against which the 1.7.x 2.6.18 to 3.3 1.8.x 2.6.18 to 3.4 1.9.x 2.6.18 to 3.8 + 1.10.x 2.6.18 to 3.8 + 1.11.x 2.6.18 to 3.8 + 2.x 2.6.32 to 3.10 Open vSwitch userspace should also work with the Linux kernel module built into Linux 3.3 and later. Open vSwitch userspace is not sensitive to the Linux kernel version. - It should build against almost any kernel, certainly against 2.6.18 + It should build against almost any kernel, certainly against 2.6.32 and later. Q: What Linux kernel versions does IPFIX flow monitoring work with? @@ -247,6 +250,40 @@ A: The following commands configure br0 with eth0 and tap0 as trunk ovs-vsctl clear bridge br0 mirrors +Q: Does Open vSwitch support configuring a port in promiscuous mode? + +A: Yes. How you configure it depends on what you mean by "promiscuous + mode": + + - Conventionally, "promiscuous mode" is a feature of a network + interface card. Ordinarily, a NIC passes to the CPU only the + packets actually destined to its host machine. It discards + the rest to avoid wasting memory and CPU cycles. When + promiscuous mode is enabled, however, it passes every packet + to the CPU. On an old-style shared-media or hub-based + network, this allows the host to spy on all packets on the + network. But in the switched networks that are almost + everywhere these days, promiscuous mode doesn't have much + effect, because few packets not destined to a host are + delivered to the host's NIC. + + This form of promiscuous mode is configured in the guest OS of + the VMs on your bridge, e.g. with "ifconfig". + + - The VMware vSwitch uses a different definition of "promiscuous + mode". When you configure promiscuous mode on a VMware vNIC, + the vSwitch sends a copy of every packet received by the + vSwitch to that vNIC. That has a much bigger effect than just + enabling promiscuous mode in a guest OS. Rather than getting + a few stray packets for which the switch does not yet know the + correct destination, the vNIC gets every packet. The effect + is similar to replacing the vSwitch by a virtual hub. + + This "promiscuous mode" is what switches normally call "port + mirroring" or "SPAN". For information on how to configure + SPAN, see "How do I configure a port as a SPAN port, that is, + enable mirroring of all traffic to that port?" + Q: How do I configure a VLAN as an RSPAN VLAN, that is, enable mirroring of all traffic to that VLAN? @@ -934,22 +971,26 @@ A: Open vSwitch 1.9 and earlier support only OpenFlow 1.0 (plus extensions that bring in many of the features from later versions of OpenFlow). - Open vSwitch versions 1.10 and later will have experimental support - for OpenFlow 1.2 and 1.3. On these versions of Open vSwitch, the - following command enables OpenFlow 1.0, 1.2, and 1.3 on bridge br0: + Open vSwitch 1.10 and later have experimental support for OpenFlow + 1.2 and 1.3. On these versions of Open vSwitch, the following + command enables OpenFlow 1.0, 1.2, and 1.3 on bridge br0: ovs-vsctl set bridge br0 protocols=OpenFlow10,OpenFlow12,OpenFlow13 + Open vSwitch version 1.12 and later will have experimental support + for OpenFlow 1.1, 1.2, and 1.3. On these versions of Open vSwitch, + the following command enables OpenFlow 1.0, 1.1, 1.2, and 1.3 on + bridge br0: + + ovs-vsctl set bridge br0 protocols=OpenFlow10,OpenFlow11,OpenFlow12,OpenFlow13 + Use the -O option to enable support for later versions of OpenFlow in ovs-ofctl. For example: ovs-ofctl -O OpenFlow13 dump-flows br0 - Support for OpenFlow 1.1 is incomplete enough that it cannot yet be - enabled, even experimentally. - - Support for OpenFlow 1.2 and 1.3 is still incomplete. Work to be - done is tracked in OPENFLOW-1.1+ in the Open vSwitch source tree + Support for OpenFlow 1.1, 1.2, and 1.3 is still incomplete. Work + to be done is tracked in OPENFLOW-1.1+ in the Open vSwitch sources (also via http://openvswitch.org/development/openflow-1-x-plan/). When support for a given OpenFlow version is solidly implemented, Open vSwitch will enable that version by default.