Package: network-manager-openconnect Version: 1.2.10-3+b1 Severity: normal Dear Maintainer, proper MTU is not being set on the tunnel device when connecting to a cisco anyconnect server. Value of 1396 is always being set.
This does not produce any ill effects as long as actual MTU is equal or greater than 1396. For example, on an ISP with wired connection openconnect detects MTU 1399 and everything works fine. On a mobile ISP MTU may be choked, openconnect detects MTU 1390 and provides INTERNAL_IP4_MTU=1390 in the environment it sends to nm-openconnect-service-openconnect-helper. But since it is being ignored, default 1395 value results in partial failures when accessing resources through the tunnel. Setting the correct value manually via 'ip link set' resolves connectivity issues. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (900, 'unstable'), (300, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.8.9-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_AUX Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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 network-manager-openconnect depends on: ii adduser 3.137 ii libc6 2.38-11 ii libglib2.0-0t64 2.80.2-1 ii libnm0 1.46.0-2 ii libopenconnect5 9.12-1+b2 ii network-manager 1.46.0-2 ii openconnect 9.12-1+b2 network-manager-openconnect recommends no packages. network-manager-openconnect suggests no packages. -- no debconf information
