From: Jiri Benc <jbenc@redhat.com>
To: Thomas Graf <tgraf@suug.ch>
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 10:55:44 +0200 [thread overview]
Message-ID: <20150829105544.33b7799f@griffin> (raw)
In-Reply-To: <20150828223929.GC32001@pox.localdomain>
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.
Jiri
--
Jiri Benc
next prev parent reply other threads:[~2015-08-29 8:55 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
2015-08-29 8:55 ` Jiri Benc [this message]
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=20150829105544.33b7799f@griffin \
--to=jbenc@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pshelar@nicira.com \
--cc=tgraf@suug.ch \
/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).