vpn.timeout is being ignored
Hey,
I encounter large differences when it comes to the activation time of the VPN and the underlying tun device/connection "vpn0". When the activation of vpn0 takes more than 10 seconds, the activation is aborted and the the VPN connection fails.
Mär 15 23:14:16 HOSTNAME NetworkManager[20792]: <info> [1710540856.4506] vpn[0x5d5b65115aa0,c2631fb6-fc16-4b25-ade2-533e47618366,"CORPVPN"]: starting openconnect
Mär 15 23:14:16 HOSTNAME NetworkManager[20792]: <info> [1710540856.4511] audit: op="connection-activate" uuid="c2631fb6-fc16-4b25-ade2-533e47618366" name="VPN" pid=23205 uid=0 result="success"
Mär 15 23:14:26 HOSTNAME NetworkManager[20792]: <warn> [1710540866.6578] vpn[0x5d5b65115aa0,c2631fb6-fc16-4b25-ade2-533e47618366,"CORPVPN"]: failed to connect: 'Zeitüberschreitung wurde erreicht'
I'd expect that setting vpn.timeout
to a higher value (I think default is 60s) should work around that performance problem but apparently, it does not have an impact how long nm-openconnect-service (?) waits for the tun device to be ready. Can this be tweaked somehow?
Currently, I connect via passwdfile. Instant retry with same passwdfile then works most of the time.
libopenconnect5/mantic,now 9.12-1 amd64
network-manager-openconnect-gnome/mantic,now 1.2.10-1 amd64
network-manager-openconnect/mantic,now 1.2.10-1 amd64
openconnect/mantic,now 9.12-1 amd64
Thanks in advance!