[ovs-dev] [patch_ports (rebased) 3/4] ofproto-dpif: Implement patch ports in userspace.
emaste at freebsd.org
Wed Jan 23 22:10:54 UTC 2013
On 23 January 2013 15:51, Ethan Jackson <ethan at nicira.com> wrote:
> diff --git a/FAQ b/FAQ
> index ab1c1cc..a466ca4 100644
> --- a/FAQ
> +++ b/FAQ
> @@ -172,17 +172,24 @@ A: The kernel module in upstream Linux 3.3 and later does not include
> vSwitch distribution instead of the upstream Linux kernel
> - - Patch virtual ports, that is, interfaces with type "patch".
> - You can use Linux "veth" devices as a substitute.
> - We don't have any plans to add patch ports upstream.
> Q: What features are not available when using the userspace datapath?
> -A: Tunnel and patch virtual ports are not supported, as described in the
> - previous answer. It is also not possible to use queue-related
> - actions. On Linux kernels before 2.6.39, maximum-sized VLAN packets
> - may not be transmitted.
> +A: The kernel module in upstream Linux 3.3 and later does not include
> + tunnel virtual ports, that is, interfaces with type "gre",
> + "ipsec_gre", "gre64", "ipsec_gre64", "vxlan", or "capwap". It is
> + possible to create tunnels in Linux and attach them to Open vSwitch
> + as system devices. However, they cannot be dynamically created
> + through the OVSDB protocol or set the tunnel ids as a flow action.
This new answer seems to be exclusively about Linux kernel modules,
which seems surprising for a question about the userspace datapath.
On FreeBSD (which uses only the userspace datapath) the new answer has
More information about the dev