Package: wireguard-tools Version: 1.0.20210914-1+b1 Severity: normal File: /usr/bin/wg-quick
Dear Maintainer, I have been using wg-quick in combination with resolvconf and the option SaveConfig=true to make a tunnel between two hosts. After some time the connection was no longer established; there were too many DNS-lines /etc/wireguard/wg0.conf. When wg-quick saves the configuration for a tunnel it uses "resolvconf -l <interface>" to list the DNS configuration for a specific interface, however the version of the resolvconf program in the package resolvconf does noet support this. Consequently wg-quick saves the nameservers supplied with the tunnel as well as all the other ones and the configuration file grows every time the tunnel is brought down e.g. when powering off the system. Using openresolv rather than resolvconf solves the issue, so arguably this is a bug in resolvconf rather than in wg-quick. I have not tried it with systemd-resolved. As long as this has not been fixed, I think wireguard-tools should document this behaviour somewhere and stop suggesting resolvconf. Kind regards, Arnold Metselaar -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (555, 'testing'), (550, 'stable'), (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'oldstable-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-2-amd64 (SMP w/3 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8), LANGUAGE=nl Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages wireguard-tools depends on: ii libc6 2.36-8 Versions of packages wireguard-tools recommends: ii iptables 1.8.9-2 ii linux-image-amd64 [wireguard-modules] 6.1.8-1 ii nftables 1.0.6-2 Versions of packages wireguard-tools suggests: ii resolvconf 1.91+nmu1 -- no debconf information
