Re: ssh timeouts

["Curtis H. Wilbar Jr." <bsd@hawkmountain.net>]

This doesn't belong on tech@... so this is cc'd to misc@ where it
should be moved to...

I've solved the problem with firewalls timing out the state for
ssh connections that are idle longer than the firewall keeps
states by adding the following to /etc/ssh/sshd_config on boxes
you ssh into:

ClientAliveInterval     60

If you don't control the box you ssh into, then all you can do is
contact whomever runs the system and see if they will be kind enough
to add this.

-- Curt


On Mon, 2004-02-02 at 13:27, Anthony Roberts wrote:
> >"Jan 30 13:24:38 knight sshd[23215]: Disconnecting:
> >Timeout, your sessionnot responding."
> 
> I get this all the time when I log in to home from work, and some friends 
> have this problem logging in to my computer from behind the university's 
> firewall. It happens because their firewall/nat drops the connection after 
> the connection has been idle for a given period. I don't know why that would 
> happen on a Windows machine on the physical network. Something is making 
> idle connections time out on Windows computers, and I don't think it's your 
> client software. It's probably either firewall software or Windows itself. 
> It occurs to me that the Windows network stack might actually have been 
> altered to time out idle connections all by itself, so they don't have to 
> fix other parts of the OS that are being sloppy. I don't know, but I 
> wouldn't be surprised either way.
> 
> In either case, something is timing out the connection. The workaround is to 
> enable client side keepalive signals. This can be done in Putty in the 
> connection properties. I don't know about other software, but it can 
> probably do it too.
> 
> _________________________________________________________________
> MSN 8 with e-mail virus protection service: 2 months FREE*  
> http://join.msn.com/?page=features/virus&pgmarket=en-ca&RU=http%3a%2f%2fjoin.msn.com%2f%3fpage%3dmisc%2fspecialoffers%26pgmarket%3den-ca