From owner-freebsd-questions@FreeBSD.ORG Sat Mar 6 05:37:30 2004 Return-Path: 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 C4B9916A4CE for ; Sat, 6 Mar 2004 05:37:30 -0800 (PST) Received: from out007.verizon.net (out007pub.verizon.net [206.46.170.107]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7BD1543D3F for ; Sat, 6 Mar 2004 05:37:30 -0800 (PST) (envelope-from cswiger@mac.com) Received: from mac.com ([68.161.120.219]) by out007.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20040306133729.NOYF28276.out007.verizon.net@mac.com>; Sat, 6 Mar 2004 07:37:29 -0600 Message-ID: <4049D3F9.9020604@mac.com> Date: Sat, 06 Mar 2004 08:36:57 -0500 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Rishi Chopra References: <40496C83.80605@cal.berkeley.edu> In-Reply-To: <40496C83.80605@cal.berkeley.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out007.verizon.net from [68.161.120.219] at Sat, 6 Mar 2004 07:37:29 -0600 cc: questions@freebsd.org Subject: Re: Getting Cut-Off X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Mar 2004 13:37:30 -0000 Rishi Chopra wrote: > I connect to the FreeBSD machine via SSH, and use secure file transfer > to upload/download from the machine. > > In the last week, the FreeBSD machine has dropped my connection on 3 > seperate occasions. I'll queue up some work and leave the machine > unattended, only to return at a later time and find that the connection > has been closed. Is sshd configured with the "KeepAlive" option set? Does netstat -i or -s report any errors? Maybe you have a flaky cable? Do you have any packet-filtering or NAT translation involved on one of the two hosts? [ Your description of the setup suggests no, but the behavior you describe can happen if one were using a (busy and/or dumb) stateful firewall... ] -- -Chuck