Viscosity + Tunnelblick = lost internet conn. on disconnect

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

filipp

Posts: 16
Joined: Wed Feb 24, 2010 5:48 pm

Post by filipp » Wed Feb 24, 2010 6:19 pm
This is more of a heads up for those like me who are comparing Viscosity and Tunnelblick and hence running them on the same machine, than a support issue. Just a couple of things people might run into:

1. You can't use the other when the other one is running. This is obvious because they both use the same OpenVPN kext. Maybe Viscosity should actually unload them every time it's loaded?

2. You might lose connectivity after a disconnect if you run the two on the same machine at some point in time. The exact steps to reproduce are:
- Open VPN connection in Viscosity
- Close the connection and Viscosity
- Check that internet connection is still working (it should be)
- Open and close Tunnelblick
- Open Viscosity and your VPN connection
- Disconnect, check internet connectivity
- You should get an error. To fix it, renew your DHCP lease (or enable/disable the interface).

At first I thought this was a Viscosity bug or routing issue (it looks exactly like http://www.viscosityvpn.com/support/?se ... pportid=15, but my local net is 192.168.2.0/28 and remote is 172.17.67.0/24) but then I noticed it didn't happen every time and was able to narrow it down to Tunnelblick being open at some point. Viscosity's "Reset network interfaces on disconnect" helps, but I would like to avoid using it.

I think this has something to do with Tunnelblick's "Monitor connection" feature. I've noticed there's a launchd job still running after Tunnelblick has been closed. The "complete solution" (at least for me) has been to reboot and only use Viscosity. :-)

Btw, my comparison lead me to buying Viscosity and I'll be recommending it to all my customers as well. ;-)

Viscosity 1.0.9 and Tunnelbick 3.0b26.

Hopefully this'll prove useful to someone else as well.

James

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

Post by James » Wed Feb 24, 2010 7:19 pm
Hi filipp,

Thanks for posting - I'm sure others will find it very useful!
Maybe Viscosity should actually unload them every time it's loaded?
Viscosity attempts to load it's own kexts when launched, and unload any others that may clash. However if these are in use (e.g. another application like Tunnelblick has an active connection), they can't be unloaded until the connection is disconnected.

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

filipp

Posts: 16
Joined: Wed Feb 24, 2010 5:48 pm

Post by filipp » Sun Mar 14, 2010 6:32 pm
Thanks :)
3 posts Page 1 of 1