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
after update to v 2.6.3 the "network protection" switch (aka kill switch) does not work properly any more, when the connection is disabled (manually, or device wake-up) ... earlier versions of the client showed a message "cannot disconnect ..."and automatically re-connected, this feature does no longer work in all cases
Please note: all related settings and rules have been carefully set, reviewed, and not changed before or after update of the ivpn client, this is NOT the result of a sloppy setup by the user
Steps to reproduce:
cannot give detailed instructions, but it most often occurs when the device wakes up from sleep
the problem does not always occure
Observed Results:
client remains disconnected, sometimes a wireguard related message is shown, but not always
Expected Results:
to work like in the past with earlier versions
The text was updated successfully, but these errors were encountered:
Bug report
Describe your environment
Describe the problem
after update to v 2.6.3 the "network protection" switch (aka kill switch) does not work properly any more, when the connection is disabled (manually, or device wake-up) ... earlier versions of the client showed a message "cannot disconnect ..."and automatically re-connected, this feature does no longer work in all cases
Please note: all related settings and rules have been carefully set, reviewed, and not changed before or after update of the ivpn client, this is NOT the result of a sloppy setup by the user
Steps to reproduce:
cannot give detailed instructions, but it most often occurs when the device wakes up from sleep
the problem does not always occure
Observed Results:
client remains disconnected, sometimes a wireguard related message is shown, but not always
Expected Results:
to work like in the past with earlier versions
The text was updated successfully, but these errors were encountered: