Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Maximilian Wilhelm <max@sdn.clinic>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard and VRFs?
Date: Fri, 15 Sep 2017 04:17:20 +0200	[thread overview]
Message-ID: <CAHmME9oy6P6Uu1Ua=heozE8LsfFK2OPUtLwLa7e4N_QypjvqHg@mail.gmail.com> (raw)
In-Reply-To: <20170915005255.GA5107@principal.rfc2324.org>

Hi Max,

Yes, WireGuard supports this type of functionality through two more
powerful mechanisms:

- fwmark, so you can do proper policy-based routing via `ip rule` with
multiple tables
- network namespace, so that you can have the udp socket in one
namespace and the actual interface in another

I imagine what you want is the fwmark feature, which seems to match up
with much of the language used in vrf.txt. Check out the wg(8) manpage
for details.

Regards,
Jason

  reply	other threads:[~2017-09-15  1:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-15  0:52 Maximilian Wilhelm
2017-09-15  2:17 ` Jason A. Donenfeld [this message]
2017-09-20  3:12 Florian Werner
2017-09-20 10:01 ` Jörg Thalheim

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='CAHmME9oy6P6Uu1Ua=heozE8LsfFK2OPUtLwLa7e4N_QypjvqHg@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --cc=max@sdn.clinic \
    --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).