netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Benc <jbenc@redhat.com>
To: netdev@vger.kernel.org
Cc: Thomas Graf <tgraf@suug.ch>
Subject: [PATCH net-next 0/2] vxlan: support both IPv4 and IPv6 sockets
Date: Thu, 24 Sep 2015 13:50:00 +0200	[thread overview]
Message-ID: <cover.1443094736.git.jbenc@redhat.com> (raw)

Note: this needs net merged into net-next in order to apply.

It's currently not easy enough to work with metadata based vxlan tunnels. In
particular, it's necessary to create separate network interfaces for IPv4
and IPv6 tunneling. Assigning an IPv6 address to an IPv4 interface is
allowed yet won't do what's expected. With route based tunneling, one has to
pay attention to use the vxlan interface opened with the correct family.
Other users of this (openvswitch) would need to always create two vxlan
interfaces.

Furthermore, there's no sane API for creating an IPv6 vxlan metadata based
interface.

This patchset simplifies this by opening both IPv4 and IPv6 socket if the
vxlan interface has the metadata flag (IFLA_VXLAN_COLLECT_METADATA) set.
Assignment of addresses etc. works as expected after this.

Jiri Benc (2):
  vxlan: make vxlan_sock_add and vxlan_sock_release complementary
  vxlan: support both IPv4 and IPv6 sockets in a single vxlan device

 drivers/net/vxlan.c           | 167 +++++++++++++++++++++++++++---------------
 include/net/vxlan.h           |  14 +++-
 net/openvswitch/vport-vxlan.c |   3 +-
 3 files changed, 121 insertions(+), 63 deletions(-)

-- 
1.8.3.1

             reply	other threads:[~2015-09-24 11:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-24 11:50 Jiri Benc [this message]
2015-09-24 11:50 ` [PATCH net-next 1/2] vxlan: make vxlan_sock_add and vxlan_sock_release complementary Jiri Benc
2015-09-24 11:50 ` [PATCH net-next 2/2] vxlan: support both IPv4 and IPv6 sockets in a single vxlan device Jiri Benc
2015-09-27  5:41 ` [PATCH net-next 0/2] vxlan: support both IPv4 and IPv6 sockets David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cover.1443094736.git.jbenc@redhat.com \
    --to=jbenc@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=tgraf@suug.ch \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).