Bug#988809: resolvconf: error when attempting Wireguard connection. Unknown interface 'tun': No such device
Package: resolvconf Version: 1.79 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? executing wireguard command wg-quick up [server] * What exactly did you do (or not do) that was effective (or ineffective)? The problem was resolved by modifying the .conf file to comment out the DNS field * What was the outcome of this action? The connection attempt was successful * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: 10.9 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.4.107-1.fc25.qubes.x86_64 (SMP w/1 CPU core) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages resolvconf depends on: ii debconf [debconf-2.0] 1.5.71 ii ifupdown 0.8.35 ii init-system-helpers1.56+nmu1 ii lsb-base 10.2019051400 resolvconf recommends no packages. resolvconf suggests no packages. -- Configuration Files: /etc/resolvconf/resolv.conf.d/head changed [not included] -- debconf information: resolvconf/reboot-recommended-after-removal: resolvconf/link-tail-to-original: false resolvconf/linkify-resolvconf: true resolvconf/downup-interfaces:
Bug#988809: resolvconf: error when attempting Wireguard connection. Unknown interface 'tun': No such device
Hi, On Wed, 19 May 2021, at 22:11, librelifer wrote: > Attachments: > * encrypted.asc I don’t read encrypted private messages from unknown people. Please keep the discussion to the bug tracker. -- Cheers, Andrej
Bug#988809: resolvconf: error when attempting Wireguard connection. Unknown interface 'tun': No such device
Control: tag -1 moreinfo Hi, On Wed, 19 May 2021, at 21:30, ad wrote: >* What led up to the situation? executing wireguard command wg-quick > up [server] >* What exactly did you do (or not do) that was effective (or > ineffective)? The problem was resolved by modifying the .conf file > to comment out the DNS field >* What was the outcome of this action? The connection attempt was > successful >* What outcome did you expect instead? I don’t understand what’s the error, what did you do or how did it go away, could you please provide more details? Thanks! -- Cheers, Andrej
