resolvconf was dropped from Ubuntu due to its incompatibility with Ubuntu's default systemd-resolved setup (LP: #1990743).
There was some discussion/request at upstream WireGuard about supporting systemd's resolvectl as an alternative to resolvconf from inside wg- quick. But it looks like that was rejected: https://lists.zx2c4.com/pipermail/wireguard/2019-September/004520.html The systemd-resolved is installed by default in Ubuntu (including the resolvconf compat symlink), as also discussed and implemented in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939904 So IMO any integration issues should either be handled by upstream WireGuard (using systemd's resolvectl) or by upstream systemd (increasing resolvconf compatibility). One more note: In the bug reports referenced above, people usually call the "resolvconf" command on the "wg0" interface directly, that was created for the tunnel. Not "tun.wg0". How does your setup behave when calling "resolvconf -a wg0 -m 0 -x" instead? ** Bug watch added: Debian Bug tracker #939904 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939904 ** Changed in: wireguard (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2092329 Title: wg-quick fails with systemd resolvconf compatibility shim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireguard/+bug/2092329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
