From: Thomas Graf <tgraf@suug.ch>
To: Jiri Benc <jbenc@redhat.com>
Cc: netdev@vger.kernel.org, Pravin Shelar <pshelar@nicira.com>
Subject: Re: [PATCH v2 net-next 4/4] vxlan: do not receive IPv4 packets on IPv6 socket
Date: Sat, 29 Aug 2015 00:39:29 +0200 [thread overview]
Message-ID: <20150828223929.GC32001@pox.localdomain> (raw)
In-Reply-To: <823880925bf39790189708fcb7f7158f21231237.1440787601.git.jbenc@redhat.com>
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@redhat.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?
next prev parent reply other threads:[~2015-08-28 22:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 18:48 [PATCH v2 net-next 0/4] tunnels: fix incorrect IPv4/v6 headers interpretation Jiri Benc
2015-08-28 18:48 ` [PATCH v2 net-next 1/4] ip_tunnels: convert the mode field of ip_tunnel_info to flags Jiri Benc
2015-08-28 22:15 ` Thomas Graf
2015-08-28 22:55 ` Pravin Shelar
2015-08-28 18:48 ` [PATCH v2 net-next 2/4] ip_tunnels: record IP version in tunnel info Jiri Benc
2015-08-28 22:24 ` Thomas Graf
2015-08-29 8:43 ` Jiri Benc
2015-08-28 22:55 ` Pravin Shelar
2015-08-28 18:48 ` [PATCH v2 net-next 3/4] fou: reject IPv6 config Jiri Benc
2015-08-28 18:48 ` [PATCH v2 net-next 4/4] vxlan: do not receive IPv4 packets on IPv6 socket Jiri Benc
2015-08-28 22:39 ` Thomas Graf [this message]
2015-08-29 8:55 ` Jiri Benc
2015-08-30 9:30 ` Thomas Graf
2015-08-29 20:08 ` [PATCH v2 net-next 0/4] tunnels: fix incorrect IPv4/v6 headers interpretation 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=20150828223929.GC32001@pox.localdomain \
--to=tgraf@suug.ch \
--cc=jbenc@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pshelar@nicira.com \
/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).