netdev - Re: [PATCH net-next 0/2] vxlan: support both IPv4 and IPv6 sockets

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20150926.224110.1190457686665465368.davem@davemloft.net>
Date:	Sat, 26 Sep 2015 22:41:10 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	jbenc@...hat.com
Cc:	netdev@...r.kernel.org, tgraf@...g.ch
Subject: Re: [PATCH net-next 0/2] vxlan: support both IPv4 and IPv6 sockets

From: Jiri Benc <jbenc@...hat.com>
Date: Thu, 24 Sep 2015 13:50:00 +0200

> 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.

Series applied, thanks Jiri.
--
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