Skip to content
Disconnecting after 5 Minutes
Got a problem with Viscosity or need help? Ask here!
Hey,
I am experiencing quite the same issue but it is related to OpenVPN server route being pushed through the tunnel:
Thank you in advance, br, Jernej
I am experiencing quite the same issue but it is related to OpenVPN server route being pushed through the tunnel:
Code: Select all
The official response to this was:...
2022-06-09 20:36:51: /sbin/route add -net A.B.C.E 10.12.0.1 255.255.255.240
....
2022-06-09 20:36:52: Testing address: A.B.C.D Route points into VPN network
2022-06-09 20:36:52: Route: A.B.C.E/255.255.255.240 utun10
2022-06-09 20:36:52: Disconnecting connection as it is no longer reachable
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.I am aware of this however I do not control, which routes are pushed through the configuration. Is there a way to avoid the disconnection?
Thank you in advance, br, Jernej
Hi Jernej,
I've split your post into its own topic, as the parent topic was quite old.
We would need to see what routes are being set by the OpenVPN server, and what (if any) routes are being set locally to see what the cause is. If it is caused by a route (such as a default route) being pushed by the server, then it is possible to ignore this route in Viscosity.
We'll need more detailed information to make a recommendation. Please supply the details requested in the following article. You may prefer not to post these details on a public forum, so please feel free to email them to our support email address instead.
https://www.sparklabs.com/support/kb/ar ... ort-staff/
Cheers,
James
I've split your post into its own topic, as the parent topic was quite old.
We would need to see what routes are being set by the OpenVPN server, and what (if any) routes are being set locally to see what the cause is. If it is caused by a route (such as a default route) being pushed by the server, then it is possible to ignore this route in Viscosity.
We'll need more detailed information to make a recommendation. Please supply the details requested in the following article. You may prefer not to post these details on a public forum, so please feel free to email them to our support email address instead.
https://www.sparklabs.com/support/kb/ar ... ort-staff/
Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
2 posts
Page 1 of 1