On 8/21/07, blee2@tampabay.rr.com <blee2@tampabay.rr.com> wrote:
> Thus Chuck Hast hast written on Tue, Aug 21, 2007 at 08:59:09PM -0400, and, according to prophecy, it shall come to pass that:
> > I ssh into my machines at home, as long as I am active on the keyboard
> > (or browser if I use fish) there is no problem, but if I go to check e-mail or
> > do something for just a few minutes when I come back the session is froze
> > up... I have noticed that at some places where I stay, not sure if there is
> > some sort of idle timer on the router or what, the http stuff seems to always
> > respond, but if I do a ssh to something and do not keep typing or getting
> > screen updates it will lock up, any one have ideas as to what is going on?
>
> It sounds like you're connecting through a firewall. One setting on
> firewalls is to drop any TCP connections that have been idle longer
> then X. A router could be configured to do this too.
>
> HTTP doesn't really care about this, but Telnet and SSH do.
>
> Most SSH clients have a setting to send Keep Alive packet every Y seconds.
> If you're using PuTTY as your client, there is a setting in the options
> man ssh says:
> -o option
> Can be used to give options in the format used in the
> configuration file. This is useful for specifying options
> for which there is no separate command-line flag. For full
> details of the options listed below, and their possible
> values, see ssh_config(5).
> <snip>
> TCPKeepAlive
> <snip>
>
>
> TCPKeepAlive
> Specifies whether the system should send TCP keepalive messages
> to the other side. If they are sent, death of the connection or
> crash of one of the machines will be properly noticed. This
> option only uses TCP keepalives (as opposed to using ssh level
> keepalives), so takes a long time to notice when the connection
> dies. As such, you probably want the ServerAliveInterval option
> as well. However, this means that connections will die if the
> route is down temporarily, and some people find it annoying.
>
> The default is #yes# (to send TCP keepalive messages), and the
> client will notice if the network goes down or the remote host
> dies. This is important in scripts, and many users want it too.
>
> To disable TCP keepalive messages, the value should be set to
> #no#.
>
> You could also cheat and run something that updates regularly, like top or cmatrix...:-)
>
> Plug for screen:
>
> The program "screen" let's you multiplex a terminal...you can run
> multiple shells. I have one for mutt and others for shells. It also
> let's you detach a screen session and log out, then login someplace else
> and resume your existing session.
I went into the config file and added TCPKeepAlive, let me see what that
does for it.
-- Chuck Hast -- KP4DJT -- To paraphrase my flight instructor; "the only dumb question is the one you DID NOT ask resulting in my going out and having to identify your bits and pieces in the midst of torn and twisted metal." ----------------------------------------------------------------------- This list is provided as an unmoderated internet service by Networked Knowledge Systems (NKS). Views and opinions expressed in messages posted are those of the author and do not necessarily reflect the official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 18:40:34 EDT