netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: netdev@vger.kernel.org
Cc: David Ahern <dsahern@gmail.com>
Subject: [PATCH net-next 0/2] net: vrf: Support for local traffic with sockets bound to enslaved devices
Date: Fri, 11 Aug 2017 17:11:13 -0700	[thread overview]
Message-ID: <1502496675-13349-1-git-send-email-dsahern@gmail.com> (raw)

This set gets local traffic working for sockets bound to enslaved
devices. The local rtable and rt6_info added in June 2016 to get
local traffic in VRFs working is no longer needed and actually
keeps local traffic for sockets bound to an enslaved device from
working. Patch 1 removes them.

Patch 2 adds a fix up for IPv4 IP_PKTINFO to return rt_iif for
packets sent over the VRF device. This is similar to the handling
of loopback.

David Ahern (2):
  net: vrf: Drop local rtable and rt6_info
  net: ipv4: add check for l3slave for index returned in IP_PKTINFO

 drivers/net/vrf.c      | 122 ++++---------------------------------------------
 net/ipv4/ip_sockglue.c |   3 +-
 2 files changed, 10 insertions(+), 115 deletions(-)

-- 
2.1.4

             reply	other threads:[~2017-08-12  0:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-12  0:11 David Ahern [this message]
2017-08-12  0:11 ` [PATCH net-next 1/2] net: vrf: Drop local rtable and rt6_info David Ahern
2017-08-12  0:11 ` [PATCH net-next 2/2] net: ipv4: add check for l3slave for index returned in IP_PKTINFO David Ahern
2017-08-14  3:05 ` [PATCH net-next 0/2] net: vrf: Support for local traffic with sockets bound to enslaved devices 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=1502496675-13349-1-git-send-email-dsahern@gmail.com \
    --to=dsahern@gmail.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).