1.5.3


Old Stuff

 www.your-freedom.net
 www.secure-tunnel.com

Ticket #6 (closed enhancement: fixed)

Opened 3 years ago

Last modified 2 years ago

SSH session needs to employ TCPKeepAlive option

Reported by: admin Assigned to: andrei
Priority: low Milestone: AlmostVPN 0.9.8
Component: PreferencePanel Version: 0.9
Severity: normal Keywords:
Cc:

Description

Initially it is OK to have it always ON. Eventually, need to be able to turn it on/off

Change History

09/14/05 15:11:47 changed by admin

  • status changed from new to assigned.
  • milestone changed from AlmostVPN 0.9 Beta 2 to AlmostVPN 0.9 Beta 3.

Milestone corrected

09/14/05 21:39:19 changed by admin

  • priority changed from normal to low.
  • severity changed from normal to enhancement.
  • milestone changed from AlmostVPN 0.9 Beta 3 to AlmostVPN 1.0.

Starting with Beta 3 each ssh session will employ "TCPKeepAlive" option. Ability to turn it on/off deferred until post 0.9 GA

10/06/05 09:51:42 changed by andrei

  • owner changed from admin to andrei.
  • status changed from assigned to new.

NOTE: Panther shipped with version of ssh which does not support TCPKeepAlive option. AlmostVPN on Panther does not use it.

12/29/05 07:49:35 changed by andrei

  • cc deleted.
  • status changed from new to assigned.
  • milestone changed from AlmostVPN 1.0 to AlmostVPN 0.9.8.

On Tiger need to switch from TCPKeepAlive to ServerAliveInterval/ServerAliveCountMax?

12/30/05 10:52:06 changed by andrei

As of 0.9.8 AlmostVPN on Tiger employes two more options:

so as a result complete command line looks like this 

ssh... -o ConnectTimeout=xxx -o TCPKeepAlive=yes -o ServerAliveInterval=15 -o ServerAliveCountMax=4...

NOTE It looks like Panther does support TCP Keep Alive functionality. The only thing which is different is that name of the option is KeepAlive? (vs TCPKeepAlive on Tiger). In both cases (Tiger and Pather) this option is ON by default, so "-o TCPKeepAlive=yes" is not really necessary. Unfortunately, Panther does NOT support ServerAlive... options.

12/30/05 10:54:06 changed by andrei

  • status changed from assigned to closed.
  • resolution set to fixed.

This issue is not going to be addressed any further with AlmostVPN. Any additional fixes will be implemented only as part of AlmostVPNPro.