From: David Miller <davem@davemloft.net>
To: dsahern@kernel.org
Cc: netdev@vger.kernel.org, dsahern@gmail.com
Subject: Re: [PATCH net] net/ipv6: Fix linklocal to global address with VRF
Date: Sat, 21 Jul 2018 19:32:36 -0700 (PDT) [thread overview]
Message-ID: <20180721.193236.2034280150310979114.davem@davemloft.net> (raw)
In-Reply-To: <20180719194118.25346-1-dsahern@kernel.org>
From: dsahern@kernel.org
Date: Thu, 19 Jul 2018 12:41:18 -0700
> From: David Ahern <dsahern@gmail.com>
>
> Example setup:
> host: ip -6 addr add dev eth1 2001:db8:104::4
> where eth1 is enslaved to a VRF
>
> switch: ip -6 ro add 2001:db8:104::4/128 dev br1
> where br1 only has an LLA
>
> ping6 2001:db8:104::4
> ssh 2001:db8:104::4
>
> (NOTE: UDP works fine if the PKTINFO has the address set to the global
> address and ifindex is set to the index of eth1 with a destination an
> LLA).
>
> For ICMP, icmp6_iif needs to be updated to check if skb->dev is an
> L3 master. If it is then return the ifindex from rt6i_idev similar
> to what is done for loopback.
>
> For TCP, restore the original tcp_v6_iif definition which is needed in
> most places and add a new tcp_v6_iif_l3_slave that considers the
> l3_slave variability. This latter check is only needed for socket
> lookups.
>
> Fixes: 9ff74384600a ("net: vrf: Handle ipv6 multicast and link-local addresses")
> Signed-off-by: David Ahern <dsahern@gmail.com>
Applied and queued up for -stable.
> Dave: I can look at the backports to stable if needed.
Please do, that will help me a lot.
next prev parent reply other threads:[~2018-07-22 3:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 19:41 [PATCH net] net/ipv6: Fix linklocal to global address with VRF dsahern
2018-07-22 2:32 ` David Miller [this message]
2018-07-24 17:23 ` David Ahern
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=20180721.193236.2034280150310979114.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=dsahern@kernel.org \
--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).