netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: abauvin@scaleway.com
Cc: dsa@cumulusnetworks.com, roopa@cumulusnetworks.com,
	stephen@networkplumber.org, netdev@vger.kernel.org,
	akherbouche@scaleway.com
Subject: Re: [PATCH v6 1/4] udp_tunnel: add config option to bind to a device
Date: Fri, 30 Nov 2018 13:15:37 -0800 (PST)	[thread overview]
Message-ID: <20181130.131537.2038374142327178570.davem@davemloft.net> (raw)
In-Reply-To: <20181127130545.54356-2-abauvin@scaleway.com>

From: Alexis Bauvin <abauvin@scaleway.com>
Date: Tue, 27 Nov 2018 14:05:42 +0100

> UDP tunnel sockets are always opened unbound to a specific device. This
> patch allow the socket to be bound on a custom device, which
> incidentally makes UDP tunnels VRF-aware if binding to an l3mdev.
> 
> Signed-off-by: Alexis Bauvin <abauvin@scaleway.com>
> Reviewed-by: Amine Kherbouche <akherbouche@scaleway.com>
> Reviewed-by: David Ahern <dsahern@gmail.com>
> Tested-by: Amine Kherbouche <akherbouche@scaleway.com>

Please address Sabrina's feedback and respin this series.

Thanks.

  parent reply	other threads:[~2018-12-01  8:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-27 13:05 [PATCH v6 0/4] Add VRF support for VXLAN underlay Alexis Bauvin
2018-11-27 13:05 ` [PATCH v6 1/4] udp_tunnel: add config option to bind to a device Alexis Bauvin
2018-11-30 14:31   ` Sabrina Dubroca
2018-12-03  9:14     ` Alexis Bauvin
2018-11-30 21:15   ` David Miller [this message]
2018-11-27 13:05 ` [PATCH v6 2/4] l3mdev: add function to retreive upper master Alexis Bauvin
2018-11-27 13:05 ` [PATCH v6 3/4] vxlan: add support for underlay in non-default VRF Alexis Bauvin
2018-11-27 13:05 ` [PATCH v6 4/4] test/net: Add script for VXLAN underlay in a VRF Alexis Bauvin

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=20181130.131537.2038374142327178570.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=abauvin@scaleway.com \
    --cc=akherbouche@scaleway.com \
    --cc=dsa@cumulusnetworks.com \
    --cc=netdev@vger.kernel.org \
    --cc=roopa@cumulusnetworks.com \
    --cc=stephen@networkplumber.org \
    /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).