From: David Ahern <dsahern@gmail.com>
To: Jeff Barnhill <0xeffeff@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: v6/sit tunnels and VRFs
Date: Sun, 29 Oct 2017 09:48:21 -0600 [thread overview]
Message-ID: <abb3291a-222a-7eff-724c-9d06fea9f02d@gmail.com> (raw)
In-Reply-To: <CAL6e_pcL3DF1J1-+w0pw0CZ=Zm_BRfKtz=5jML_GcZBZFW1JVA@mail.gmail.com>
On 10/27/17 8:43 PM, Jeff Barnhill wrote:
> ping v4 loopback...
>
> jeff@VM2:~$ ip route list vrf myvrf
> 127.0.0.0/8 dev myvrf proto kernel scope link src 127.0.0.1
> 192.168.200.0/24 via 192.168.210.3 dev enp0s8
> 192.168.210.0/24 dev enp0s8 proto kernel scope link src 192.168.210.2
>
> Lookups shown in perf script were for table 255. Is it necessary to
> put the l3mdev table first? If I re-order the tables, it starts
> working:
Yes, we advise moving the local table down to avoid false hits (e.g.,
duplicate addresses like this between the default VRF and another VRF).
I covered that and a few other things at OSS 2017. Latest VRF slides for
users:
http://schd.ws/hosted_files/ossna2017/fe/vrf-tutorial-oss.pdf
next prev parent reply other threads:[~2017-10-29 15:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 20:45 v6/sit tunnels and VRFs Jeff Barnhill
2017-10-25 21:31 ` David Ahern
2017-10-26 3:28 ` Jeff Barnhill
2017-10-26 17:24 ` David Ahern
2017-10-27 5:19 ` Jeff Barnhill
2017-10-27 16:25 ` David Ahern
2017-10-27 20:59 ` Jeff Barnhill
2017-10-27 22:53 ` David Ahern
2017-10-28 2:43 ` Jeff Barnhill
2017-10-29 15:48 ` David Ahern [this message]
2017-10-31 22:20 ` Jeff Barnhill
2017-10-31 22:36 ` David Ahern
2017-10-31 22:42 ` David Ahern
2018-04-12 16:54 ` Jeff Barnhill
2018-04-13 2:25 ` David Ahern
2018-04-13 20:23 ` Jeff Barnhill
2018-04-13 20:31 ` David Ahern
2018-04-14 22:07 ` Jeff Barnhill
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=abb3291a-222a-7eff-724c-9d06fea9f02d@gmail.com \
--to=dsahern@gmail.com \
--cc=0xeffeff@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).