You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a VPN session is being brought up, we should wait for the session to come up before returning. We could do this by listening to a dynamically generated status file (that is passed into the openvpn config) or by querying the management socket.
If I call up multiple times on the same remote server the client becomes out of state because it will overwrite the existing PID file, try to start another OpenVPN client, and then discover that it cannot start a new connection, as another connection is already running. Since the PID file has been overwritten, the associated OpenVPN client becomes a "zombie", unmanageable by the wrapper tools.
When a VPN session is being brought up, we should wait for the session to come up before returning. We could do this by listening to a dynamically generated status file (that is passed into the openvpn config) or by querying the management socket.
If I call
upmultiple times on the same remote server the client becomes out of state because it will overwrite the existing PID file, try to start another OpenVPN client, and then discover that it cannot start a new connection, as another connection is already running. Since the PID file has been overwritten, the associated OpenVPN client becomes a "zombie", unmanageable by the wrapper tools.