Do not close OpenVPN sessions when using Wireguard protocol Planned
We are using Wireguard with Timus and a separate OpenVPN client, when clicking Disconnect in Timus the OpenVPN client closes. We have been told that this is by design, regardless of which protocol Timus is using it always terminates all OpenVPN processes as part of the disconnect cycle.
This is poor design and should be changed. It is disruptive to the client and makes it appear that Timus is causing application crashes. Their previous VPN solution had no such interoperation issues with OpenVPN client.
Even if Timus were to be using the OpenVPN protocol, it should be possible for multiple OpenVPN sessions to be established simultaneously. Timus should be tracking the PID for the OpenVPN client sessions that it is establishing and managing, and only terminate that PID when disconnecting.
Comments
1 comment
Improvements planned for this. No ETA as of yet.
Please sign in to leave a comment.