Package: network-manager-ssh Version: 1.2.11-1 Severity: normal Hello,
on a Debian system with /bin/sh pointing to dash network-manager-ssh incorrectly decides that tap0 is available for use as a local interface. When tap0 is in use by some other application this results in inability to connect to the ssh-based VPN. My expectation is that network-manager-ssh should be able to find an unused tap interface name regardless of the default shell type. I have reported it and proposed a fix to the upstream here: https://github.com/danfruehauf/NetworkManager-ssh/pull/105/commits/82b4217e89e1abb5554609c6096b2e21c4e4eab2 -- System Information: Debian Release: 11.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-11-amd64 (SMP w/8 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages network-manager-ssh depends on: ii libc6 2.31-13+deb11u3 ii libglib2.0-0 2.66.8-1 ii libnm0 1.30.0-2 ii openssh-client 1:8.4p1-5 ii sshpass 1.09-1+b1 Versions of packages network-manager-ssh recommends: ii network-manager-ssh-gnome 1.2.11-1 network-manager-ssh suggests no packages. -- no debconf information -- Thanks. -- Max
