Kill switch?
Posted: Mon Jan 28, 2019 11:35 am
Hi,
I recently had Viscosity unexpectedly disconnect from my VPN and so my IP address was exposed, which is not a good thing. Obviously, I'd like to prevent this from happening again in the future.
I found this thread from 2015, where Eric says a kill switch is in the making.
viewtopic.php?f=9&t=1778
Is there any news on this?
I am also aware that there is a script solution to prevent network leaks:
https://www.sparklabs.com/support/kb/ar ... fic-leaks/
Unfortunately, this isn't really useful for me, as I only use Viscosity occasionally. I would need something that only kicks in when the network connection drops, but not when I terminate it manually.
Last but not least, I am posting log from when I was disconnected. No idea if "no usable connection profiles" points at a problem with the VPN or something with Viscosity, but if its the latter, maybe it hints at some software bug that can be fixed. Thanks!
Jan 24 23:38:07: Status changed to connected
Jan 25 00:24:24: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #392846 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jan 25 00:24:24: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #392847 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jan 25 00:24:24: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #392848 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jan 25 00:24:24: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #392849 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jan 25 00:24:24: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #392850 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jan 25 00:26:55: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #575096 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jan 25 04:22:27: [VPN] Inactivity timeout (--ping-restart), restarting
Jan 25 04:22:27: SIGUSR1[soft,ping-restart] received, process restarting
Jan 25 04:22:27: Status changed to connecting
Jan 25 04:22:28: Checking remote host "***vpn.com" is reachable...
Jan 25 04:22:37: Checking remote host "***vpn.com" is reachable...
Jan 25 04:22:46: No usable connection profiles are present
Jan 25 04:22:46: Exiting due to fatal error
Jan 25 04:22:46: Exiting due to fatal error
Jan 25 04:22:46: Status changed to disconnected
I recently had Viscosity unexpectedly disconnect from my VPN and so my IP address was exposed, which is not a good thing. Obviously, I'd like to prevent this from happening again in the future.
I found this thread from 2015, where Eric says a kill switch is in the making.
viewtopic.php?f=9&t=1778
Is there any news on this?
I am also aware that there is a script solution to prevent network leaks:
https://www.sparklabs.com/support/kb/ar ... fic-leaks/
Unfortunately, this isn't really useful for me, as I only use Viscosity occasionally. I would need something that only kicks in when the network connection drops, but not when I terminate it manually.
Last but not least, I am posting log from when I was disconnected. No idea if "no usable connection profiles" points at a problem with the VPN or something with Viscosity, but if its the latter, maybe it hints at some software bug that can be fixed. Thanks!
Jan 24 23:38:07: Status changed to connected
Jan 25 00:24:24: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #392846 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jan 25 00:24:24: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #392847 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jan 25 00:24:24: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #392848 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jan 25 00:24:24: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #392849 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jan 25 00:24:24: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #392850 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jan 25 00:26:55: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #575096 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jan 25 04:22:27: [VPN] Inactivity timeout (--ping-restart), restarting
Jan 25 04:22:27: SIGUSR1[soft,ping-restart] received, process restarting
Jan 25 04:22:27: Status changed to connecting
Jan 25 04:22:28: Checking remote host "***vpn.com" is reachable...
Jan 25 04:22:37: Checking remote host "***vpn.com" is reachable...
Jan 25 04:22:46: No usable connection profiles are present
Jan 25 04:22:46: Exiting due to fatal error
Jan 25 04:22:46: Exiting due to fatal error
Jan 25 04:22:46: Status changed to disconnected