| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <cover.1443094736.git.jbenc@redhat.com> Date: Thu, 24 Sep 2015 13:50:00 +0200 From: Jiri Benc <jbenc@...hat.com> To: netdev@...r.kernel.org Cc: Thomas Graf <tgraf@...g.ch> Subject: [PATCH net-next 0/2] vxlan: support both IPv4 and IPv6 sockets 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 -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists