Package: openfortivpn Version: 1.21.0-1 Severity: normal Dear Maintainer,
On a Debian Sid system, after upgrading from 1.20.5-1 and activating a previously working VPN config, I am not able to connect (ssh) any host by IP or name. And downgrading to 1.20.5-1 solves this. I do not see any message in the journal log that may be different from the working version. Unless that systemd-resolved is then not able to connect the VPN DNS. Looking at the upstream issues, may be this is something new?! Regards, Patrice -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'unstable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-4-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 openfortivpn depends on: ii libc6 2.37-12 ii libssl3 3.0.12-2 ii libsystemd0 255~rc2-2 ii ppp 2.4.9-1+1.1+b1 openfortivpn recommends no packages. Versions of packages openfortivpn suggests: ii systemd-resolved [resolvconf] 255~rc2-2 -- Configuration Files: /etc/openfortivpn/config [Errno 13] Permission non accordée: '/etc/openfortivpn/config' -- no debconf information
