From: "M. Dietrich" <mdt@emdete.de>
To: wireguard@lists.zx2c4.com
Subject: Defaultroutepiercing
Date: Thu, 18 Jan 2018 14:00:11 +0100 [thread overview]
Message-ID: <1516279577.16nr5x0y18.astroid@morple.none> (raw)
[-- Attachment #1: Type: text/plain, Size: 883 bytes --]
in case i want to use a vpn to route all my traffic through
the tunnel i have a kind of hen&egg problem: how does my
client contact the other side if i switch the default route?
the demo script adds a route to the other side in the
moment of establishing the connection like this:
163.172.161.0 via 192.168.0.1 dev wlan0
(assuming 192.168.0.1 is my router). this goes well as long as
the router (or the interface) doesnt change. this is fine for
most VPNs as they fail when the connection is lost.
wireguard is ment for the modern world and survives connection
drops. but the route must be reestablished afterwords in case
router or interface changed.
is there a solution to automate that already? i know this is
not really a wireguard topic as it has to be done near dhcp.
this should have been solved for android already or am i
wrong?
M. Dietrich
[-- Attachment #2: Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2018-01-18 12:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 13:00 M. Dietrich [this message]
2018-01-18 13:02 ` Defaultroutepiercing Jason A. Donenfeld
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=1516279577.16nr5x0y18.astroid@morple.none \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.