Package: openconnect Version: 9.12-3.3 Severity: important When I interrupted openconnect with Ctrl-C (thus SIGINT), the previous network status was not restored: it still had the VPN route and DNS server. Since the DNS server was available only in the VPN, this broke DNS resolution completely.
Some journalctl output... I launched the command to start the VPN at 19:25:05. The VPN was started at 19:25:10. And at 19:25:55, I did a Ctrl-C. Mar 30 19:25:05 qaa sudo[1015866]: pam_unix(sudo:session): session opened for user root(uid=0) by vinc17(uid=1000) Mar 30 19:25:10 qaa NetworkManager[1429]: <info> [1774891510.1798] manager: (tun0): new Tun device (/org/freedesktop/NetworkManager/Devices/8) Mar 30 19:25:10 qaa NetworkManager[1429]: <info> [1774891510.2156] device (tun0): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'external') Mar 30 19:25:10 qaa NetworkManager[1429]: <info> [1774891510.2168] device (tun0): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'external') Mar 30 19:25:10 qaa NetworkManager[1429]: <info> [1774891510.2171] device (tun0): Activation: starting connection 'tun0' (1c91cb47-11bd-4fd9-a46b-499e5b96e828) Mar 30 19:25:10 qaa NetworkManager[1429]: <info> [1774891510.2172] device (tun0): state change: disconnected -> prepare (reason 'none', managed-type: 'external') Mar 30 19:25:10 qaa NetworkManager[1429]: <info> [1774891510.2174] device (tun0): state change: prepare -> config (reason 'none', managed-type: 'external') Mar 30 19:25:10 qaa NetworkManager[1429]: <info> [1774891510.2175] device (tun0): state change: config -> ip-config (reason 'none', managed-type: 'external') Mar 30 19:25:10 qaa NetworkManager[1429]: <info> [1774891510.2176] device (tun0): state change: ip-config -> ip-check (reason 'none', managed-type: 'external') Mar 30 19:25:10 qaa dbus-daemon[1285]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.15' (uid=0 pid=1429 comm="/usr/sbin/NetworkManager --no-daemon") Mar 30 19:25:10 qaa systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service... Mar 30 19:25:10 qaa dbus-daemon[1285]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Mar 30 19:25:10 qaa systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service. Mar 30 19:25:10 qaa NetworkManager[1429]: <info> [1774891510.2582] device (tun0): state change: ip-check -> secondaries (reason 'none', managed-type: 'external') Mar 30 19:25:10 qaa NetworkManager[1429]: <info> [1774891510.2583] device (tun0): state change: secondaries -> activated (reason 'none', managed-type: 'external') Mar 30 19:25:10 qaa NetworkManager[1429]: <info> [1774891510.2586] device (tun0): Activation: successful, device activated. Mar 30 19:25:20 qaa systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Mar 30 19:25:55 qaa sudo[1015866]: pam_unix(sudo:session): session closed for user root Mar 30 19:25:55 qaa NetworkManager[1429]: <info> [1774891555.3377] device (tun0): state change: activated -> unmanaged (reason 'unmanaged', managed-type: 'removed') Mar 30 19:25:55 qaa dbus-daemon[1285]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.15' (uid=0 pid=1429 comm="/usr/sbin/NetworkManager --no-daemon") Mar 30 19:25:55 qaa systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service... Mar 30 19:25:55 qaa dbus-daemon[1285]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Mar 30 19:25:55 qaa systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service. Mar 30 19:26:05 qaa systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Unfortunately I haven't kept the output since I noticed the issue too late. This was the first time I got such an issue. -- System Information: Debian Release: forky/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.7.12-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages openconnect depends on: ii libc6 2.42-13 ii libgnutls30t64 3.8.12-3 ii libopenconnect5 9.12-3.3 ii libproxy1v5 0.5.12-1 ii libxml2-16 2.15.2+dfsg-0.1 ii vpnc-scripts 0.1~git20220510-1+local1 Versions of packages openconnect recommends: ii python3 3.13.9-3 ii python3-asn1crypto 1.5.1-3 ii python3-mechanize 1:0.4.10+ds-7 ii python3-netifaces 0.11.0-2+b7 Versions of packages openconnect suggests: ii bash-completion 1:2.16.0-8 ii xdg-utils 1.2.1-2 -- no debconf information -- Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)
