From owner-freebsd-questions@FreeBSD.ORG Wed May 13 13:11:12 2009 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 6B82F106567A for ; Wed, 13 May 2009 13:11:12 +0000 (UTC) (envelope-from tajudd@gmail.com) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.24]) by mx1.freebsd.org (Postfix) with ESMTP id 1F0848FC17 for ; Wed, 13 May 2009 13:11:11 +0000 (UTC) (envelope-from tajudd@gmail.com) Received: by qw-out-2122.google.com with SMTP id 3so431863qwe.7 for ; Wed, 13 May 2009 06:11:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:cc:content-type; bh=zW6qfCDGRSVPjfCgb8A8MrE+cIxhRXvrXyNud/qb+zc=; b=ei77UrtPfBbBXTXxbESDiMNLfBuEVrDC8oaX88DoDUG3x9f7GhCyRUssu4rniqfkRh kBHG8Fj5kakvynAMcjZluphh6pUhy59R3X1CxKq9K1EomWUQAxGHEADm0CUCz5oqw/X8 1YeY54YA4ocgaxiJgxH5x1jaRoCIRX8uY0eWk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=JbuS+wlhsHXOa5vcXLT5kNL4I2BMim3IaxTYqXU5lZxsDVJNUoZLDgthITJgcyguJN aML5RgLRuLTIAPvz3feuaYzVNsA+ptaTI0ZcD3UtF+Fg/LxxOsvxGwPzfzGJgzlniUM5 Mnm0uiI/sz5FNkUZUnCWkbxUZDuIHKa4hiydQ= MIME-Version: 1.0 Received: by 10.220.99.144 with SMTP id u16mr829695vcn.119.1242220269255; Wed, 13 May 2009 06:11:09 -0700 (PDT) In-Reply-To: <20090513052912.GB44104@troutmask.apl.washington.edu> References: <20090513050333.GA4509@troutmask.apl.washington.edu> <20090513052912.GB44104@troutmask.apl.washington.edu> From: Tim Judd Date: Wed, 13 May 2009 07:10:49 -0600 Message-ID: To: Steve Kargl Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-questions Subject: Re: Disabling ssh timeouts? 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: Wed, 13 May 2009 13:11:12 -0000 On Tue, May 12, 2009 at 11:29 PM, Steve Kargl < sgk@troutmask.apl.washington.edu> wrote: > On Tue, May 12, 2009 at 11:14:26PM -0600, Tim Judd wrote: > > On Tue, May 12, 2009 at 11:03 PM, Steve Kargl < > > sgk@troutmask.apl.washington.edu> wrote: > > > > > Is there anyway to disable sshd from timing out a connection? > > > I've tried setting ClientAliveCountMax and ClientAliveInterval > > > and TCPKeepAlive in sshd.conf, but no combination that I've > > > tried has worked. > > > > > > > > > Read from remote host troutmask.apl.washington.edu: Connection reset > by > > > peer > > > Connection to troutmask.apl.washington.edu closed. > > > > > > The only way I'v efound to complete a run of the GCC testsuite > > > is to sit at the terminal and hit enter every so often. Also > > > note, nohup and backgrounding the job does not inhibit sshd > > > dropping the connection and losing all testsuite results. > > > > > > > I had this problem at a hotel recently. I think it was the router saying > > "stale connection here, cut it off".. Only way around it I got to work > was > > setting PuTTY (Win32 app) connection keepalive to some value (I used 90 > > seconds). > > > > Is your ISP or gateway one that actively and annoyingly cleans up stale > > connections? > > The ISP is comcast.net. As long as I'm doing something > interactively over the net, comcast.net doesn't time > out the connection. The system resetting the connection > is my system at work. It is my work system that I want > to disable sshd's reset feature. > > -- > Steve > As I said before, it could also be the gateway at the client, or the gateway at the server. I was making the change on a client to keep it active, so check your /etc/ssh/ssh_config I have cisco routers that would potentially do it too, and it's all about the config.