Re: Timeout problems...

I had a similar problem. The problem is that the keepalives use SO_KEEPALIVE of socket option which is at least 2hrs:

/proc/sys/net/ipv4/tcp_keepalive_time == 7200 (default)

What you need to do is to patch the source with the "Heartbeat" patch at:

http://www.sc.isc.tohoku.ac.jp/~hgot/sources/openssh-watchdog.html

It sends an SSH null message periodically. This should take care of your "2 hours to reconnect" problem.

As for "up to 3 minutes to timeout", it is the TCP connection setup timeout while waiting for a syn-ack. You can play with:

/proc/sys/net/ipv4/tcp_syn_retries
/proc/sys/net/ipv4/tcp_retries1

Do you need help?

In addition to our free technical library, Pantek provides professional IT services to companies who utilize Open Source software: Learn more about Pantek's Technical Support offerings Place an order for 24/7/365 Technical Support here Learn more about Pantek, who we are, and what we do Chat with a Live Operator Related securityfocus.com Links bugtraq certification focus-bsd focus-ids focus-ih focus-linux focus-ms focus-sun focus-unix-other focus-virus forensics incidents libnet linux-secnews ms-secnews pen-test secpapers secprog sectools secureshell security-basics securityjobs sf-news vuln-dev webappsec Request more information about Pantek

to reduce this timeout. In general the default behavior should be acceptable, though.

Ramin

On Sun, May 11, 2003 at 10:39:01AM +0300, Stephen Biggs wrote:

> I am running Redhat 8.0/openssh with ssh -V:
Received on Mon May 12 12:58:17 2003