no default gateway

Got a problem with Viscosity or need help? Ask here!

francesco

Posts: 3
Joined: Mon Nov 16, 2020 5:42 am

Post by francesco » Mon Nov 16, 2020 5:49 am
HI, to all,
I am testing viscosity as an alternative to tunnelblick client for my company.
I have a very simple problem.

When I terminate the connection, my MAC has not anymore the default gateway.
Of course I can stop/start my wifi and I get it back, but doing that I kill all other connections I have.

We had the same issue with tunneblick, and there we solved it using the provided down-root module.

How to do the same in viscosity?

Thx Francesco

James

User avatar
Posts: 2313
Joined: Thu Sep 04, 2008 9:27 pm

Post by James » Mon Nov 16, 2020 3:55 pm
Hi Francesco,

Please see the following support article:
https://www.sparklabs.com/support/kb/ar ... connected/

Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs

francesco

Posts: 3
Joined: Mon Nov 16, 2020 5:42 am

Post by francesco » Tue Nov 17, 2020 4:13 am
Hi James,
thx for your reply.

I read that article before posting here.

I have not problems with addresses and the idea of either resetting the interface or the network card is really not nice.

When I close the VPN it may be I have (many) other links active and they would be reset!

As a user, I would expect the MAC at the end of a VPN having same network configuration I had before starting it.
And having to write "my script" sounds incredible to me.
If this is viscosity standard behaviour, I have to say it does not cover our needs.
Just let me know, thank you

Bye Francesco

francesco

Posts: 3
Joined: Mon Nov 16, 2020 5:42 am

Post by francesco » Sat Nov 21, 2020 4:15 am
Just to finally check: there is not any viscosity standard solution to my problem?
Something similar to the down-root of tunnelblick?
Thx Francesco

James

User avatar
Posts: 2313
Joined: Thu Sep 04, 2008 9:27 pm

Post by James » Tue Nov 24, 2020 8:25 pm
Hi Francesco,

The problem is caused by a configuration issue: the OpenVPN server is pushing out a route that clashes with the routes already on the local machine. For example, the default route is being pushed instead of using "redirect-gateway def1", or the VPN network is using the same IP range as the user's network. The article linked earlier goes into more detail.

The "Reset network interfaces on disconnect" option is presented as a work-around. The better solution is to fix the routing clash and ensure you're not pushing the default route manually.

Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
5 posts Page 1 of 1