aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/src/send.c
diff options
context:
space:
mode:
authorJason A. Donenfeld <Jason@zx2c4.com>2017-05-22 13:28:02 +0200
committerJason A. Donenfeld <Jason@zx2c4.com>2017-05-30 18:07:28 +0200
commitc7ac9b4e66e613446a323de53ff9d2b34a936d66 (patch)
treef67ceb132a105f9c7028f42a9f1ecc456f308a29 /src/send.c
parentchacha20poly1305: add NEON versions for ARM and ARM64 (diff)
downloadwireguard-monolithic-historical-c7ac9b4e66e613446a323de53ff9d2b34a936d66.tar.xz
wireguard-monolithic-historical-c7ac9b4e66e613446a323de53ff9d2b34a936d66.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?
Diffstat (limited to 'src/send.c')
0 files changed, 0 insertions, 0 deletions