From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "M. Dietrich" <mdt@emdete.de>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Defaultroutepiercing
Date: Thu, 18 Jan 2018 14:02:45 +0100 [thread overview]
Message-ID: <CAHmME9oiqr7dN+riRgJ0jXxxwuXB0U9ot94GsoM7KUWGbEE-0Q@mail.gmail.com> (raw)
In-Reply-To: <1516279577.16nr5x0y18.astroid@morple.none>
Take a look at what wg-quick does to solve this:
https://git.zx2c4.com/WireGuard/tree/src/tools/wg-quick.bash#n162
It uses policy routing, which is much nicer than overriding the default rou=
te.
If, however, you do with to do it the old 0/1, 128/1 way, here's a
script to automate that: https://=D7=90.cc/gvFOR5BO/bash But I'd recommend
doing the trick that wg-quick does.
next prev parent reply other threads:[~2018-01-18 12:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 13:00 Defaultroutepiercing M. Dietrich
2018-01-18 13:02 ` Jason A. Donenfeld [this message]
2018-01-18 14:11 ` Defaultroutepiercing M. Dietrich
2018-01-18 14:20 ` Defaultroutepiercing Jason A. Donenfeld
2018-01-18 14:44 ` Defaultroutepiercing M. Dietrich
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=CAHmME9oiqr7dN+riRgJ0jXxxwuXB0U9ot94GsoM7KUWGbEE-0Q@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=mdt@emdete.de \
--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).