Inactivity timeout?

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

col_harris

Posts: 2
Joined: Tue Nov 17, 2009 9:50 pm

Post by col_harris » Tue Nov 17, 2009 10:30 pm
I've been using Viscosity for awhile now but just recently I've started having problems with it dropping out. It reconnects fine but it's fairly annoying. I've checked the logs (see below) and it seems to be restarting every 3 minutes, well 3 minutes of inactivity.

Can anyone tell me how to change this? Can I stop this restart or at least make the time longer like 30 minutes? Is this a server side option of a client option?

Any help would be appreciated.

cheers

Col.

Tue Nov 17 10:14:50 2009: [...] Inactivity timeout (--ping-restart), restarting
Tue Nov 17 10:14:50 2009: /Applications/Viscosity.app/Contents/Resources/dnsdown.py tun0 1500 1542 10.3.212.18 10.3.212.17 restart
Tue Nov 17 10:14:50 2009: SIGUSR1[soft,ping-restart] received, process restarting
Tue Nov 17 10:14:50 2009: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Tue Nov 17 10:14:50 2009: Re-using SSL/TLS context
Tue Nov 17 10:14:50 2009: LZO compression initialized
Tue Nov 17 10:14:50 2009: UDPv4 link local: [undef]
Tue Nov 17 10:14:50 2009: UDPv4 link remote: 203.94.158.49:24789
Tue Nov 17 10:14:50 2009: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Tue Nov 17 10:14:57 2009: [...] Peer Connection Initiated with 203.94.158.49:24789
Tue Nov 17 10:14:59 2009: Preserving previous TUN/TAP instance: tun0
Tue Nov 17 10:14:59 2009: /Applications/Viscosity.app/Contents/Resources/dnsup.py tun0 1500 1542 10.3.212.18 10.3.212.17 restart
Tue Nov 17 10:14:59 2009: Initialization Sequence Completed
Tue Nov 17 10:17:57 2009: [etglvpn.etechgroup.com.au] Inactivity timeout (--ping-restart), restarting
Tue Nov 17 10:17:57 2009: /Applications/Viscosity.app/Contents/Resources/dnsdown.py tun0 1500 1542 10.3.212.18 10.3.212.17 restart
Tue Nov 17 10:17:57 2009: SIGUSR1[soft,ping-restart] received, process restarting
Tue Nov 17 10:17:57 2009: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Tue Nov 17 10:17:57 2009: Re-using SSL/TLS context
Tue Nov 17 10:17:57 2009: LZO compression initialized
Tue Nov 17 10:17:57 2009: UDPv4 link local: [undef]
Tue Nov 17 10:17:57 2009: UDPv4 link remote: 203.94.158.49:24789
Tue Nov 17 10:17:57 2009: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Tue Nov 17 10:18:05 2009: [...] Peer Connection Initiated with 203.94.158.49:24789
Tue Nov 17 10:18:07 2009: Preserving previous TUN/TAP instance: tun0
Tue Nov 17 10:18:07 2009: /Applications/Viscosity.app/Contents/Resources/dnsup.py tun0 1500 1542 10.3.212.18 10.3.212.17 restart
Tue Nov 17 10:18:07 2009: Initialization Sequence Completed

col_harris

Posts: 2
Joined: Tue Nov 17, 2009 9:50 pm

Post by col_harris » Thu Nov 19, 2009 9:05 am
bump

Any suggestions?? Please?

James

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

Post by James » Thu Nov 19, 2009 10:20 pm
Hi Col,

You'll need to have a play with the "Ping" and "Ping-restart" fields, which are under the Options tab when editing your connection in Viscosity. For example, try setting a Ping value of 10, and a Ping-restart value of 3600.

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