netdev - Re: [PATCH v2 net-next 4/4] vxlan: do not receive IPv4 packets on IPv6 socket

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20150828223929.GC32001@pox.localdomain>
Date:	Sat, 29 Aug 2015 00:39:29 +0200
From:	Thomas Graf <tgraf@...g.ch>
To:	Jiri Benc <jbenc@...hat.com>
Cc:	netdev@...r.kernel.org, Pravin Shelar <pshelar@...ira.com>
Subject: Re: [PATCH v2 net-next 4/4] vxlan: do not receive IPv4 packets on
 IPv6 socket

On 08/28/15 at 08:48pm, Jiri Benc wrote:
> By default (subject to the sysctl settings), IPv6 sockets listen also for
> IPv4 traffic. Vxlan is not prepared for that and expects IPv6 header in
> packets received through an IPv6 socket.
> 
> In addition, it's currently not possible to have both IPv4 and IPv6 vxlan
> tunnel on the same port (unless bindv6only sysctl is enabled), as it's not
> possible to create and bind both IPv4 and IPv6 vxlan interfaces and there's
> no way to specify both IPv4 and IPv6 remote/group IP addresses.
> 
> Set IPV6_V6ONLY on vxlan sockets to fix both of these issues. This is not
> done globally in udp_tunnel, as l2tp and tipc seems to work okay when
> receiving IPv4 packets on IPv6 socket and people may rely on this behavior.
> The other tunnels (geneve and fou) do not support IPv6.
> 
> Signed-off-by: Jiri Benc <jbenc@...hat.com>

Can we fix VXLAN instead? It should be possible to receive and send both
v4 and v6 frames and represent it with metadata on a single socket.

Maybe set the flag if IFLA_VXLAN_COLLECT_METADATA is not set?
--
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