From: Jiri Benc <jbenc@redhat.com>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: Martin Varghese <martinvarghesenokia@gmail.com>,
Network Development <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
Jonathan Corbet <corbet@lwn.net>,
scott.drennan@nokia.com, martin.varghese@nokia.com
Subject: Re: [PATCH net-next 1/2] UDP tunnel encapsulation module for tunnelling different protocols like MPLS,IP,NSH etc.
Date: Thu, 7 Nov 2019 18:31:36 +0100 [thread overview]
Message-ID: <20191107183136.466013d1@redhat.com> (raw)
In-Reply-To: <CAF=yD-JeCV-AW2HO9inJt-yePUrBGQ9=M58fYr8f2CDHdNNpaA@mail.gmail.com>
On Thu, 7 Nov 2019 11:35:07 -0500, Willem de Bruijn wrote:
> If the bareudp device binds to a specific port on all local addresses,
> which I think it's doing judging from what it passes to udp_sock_create
> (but I may very well be missing something), then in6addr_any alone will
> suffice to receive both v6 and v4 packets.
This will not work when IPv6 is disabled, either by the kernel config
or administratively. We do need to have two sockets.
Jiri
next prev parent reply other threads:[~2019-11-07 17:31 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 9:48 [PATCH net-next 0/2] Bareudp Tunnel Module Martin Varghese
2019-10-08 9:48 ` [PATCH net-next 1/2] UDP tunnel encapsulation module for tunnelling different protocols like MPLS,IP,NSH etc Martin Varghese
2019-10-08 14:06 ` Jonathan Corbet
2019-10-08 14:57 ` Randy Dunlap
2019-10-08 16:04 ` Stephen Hemminger
2019-10-08 16:05 ` Stephen Hemminger
2019-10-08 16:28 ` Willem de Bruijn
2019-10-09 12:48 ` Martin Varghese
2019-10-09 14:58 ` Willem de Bruijn
2019-10-09 15:21 ` Willem de Bruijn
2019-10-09 15:42 ` Jiri Benc
2019-10-09 16:15 ` Willem de Bruijn
2019-10-18 20:03 ` Tom Herbert
2019-10-21 17:18 ` Jiri Benc
2019-10-17 13:20 ` Martin Varghese
2019-10-17 20:48 ` Willem de Bruijn
2019-10-18 8:20 ` Martin Varghese
2019-10-18 14:59 ` Willem de Bruijn
2019-10-23 2:40 ` Martin Varghese
2019-11-07 13:38 ` Martin Varghese
2019-11-07 15:53 ` Willem de Bruijn
2019-11-07 16:12 ` Martin Varghese
2019-11-07 16:35 ` Willem de Bruijn
2019-11-07 17:31 ` Jiri Benc [this message]
2019-11-07 18:59 ` Willem de Bruijn
2019-11-07 19:05 ` Jiri Benc
2019-11-07 19:13 ` Willem de Bruijn
2019-11-11 16:02 ` Martin Varghese
2019-11-11 21:45 ` Willem de Bruijn
2019-11-14 13:17 ` Martin Varghese
2019-10-08 9:49 ` [PATCH net-next 2/2] Special handling for IP & MPLS Martin Varghese
2019-10-08 14:58 ` Randy Dunlap
2019-10-08 16:09 ` Willem de Bruijn
2019-10-09 13:38 ` Martin Varghese
2019-10-09 15:06 ` Willem de Bruijn
2019-10-09 15:19 ` Willem de Bruijn
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=20191107183136.466013d1@redhat.com \
--to=jbenc@redhat.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=martin.varghese@nokia.com \
--cc=martinvarghesenokia@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=scott.drennan@nokia.com \
--cc=willemdebruijn.kernel@gmail.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).