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 currently have the latest stable version of Qubes OS running on a laptop that I put to sleep and wake frequently.
When the laptop is asleep for more a little while (long enough for the vpn connection to time out I presume) and woken up the VPN does not try to reconnect. There are no log entries for the vpn services stating anything after wake.
The message stating that all traffic was blackholed due to connection loss does come up but after that nothing and no internet.
The text was updated successfully, but these errors were encountered:
On 01/13/2017 01:36 PM, SentinelX101 wrote:
I currently have the latest stable version of Qubes OS running on a
laptop that I put to sleep and wake frequently.
When the laptop is asleep for more a little while (long enough for the
vpn connection to time out I presume) and woken up the VPN does not
try to reconnect. There are no log entries for the vpn services
stating anything after wake.
The message stating that all traffic was blackholed due to connection
loss does come up but after that nothing and no internet.
Thank you for the bug report. Sometimes you must restart openvpn in the
VPN VM by killing it. I think it's a bug in openvpn — thinks it's still
connected, does nothing tho. I am interested in solutions to the
problem. Perhaps a watchdog will be necessary.
I currently have the latest stable version of Qubes OS running on a laptop that I put to sleep and wake frequently.
When the laptop is asleep for more a little while (long enough for the vpn connection to time out I presume) and woken up the VPN does not try to reconnect. There are no log entries for the vpn services stating anything after wake.
The message stating that all traffic was blackholed due to connection loss does come up but after that nothing and no internet.
The text was updated successfully, but these errors were encountered: