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
I noticed the following today that the OpenVPN client was unable to reconnect when the session timed out. The the inactivity timeout occurred and the VPN connection was lost, the routes did not revert and still appear as though the VPN connection is established, which explains why it can't reconnect.
I would MUCH prefer that only the OpenVPN process have Internet connectivity when the VPN is disconnected, but it seems the routes definitely need to be reset/cleared after a timeout/disconnect in order to restore connectivity for a DNS lookup and reconnection.
Alternative: Kill the container when OpenVPN disconnects/terminates and let Docker restart it?
I found a similar issue with dperson's image and I'm wondering if the same might apply? dperson/openvpn-client#13
Logs:
Mon Jan 22 23:04:32 2018 [7b937c1bc334ae9eeb9c670627a246da] Inactivity timeout (--ping-restart), restarting
Mon Jan 22 23:04:32 2018 SIGUSR1[soft,ping-restart] received, process restarting
Mon Jan 22 23:04:34 2018 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Mon Jan 22 23:04:39 2018 RESOLVE: Cannot resolve host address: [HOST]: Try again
*** It has been scrolling the last line in the logs every 10 seconds since then.
The text was updated successfully, but these errors were encountered:
Hossy
changed the title
Unable to reconnect -- RESOLVE: Cannot resolve host address: <HOST>: Try again
Unable to reconnect -- RESOLVE: Cannot resolve host address: [HOST]: Try again
Jan 23, 2018
I noticed the following today that the OpenVPN client was unable to reconnect when the session timed out. The the inactivity timeout occurred and the VPN connection was lost, the routes did not revert and still appear as though the VPN connection is established, which explains why it can't reconnect.
I would MUCH prefer that only the OpenVPN process have Internet connectivity when the VPN is disconnected, but it seems the routes definitely need to be reset/cleared after a timeout/disconnect in order to restore connectivity for a DNS lookup and reconnection.
Alternative: Kill the container when OpenVPN disconnects/terminates and let Docker restart it?
I found a similar issue with dperson's image and I'm wondering if the same might apply? dperson/openvpn-client#13
Logs:
Mon Jan 22 23:04:32 2018 [7b937c1bc334ae9eeb9c670627a246da] Inactivity timeout (--ping-restart), restarting
Mon Jan 22 23:04:32 2018 SIGUSR1[soft,ping-restart] received, process restarting
Mon Jan 22 23:04:34 2018 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Mon Jan 22 23:04:39 2018 RESOLVE: Cannot resolve host address: [HOST]: Try again
*** It has been scrolling the last line in the logs every 10 seconds since then.
The text was updated successfully, but these errors were encountered: