SparkLabs Forum.

Community Help.


Disconnecting after 5 Minutes

Hello,

we are using Viscosity for years now. On one device i have an issue that it disconnects on is own after 5 minutes.
It seems to make some kind of connection test or something, fails on it and then decides to disconnect the connect ( while it is actually working )

The initial connection works without issues. I obfuscated <PUBLIC_IP> which is he public ip of the VPN gateway. We are using OpenVPN - other clients / users have no issue.

The device is a desktop, connected over cable. Internet Connection is 100% stable.

Code: Select all

2018-11-29 10:04:24: /sbin/ifconfig utun1 10.246.246.6 10.246.246.6 netmask 255.255.255.0 mtu 1500 up
2018-11-29 10:04:24: Initialization Sequence Completed
2018-11-29 10:04:24: DNS mode set to Split
2018-11-29 10:04:24: State changed to Connected
2018-11-29 10:09:16: Testing address: <PUBLIC_IP> Route points into VPN network
2018-11-29 10:09:16: Route: 0.0.0.0/0.0.0.0 utun1
2018-11-29 10:09:16: Disconnecting connection as it is no longer reachable
2018-11-29 10:09:16: State changed to Disconnecting
2018-11-29 10:09:17: State changed to Disconnected


Do you have any idea? Thanks
Hi xordish,

This error indicates that the external IP address of the VPN server is being routed into the VPN tunnel itself. This results in a non-functioning VPN connection. The reason for this seems to be as there is a 0.0.0.0/0 route for the VPN connection: if this is being set by the VPN connection itself it is *not* recommended. If a 0.0.0.0/0 route route is being manually set or pushed by the OpenVPN server it should be replaced with the "redirect-gateway def1" command. If you're already pushing "redirect-gateway", ensure it has the "def1" parameter.

2018-11-29 10:09:16: Testing address: <PUBLIC_IP> Route points into VPN network
2018-11-29 10:09:16: Route: 0.0.0.0/0.0.0.0 utun1
2018-11-29 10:09:16: Disconnecting connection as it is no longer reachable


As for why this is happening after around 5 minutes, my guess is that something else on the machine is triggering a network change. It's also possible the DHCP lease time on the local network could be set to a very low value.

Cheers,
James
2 posts Page 1 of 1

Copyright © 2016 SparkLabs Pty Ltd. All Rights Reserved. Privacy Policy