From: David Ahern <dsahern@gmail.com>
To: Mike Manning <mmanning@vyatta.att-mail.com>, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v5 4/9] net: provide a sysctl raw_l3mdev_accept for raw socket lookup with VRFs
Date: Wed, 7 Nov 2018 12:07:01 -0700 [thread overview]
Message-ID: <05dd6127-34e5-9872-ac86-74520e1fd943@gmail.com> (raw)
In-Reply-To: <20181107153610.7526-5-mmanning@vyatta.att-mail.com>
On 11/7/18 8:36 AM, Mike Manning wrote:
> Add a sysctl raw_l3mdev_accept to control raw socket lookup in a manner
> similar to use of tcp_l3mdev_accept for stream and of udp_l3mdev_accept
> for datagram sockets. Have this default to enabled for reasons of
> backwards compatibility. This is so as to specify the output device
> with cmsg and IP_PKTINFO, but using a socket not bound to the
> corresponding VRF. This allows e.g. older ping implementations to be
> run with specifying the device but without executing it in the VRF.
> If the option is disabled, packets received in a VRF context are only
> handled by a raw socket bound to the VRF, and correspondingly packets
> in the default VRF are only handled by a socket not bound to any VRF.
>
> Signed-off-by: Mike Manning <mmanning@vyatta.att-mail.com>
> ---
> Documentation/networking/ip-sysctl.txt | 12 ++++++++++++
> Documentation/networking/vrf.txt | 13 +++++++++++++
> include/net/netns/ipv4.h | 3 +++
> include/net/raw.h | 1 +
> net/ipv4/af_inet.c | 2 ++
> net/ipv4/raw.c | 28 ++++++++++++++++++++++++++--
> net/ipv4/sysctl_net_ipv4.c | 11 +++++++++++
> 7 files changed, 68 insertions(+), 2 deletions(-)
Reviewed-by: David Ahern <dsahern@gmail.com>
Tested-by: David Ahern <dsahern@gmail.com>
next prev parent reply other threads:[~2018-11-08 4:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 15:36 [PATCH net-next v5 0/9] vrf: allow simultaneous service instances in default and other VRFs Mike Manning
2018-11-07 15:36 ` [PATCH net-next v5 1/9] net: allow binding socket in a VRF when there's an unbound socket Mike Manning
2018-11-07 19:06 ` David Ahern
2018-11-07 15:36 ` [PATCH net-next v5 2/9] net: ensure unbound stream socket to be chosen when not in a VRF Mike Manning
2018-11-07 19:06 ` David Ahern
2018-11-07 15:36 ` [PATCH net-next v5 3/9] net: ensure unbound datagram " Mike Manning
2018-11-07 19:06 ` David Ahern
2018-11-07 15:36 ` [PATCH net-next v5 4/9] net: provide a sysctl raw_l3mdev_accept for raw socket lookup with VRFs Mike Manning
2018-11-07 19:07 ` David Ahern [this message]
2018-11-07 15:36 ` [PATCH net-next v5 5/9] net: fix raw socket lookup device bind matching " Mike Manning
2018-11-07 19:07 ` David Ahern
2018-11-07 15:36 ` [PATCH net-next v5 6/9] vrf: mark skb for multicast or link-local as enslaved to VRF Mike Manning
2018-11-07 19:07 ` David Ahern
2018-11-07 15:36 ` [PATCH net-next v5 7/9] ipv6: allow ping to link-local address in VRF Mike Manning
2018-11-07 19:07 ` David Ahern
2018-11-07 15:36 ` [PATCH net-next v5 8/9] ipv6: handling of multicast packets received " Mike Manning
2018-11-07 19:08 ` David Ahern
2018-11-07 15:36 ` [PATCH net-next v5 9/9] ipv6: do not drop vrf udp multicast packets Mike Manning
2018-11-07 19:08 ` David Ahern
2018-11-08 0:13 ` [PATCH net-next v5 0/9] vrf: allow simultaneous service instances in default and other VRFs 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=05dd6127-34e5-9872-ac86-74520e1fd943@gmail.com \
--to=dsahern@gmail.com \
--cc=mmanning@vyatta.att-mail.com \
--cc=netdev@vger.kernel.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).