[Savannah-hackers] [support #103027] premature ssh timeouts on slow connections

[Sylvain Beucler]

This mail is an automated notification from the support tracker
 of the project: Savannah Administration.

/**************************************************************************/
[support #103027] Latest Modifications:

Changes by: 
                Sylvain Beucler <address@hidden>
'Date: 
                Sat 04/24/04 at 20:04 (Europe/Paris)

            What     | Removed                   | Added
---------------------------------------------------------------------------
         Assigned to | None                      | Beuc


------------------ Additional Follow-up Comments ----------------------------
Hello,

The current settings are ClientAliveInterval 30 and ClientAliveCountMax to 
default (3), hence the 90 seconds I guess :)

I do not understand your suggestion to set it to 15, as an unreachable client 
would be killed in 45 seconds.
I am also puzzled to see that your connection can be 'inactive' for more than 
one minute.
Is there something I missed?

Thanks.







/**************************************************************************/
[support #103027] Full Item Snapshot:

URL: <http://savannah.gnu.org/support/?func=detailitem&item_id=103027>
Project: Savannah Administration
Submitted by: Karl Berry
On: Fri 04/23/04 at 21:59

Category:  None
Priority:  5 - Normal
Severity:  3 - Ordinary
Resolution:  None
Assigned to:  Beuc
Originator Email:  address@hidden
Status:  Open


Summary:  premature ssh timeouts on slow connections

Original Submission:  I unfortunately had to move to a satellite-based Internet 
connection, since nothing else was available in my area.  It has very slow 
upload speeds with a large latency.  

Since moving, I've found that cvs updates in larger hierarchies, namely 
/webcvs/texinfo, usually die after approximately 90 seconds with the message:
Received disconnect from 199.232.41.3: 2: Timeout, your session not responding.

It will occasionally run to completion, occasionally time out sooner, etc.  
I've tried everything I can think of on the client side to affect this: 
ServerAliveInterval, ServerAliveCountMax, TCPKeepAlive, and more, but nothing 
has made any difference.

On the server side, setting ClientAliveInterval 15 (or some such) in 
sshd_config seems like the most likely thing to help, although I obviously 
don't know for sure.

Are you willing and able to try to help with this?  I don't know if anyone else 
is on a satellite connection; I doubt anyone on real broadband or even dialup 
would have the problem.

Thanks.



Follow-up Comments
------------------


-------------------------------------------------------
Date: Sat 04/24/04 at 20:04         By: Beuc
Hello,

The current settings are ClientAliveInterval 30 and ClientAliveCountMax to 
default (3), hence the 90 seconds I guess :)

I do not understand your suggestion to set it to 15, as an unreachable client 
would be killed in 45 seconds.
I am also puzzled to see that your connection can be 'inactive' for more than 
one minute.
Is there something I missed?

Thanks.













For detailed info, follow this link:
<http://savannah.gnu.org/support/?func=detailitem&item_id=103027>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/