From owner-freebsd-questions@FreeBSD.ORG Fri Mar 10 11:36:06 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 82E5716A420 for ; Fri, 10 Mar 2006 11:36:06 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from asmtp-out2.blueyonder.co.uk (asmtp-out2.blueyonder.co.uk [195.188.213.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id 25F6743D49 for ; Fri, 10 Mar 2006 11:36:06 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [62.31.10.79] (helo=[192.168.0.2]) by asmtp-out2.blueyonder.co.uk with esmtp (Exim 4.52) id 1FHfuf-0002Mn-3t; Fri, 10 Mar 2006 11:36:05 +0000 Message-ID: <441164A4.6080809@dial.pipex.com> Date: Fri, 10 Mar 2006 11:36:04 +0000 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.12) Gecko/20060305 X-Accept-Language: en MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <311AACD2-C64F-40BF-8CDA-A5624AFA79B0@visionn.com> <20060310044208.GA19760@alexis.mi.celestial.com> In-Reply-To: <20060310044208.GA19760@alexis.mi.celestial.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: connection reset by peer from one location but not another 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: Fri, 10 Mar 2006 11:36:06 -0000 Bill Campbell wrote: >On Thu, Mar 09, 2006, Brian Ross wrote: > > >>I'm getting a "connection reset by peer" disconnect after about 10 >>minutes (or less) when I SSH to my 5.4-STABLE server from my home >>connection (cable DHCP), but I can stay connected all day long from >>work (DSL DHCP). I couldn't find any mention of connection reset by >>peer in the list archive, so I was wondering what I could monitor >>(running SSH in verbose mode doesn't tell me much) to find where I'm >>actually getting booted off from. Since it only happens with one >>connection, I'm thinking it isn't my actual server that's causing the >>reset. But I do not know what log file to monitor in order to >>investigate further. >> >> > >My guess is that your connection to the remote machine is via a >NAT (Masquerading) connection, and there's no activity on the >connection. Running something like top when you're not actively >using the connection will probably prevent the timeout. > > > If that's the case then running "ssh -o ServerAliveInterval 60" would do that. If it works, you can stick the option in your .ssh config file. --Alex