On 5/18/06, kelsey hudson <[EMAIL PROTECTED]> wrote:
Carl Lowenstein wrote:
> Frequently I log in by ssh to a remote computer. If I don't keep
> using the connection, after a few minutes I get the message
> " Read from remote host deeptow: Connection reset by peer
> Connection to deeptow closed."
Being that you're behind a NAT router (read from another message), this
is almost certainly a translation timeout problem. I used to have the
same problem at work -- the stupid NAT devices (PIX firewalls) have a
translation timeout of 1.5 hours, and I often hit it.
Add the following to your personal or system-wide ssh configuration file:
TCPKeepAlive yes
ServerAliveInterval 30
ServerAliveCountMax 3
That way it pings the server every 30 seconds. If, after a minute and a
half, the machine doesn't respond, the connection is dropped. This also
has the benefit of keeping translation entries open.
<rant>
This is just one of the many reasons why NAT is a pain in the ass. We
have a suitable fix: IPv6 -- let's use it.
</rant>
Try that, and your problem should get a nice band-aid. :)
This seems to have cured the problem. The next question is: why are
these ssh configuration parameters not mentioned in ssh_coinfig(5) or
in /etc/ssh/ssh_config? Maybe there is other documentation for ssh.
(OpenSSH)?
Why does my Netgear WGR614 do this to me? Looking at the Netgear user
forum, it appears that others have similar problems with a 10-minute
inactivity timeout. It is reported that changing to a different
revision of firmware may or may not solve the problem. That is such a
confidence-building statement.
carl
--
carl lowenstein marine physical lab u.c. san diego
[EMAIL PROTECTED]
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
