From owner-freebsd-questions@FreeBSD.ORG Thu Nov 13 21:40:58 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 97035106567A for ; Thu, 13 Nov 2008 21:40:58 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from mail.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id 5E9178FC1A for ; Thu, 13 Nov 2008 21:40:58 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from localhost (mail.rachie.is-a-geek.net [192.168.2.101]) by mail.rachie.is-a-geek.net (Postfix) with ESMTP id 7D7AAAFC1C7; Thu, 13 Nov 2008 12:40:57 -0900 (AKST) From: Mel To: freebsd-questions@freebsd.org Date: Thu, 13 Nov 2008 22:40:52 +0100 User-Agent: KMail/1.9.7 References: <491C9C44.90406@gmail.com> In-Reply-To: <491C9C44.90406@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200811132240.54269.fbsd.questions@rachie.is-a-geek.net> Cc: Forrest Aldrich Subject: Re: SSH timeouts from remote connections on 7.1beta X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2008 21:40:58 -0000 On Thursday 13 November 2008 22:29:40 Forrest Aldrich wrote: > This is a recent phenomenon. > > I use a Mac client (iTerm) to connect to all my hosts internally. Same > network. My connections to the FreeBSD-7.1.x system continually timeout > when idle, and I have to re-connect (thankfully, I use "screen"). It's > becoming annoying, and though I've set TcpKeepAlive, it still happens. ServerAliveInterval client side is what you're looking for. =46rom ssh_config(5): ServerAliveCountMax Sets the number of server alive messages (see below) which may= be sent without ssh(1) receiving any messages back from the serve= r. If this threshold is reached while server alive messages are being sent, ssh will disconnect from the server, terminating t= he session. It is important to note that the use of server alive messages is very different from TCPKeepAlive (below). The ser= ver alive messages are sent through the encrypted channel and ther= e- fore will not be spoofable. The TCP keepalive option enabled = by TCPKeepAlive is spoofable. The server alive mechanism is valu- able when the client or server depend on knowing when a connec- tion has become inactive. The default value is 3. If, for example, ServerAliveInterval (see below) is set to 15 and ServerAliveCountMax is left at the default, if the server becomes unresponsive, ssh will disconne= ct after approximately 45 seconds. This option applies to protoc= ol version 2 only. ServerAliveInterval Sets a timeout interval in seconds after which if no data has been received from the server, ssh(1) will send a message thro= ugh the encrypted channel to request a response from the server. = The default is 0, indicating that these messages will not be sent = to the server. This option applies to protocol version 2 only. =2D-=20 Mel Problem with today's modular software: they start with the modules and never get to the software part.