netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: IPv6 multicast with VRF
Date: Wed, 20 Apr 2022 14:40:53 -0600	[thread overview]
Message-ID: <a5fdf1dc-61ef-29ba-91c3-5339c4086ec8@gmail.com> (raw)
In-Reply-To: <20220420191824.wgdh5tr3mzisalsh@skbuf>

On 4/20/22 1:18 PM, Vladimir Oltean wrote:
> On Wed, Apr 20, 2022 at 12:59:45PM -0600, David Ahern wrote:
>> Did you adjust the FIB rules? See the documentation in the kernel repo.
> 
> Sorry, I don't understand what you mean by "adjusting". I tried various
> forms of adding an IPv6 multicast route on eth0, to multiple tables,
> some routes more generic and some more specific, and none seem to match
> when eth0 is under a VRF, for a reason I don't really know. This does
> not occur with IPv4 multicast, by the way.
> 
> By documentation I think you mean Documentation/networking/vrf.rst.
> I went through it but I didn't notice something that would make me
> realize what the issue is.

try this:
    https://static.sched.com/hosted_files/ossna2017/fe/vrf-tutorial-oss.pdf
slide 79 and on

> 
>> And add a device scope to the `get`. e.g.,
>>
>>     ip -6 route get ff02::1%eth0
> 
> I'm probably not understanding this, because:
> 
>  ip -6 route get ff02::1%eth0
> Error: inet6 prefix is expected rather than "ff02::1%eth0".

ip -6 ro get oif eth0 ff02::1

(too many syntax differences between tools)

  reply	other threads:[~2022-04-20 20:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-20 16:54 IPv6 multicast with VRF Vladimir Oltean
2022-04-20 18:59 ` David Ahern
2022-04-20 19:18   ` Vladimir Oltean
2022-04-20 20:40     ` David Ahern [this message]
2022-04-21  9:24       ` Vladimir Oltean
2022-04-21 23:44         ` 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=a5fdf1dc-61ef-29ba-91c3-5339c4086ec8@gmail.com \
    --to=dsahern@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@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).