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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Sun, 30 Aug 2015 11:30:45 +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/29/15 at 10:55am, Jiri Benc wrote:
> On Sat, 29 Aug 2015 00:39:29 +0200, Thomas Graf wrote:
> > 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.
> 
> That's actually what I intend to do next. But I need the flag and this
> patch for that. If IPv6 is enabled, I'll open two sockets within a
> single vxlan_sock for metadata based vxlan, IPv4 one and IPv6 one. It
> would be easier to just open an IPv6 socket and receive both IPv4 and
> IPv6 traffic through it but unfortunately, this depends on bindv6only
> sysctl. We don't want to have IPv4 vxlan broken if bindv6only is set.
> Therefore, we need two sockets, and the IPv6 one needs to be v6only.

Awesome, sounds great.
--
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