On 5/19/06, Carl Lowenstein <[EMAIL PROTECTED]> wrote:
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."
>
> 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.
>
This seems to have cured the problem. The next question is: why are
these ssh configuration parameters not mentioned in ssh_config(5) or
in /etc/ssh/ssh_config? Maybe there is other documentation for ssh.
(OpenSSH)?
Partial answer here. The ssh_config documentation seems to lag the
software by about one release. ServerAliveInterval and friends are
discussed in ssh_config(5) for the next major release of ssh, which I
haven't started to use yet.
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.
I now have the "official" reply from Netgear Customer Service. They
suggest disabling Stateful Packet Inspection (SPI). I think I would
rather have ssh ping the connection every so often to keep it alive.
That has now worked for a couple of days without disconnecting.
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
