From: "b13253@gmail.com" <b13253@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Re: Tunnel traffic in VRF
Date: Sun, 26 Jan 2020 00:03:33 +0800 [thread overview]
Message-ID: <CA+7UkwKDJdPvWSNA1ECAPUBYh2oDxsyDC9twkFSph2mA-=a1TQ@mail.gmail.com> (raw)
In-Reply-To: <38df62df-2c77-48b1-f020-48a410ff381e@orlandi.com>
On Sat, Jan 25, 2020 at 10:10 PM Daniele Orlandi <daniele@orlandi.com> wrote:
>
> On 25/01/2020 07:55, Steven Honson wrote:
> > Hi Daniele,
> >
> > By VRFs, do you mean Linux network namespaces, or something different?
>
> They are a different feature. In short VRFs are separate routing tables
> to provide routing isolation. They are somewhat different with respect
> to namespaces as the isolation is visible to userspace.
Hi Daniele,
VRF is different from network namespaces.
I have collected some materials about the VRF implementation of Linux:
- https://schd.ws/hosted_files/ossna2017/fe/vrf-tutorial-oss.pdf
(Slides introducing VRF)
- https://cumulusnetworks.com/blog/vrf-for-linux/ (Article describing
the differences among VRF, ip rule, and namespace)
Hope they help.
Best regards,
StarBrilliant
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2020-01-30 2:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 0:03 Daniele Orlandi
2020-01-25 6:55 ` Steven Honson
2020-01-25 9:13 ` Toke Høiland-Jørgensen
2020-01-25 14:10 ` Daniele Orlandi
2020-01-25 16:03 ` b13253 [this message]
2020-01-26 19:46 ` Serge
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='CA+7UkwKDJdPvWSNA1ECAPUBYh2oDxsyDC9twkFSph2mA-=a1TQ@mail.gmail.com' \
--to=b13253@gmail.com \
--cc=wireguard@lists.zx2c4.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).