Defaultroutepiercing

[M. Dietrich]

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.zx2c4.com/pipermail/wireguard/attachments/20180118/294e1927/attachment.asc>