Defaultroutepiercing

[M. Dietrich]

Quotation from Jason A. Donenfeld at Januar 18, 2018 14:02:
>  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 route.
> 
> If, however, you do with to do it the old 0/1, 128/1 way, here's a
> script to automate that: https://א.cc/gvFOR5BO/bash But I'd recommend
> doing the trick that wg-quick does.

thank you for directing me there - i did not recognize that
wg-quick adds functionality.

using it gives some troubles here with DNS. i use a home grown
script for resolveconf (i do not change the file
/etc/resolv.conf but use dbus to tell dnsmasq the current
nameserver). wg-quick issues a

	[#] resolvconf -a tun.wg0 -m 0 -x

which seems to be wrong, the manpage resolvconf(8) states that the
this parameter is

	interface[.protocol]

why is "tun." prepended?

the command is issued before the routing is configured.
shouldnt the DNS configuration be applied after routing
changes?

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/13a9ace4/attachment.asc>