Connection fails after a while

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

AlexK

Posts: 8
Joined: Fri Jul 17, 2009 8:08 pm

Post by AlexK » Tue Oct 20, 2009 6:07 pm
Hi,
I am running Viscosity 1.0.6 on Snow Leopard 10.6.1 and I have the problem, that Viscosity disconnects after running for a few hours and then fails to reconnect. However, it reconnects just fine, if I manually tell it to.
The error message is printed below. (In this case the failure and the manual reconnect are hours apart, but it also is reproducible only minutes after the failure.)
Code: Select all
Tue Oct 20 02:42:49 2009: TLS Error: local/remote TLS keys are out of sync: 74.115.162.17:1194 [6]
Tue Oct 20 02:42:50 2009: NOTE: --mute triggered...
Tue Oct 20 02:43:37 2009: 121 variation(s) on previous 20 message(s) suppressed by --mute
Tue Oct 20 02:43:37 2009: [vpn] Inactivity timeout (--ping-restart), restarting
Tue Oct 20 02:43:37 2009: /Users/alex/Applications/Viscosity.app/Contents/Resources/dnsdownalt.py tun0 1500 1542 10.157.6.126 10.157.6.125 restart
Tue Oct 20 02:43:39 2009: script failed: external program exited with error status: 1
Tue Oct 20 07:56:42 2009: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Tue Oct 20 07:56:42 2009: LZO compression initialized
Tue Oct 20 07:56:42 2009: RESOLVE: NOTE: vpn.uk.witopia.net resolves to 8 addresses, choosing one by random
Tue Oct 20 07:56:42 2009: UDPv4 link local: [undef]
Tue Oct 20 07:56:42 2009: UDPv4 link remote: 74.115.162.10:1194
Tue Oct 20 07:56:44 2009: [vpn] Peer Connection Initiated with 74.115.162.10:1194
Tue Oct 20 07:56:45 2009: TUN/TAP device /dev/tun0 opened
Tue Oct 20 07:56:45 2009: /sbin/ifconfig tun0 delete
Tue Oct 20 07:56:45 2009: NOTE: Tried to delete pre-existing tun/tap instance -- No Problem if failure
Tue Oct 20 07:56:45 2009: /sbin/ifconfig tun0 10.150.0.222 10.150.0.221 mtu 1500 netmask 255.255.255.255 up
Tue Oct 20 07:56:45 2009: /Users/alex/Applications/Viscosity.app/Contents/Resources/dnsupalt.py tun0 1500 1542 10.150.0.222 10.150.0.221 init
Tue Oct 20 07:56:46 2009: Initialization Sequence Completed
----

And on a completely unrelated note. About two weeks back, I had problems connecting and found out that for some reason the tun.kext and tap.kext extensions where missing on my system, so I reinstalled them manually. After a restart Viscosity complained that these components are outdated and offered to upgrade them. Everything is running fine since then. I still have no idea why all of a sudden those extensions might have been gone.

James

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

Post by James » Wed Oct 21, 2009 3:00 am
Hi AlexK,

Do you still have the same problem with the latest beta version of Viscosity? This can be downloaded at:
http://www.viscosityvpn.com/forum/viewt ... p?f=7&t=34
I still have no idea why all of a sudden those extensions might have been gone.
Viscosity now stores the TUN/TAP kernel extensions inside its application bundle (which allows us to easily include new versions of the drivers when they become available), rather than in the Extensions & Startup Items directories. Viscosity now just loads the drivers when opened, and unloads them when quit (so Viscosity places nicely with other VPN clients like Cisco AnyConnect).

Cheers,
James
James Bekkema
Viscosity Developer

Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs

AlexK

Posts: 8
Joined: Fri Jul 17, 2009 8:08 pm

Post by AlexK » Sat Oct 24, 2009 6:19 pm
Hi James,
that seems to have done the trick. I will keep an eye on it. Thank you for this great program and your support.
3 posts Page 1 of 1