From: David Ahern <dsahern@gmail.com>
To: Ben Greear <greearb@candelatech.com>, netdev <netdev@vger.kernel.org>
Subject: Re: VRF notes when using ipv6 and flushing tables.
Date: Tue, 20 Aug 2019 23:02:57 -0400 [thread overview]
Message-ID: <2a8914bb-56ec-e585-bd76-36b77ca2517d@gmail.com> (raw)
In-Reply-To: <8977a25e-29c1-5375-cc97-950dc7c2eb0f@candelatech.com>
On 8/20/19 2:27 PM, Ben Greear wrote:
> I recently spend a few days debugging what in the end was user error on
> my part.
>
> Here are my notes in hope they help someone else.
>
> First, 'ip -6 route show vrf vrfX' will not show some of the
> routes (like local routes) that will show up with
> 'ip -6 route show table X', where X == vrfX's table-id
>
> If you run 'ip -6 route flush table X', then you will loose all of the auto
> generated routes, including anycast, ff00::/8, and local routes.
>
> ff00::/8 is needed for neigh discovery to work (probably among other
> things)
>
> local route is needed or packets won't actually be accepted up the stack
> (I think that is the symptom at least)
>
> Not sure exactly what anycast does, but I'm guessing it is required for
> something useful.
>
> You must manually re-add those to the table unless you for certain know
> that
> you do not need them for whatever reason.
>
sorry you went through such a long and painful debugging session.
yes, the kernel doc for VRF needs to be updated that 'ip route show vrf
X' and 'ip route show table X' are different ('show vrf' mimics the main
table in not showing local, broadcast, anycast; 'table vrf' shows all).
A suggestion for others: the documentation and selftests directory have
a lot of VRF examples now. If something basic is not working (e.g., arp
or neigh discovery), see if it works there and if so compare the outputs
of the route table along the way.
next prev parent reply other threads:[~2019-08-21 3:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 18:27 VRF notes when using ipv6 and flushing tables Ben Greear
2019-08-21 3:02 ` David Ahern [this message]
2019-08-21 20:20 ` Ben Greear
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=2a8914bb-56ec-e585-bd76-36b77ca2517d@gmail.com \
--to=dsahern@gmail.com \
--cc=greearb@candelatech.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).