-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Lonnie Olson wrote:
> On Wed, May 21, 2008 at 11:07 PM, Kimball Larsen
> <[EMAIL PROTECTED]> wrote:
>> I occasionally have to remotely admin a server at the office from home.
>>
>> I have it set up to only allow a few hosts access via ssh, and my home
>> static IP is on the permitted list. (using hosts.allow, hosts.deny)
>>
>> I can connect to and log into the server just fine. The session works great
>> as long as I am actively doing something in the shell. However, if I let it
>> sit idle for (it seems) < 1 minute, the session seems to just lock up.
>
> Many consumer routers/DSL modems do not handle long running SSH
> connections well. They sometimes tend to kill the connection
> prematurely. You can experiment with the SSH options TCPKeepAlive,
> and ServerAlive in the client to see if you can avoid it. However
> more often than not the problem is caused by the router itself.
>
> --lonnie
I've had pretty good success using these options in the sshd_config:
ClientAliveInterval 60
ClientAliveCountMax 3
Frank
- --
Frank Sorenson - KD7TZK
Linux Systems Engineer, DSS Engineering, UBS AG
[EMAIL PROTECTED]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAkg4woIACgkQaI0dwg4A47z6bwCffaEB9uzfvpz7x1WEjOtuQ6Tb
NIQAn3ih0EcGX8yChmw2d1ycXNjUJtgu
=r00Y
-----END PGP SIGNATURE-----
/*
PLUG: http://plug.org, #utah on irc.freenode.net
Unsubscribe: http://plug.org/mailman/options/plug
Don't fear the penguin.
*/
