vpnc-script does not remove routes after sleep in Mac OS

[auzhva]

Description of the Issue

If you're connected to VPN, and close the laptop, making it go sleep, after it wakes up, connection to VPN will be broken. Still "utun" device and routes through it will be there.

Reconnect attempt to VPN will fail, because routes are already present.

The only things that can help are rebooting computer or issuing route -n flush command (multiple times), and reconnection to the network.

Specifications

• Version: 1.5.x
• Platform: Mac OS X

Steps to Reproduce the Issue

1. Connect to Cisco VPN
2. Put computer asleep for a period long enough that connection lease will expire and reconnect attempt will fail
3. Wake computer

Expected Behavior

All routes are clean, reconnect is working

Actual Behavior

Routes are present at the system, reconnect doesn't work. Reboot or route -n flush is required

Other Information

Can provide more details upon request if needed, and if you would say what exactly is needed :)

[horar]

I'm expecting that on reconnect failuer a disconnect should be triggered in app i.e. disconnect in vpnc script as well.
Could you please try console version of 'openconnect' then we will know if it is generic issue with openconnect library or an issue in gui. Thanks.

[auzhva]

Hi,

Tried with console - same effect.

[ilyadnlv]

Hey there!

I'm having absolutely the same issue. Currently I use OpenConnect version v7.08 in console mode.

[horar]

Hi, thanks for update! From this information, the sleep/wakeup support should be discussed in upstream openconnect/vpnc project, mailing list. Then it will be solved in GUI & console as well. In my opinion hacking an workaround in GUI won't be good idea (yes, I should to check openconnect-console on windows too to get more info if it is only macOS issue or all platform issue).

[auzhva]

Ok,

Is e-mail thread already available? Or do I need to report it there?

[horar]

Please report it. I'm not aware if someone already open discussion about this in last months.