diff options
author | Jason A. Donenfeld <Jason@zx2c4.com> | 2017-05-22 13:28:02 +0200 |
---|---|---|
committer | Jason A. Donenfeld <Jason@zx2c4.com> | 2017-05-30 18:07:28 +0200 |
commit | f65fba7dd8fe401d9e40d89ccdc85bb3bf162c83 (patch) | |
tree | cdb36701f80d520361479871aaf2c84dc90c6869 /contrib/external-tests | |
parent | wg-quick: use src routing for default routes in v6 (diff) | |
download | wireguard-tools-f65fba7dd8fe401d9e40d89ccdc85bb3bf162c83.tar.xz wireguard-tools-f65fba7dd8fe401d9e40d89ccdc85bb3bf162c83.zip |
man: update wg-quick(8) to show Debian resolvconf braindamage
While OpenResolv supports explicit ordering directives such as `-m` and
exclusivity directives such as `-x`, Debian's own resolvconf supports
none of this, instead using a hard coded list of interface name
templates for determining ordering. While trying to emulate `-x` is
difficult [*], we can at least try to mostly emulate `-m 0` by
masquerading as a `tun*` interface to resolvconf. Ugly, but it works.
[*] One heavy handed way of emulating `-x` would be something like:
# echo nameserver 8.8.8.8 > /etc/resolv.conf.wg0-exclusive
# mount --bind -o ro /etc/resolv.conf.wg0-exclusive /etc/resolv.conf
# rm -f /etc/resolv.conf.wg0-exclusive
This in practice works quite well, but is a bit heavy to put in a man
page. It also doesn't "stack" well. For example, if we simply run
`umount /etc/resolv.conf`, how do we know which resolv.conf entry we're
unmounting?
Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
Diffstat (limited to 'contrib/external-tests')
0 files changed, 0 insertions, 0 deletions