On Tue, 27 Nov 2012 15:19:24 -0500 Kyle Mestery <kmest...@cisco.com> wrote:
> Note: v4 of this patch removes VXLAN over IPSEC support, > per an offline conversation with Jesse. > > Add support for VXLAN tunnels to Open vSwitch. Add support > for setting the destination UDP port on a per-port basis. > This is done by adding a "dst_port" parameter to the port > configuration. This is only applicable currently to VXLAN > tunnels. > > Please note this currently does not implement any sort of multicast > learning. With this patch, VXLAN tunnels must be configured similar > to GRE tunnels (e.g. point to point). A subsequent patch will implement > a VXLAN control plane in userspace to handle multicast learning. > > This patch set is based on one posted by Ben Pfaff on Oct. 12, 2011 > to the ovs-dev mailing list: > > http://openvswitch.org/pipermail/dev/2011-October/012051.html > > The patch has been maintained, updated, and freshened by me and a > version of it is available at the following github repository: > > https://github.com/mestery/ovs-vxlan/tree/vxlan > > I've tested this patch with multiple VXLAN tunnels between hosts > using different UDP port numbers. Performance is on par (though > slightly faster) than comparable GRE tunnels. > > See the following IETF draft for additional information about VXLAN: > http://tools.ietf.org/html/draft-mahalingam-dutt-dcops-vxlan-02 > > Signed-off-by: Kyle Mestery <kmest...@cisco.com> Looks good, glad to see it. One question, and it might be part of a bigger issue, the code doesn't seem to be network namespace aware. Is OVS able to handle network namespaces? The socket needs to be bound the netns of the OVS instance. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
