From: Daniele Orlandi <daniele@orlandi.com>
To: wireguard@lists.zx2c4.com
Subject: Re: Tunnel traffic in VRF
Date: Sat, 25 Jan 2020 15:10:42 +0100 [thread overview]
Message-ID: <38df62df-2c77-48b1-f020-48a410ff381e@orlandi.com> (raw)
In-Reply-To: <ea889cc3-9599-4218-a8cc-6daa9d2965e2@www.fastmail.com>
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.
In the meantime I was able to find a workaround by setting the sysctl
variable:
net.ipv4.udp_l3mdev_accept=1
this way the socket that is created in the default VRF is automatically
visible in all VRFs.
A proper binding to the correct VRF would be a better approach, however.
Regards,
--
Daniele Orlandi
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2020-01-25 14:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 0:03 Tunnel traffic in VRF 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 [this message]
2020-01-25 16:03 ` b13253
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=38df62df-2c77-48b1-f020-48a410ff381e@orlandi.com \
--to=daniele@orlandi.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).