From owner-freebsd-questions@FreeBSD.ORG Wed Feb 23 06:57:56 2005 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 0A1E316A4CE for ; Wed, 23 Feb 2005 06:57:56 +0000 (GMT) Received: from freebsdportal.com (freebsdportal.com [161.58.142.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A26043D5E for ; Wed, 23 Feb 2005 06:57:55 +0000 (GMT) (envelope-from jdf@freebsdportal.com) Received: from freebsdportal.com (localhost [127.0.0.1]) by freebsdportal.com (8.13.1/8.13.1) with ESMTP id j1N6vpUD018356; Wed, 23 Feb 2005 06:57:52 GMT Received: (from jdf@localhost) by freebsdportal.com (8.13.1/8.13.1/Submit) id j1N6voVr018346; Wed, 23 Feb 2005 06:57:50 GMT Date: Wed, 23 Feb 2005 06:57:50 +0000 From: Jim Freeze To: "Chad Leigh -- Shire.Net LLC" Message-ID: <20050223065749.GA14245@freeze.org> References: <20050222211148.GA39859@freeze.org> <421BAC56.4050801@daleco.biz> <20050222231352.GA34739@freeze.org> <57d710000502221532dbacb23@mail.gmail.com> <20050222233640.GD34739@freeze.org> <421BC3AB.8030203@mac.com> <20050223050420.GA38709@freeze.org> <4e89e37f3eff3502b8959501144502e0@shire.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4e89e37f3eff3502b8959501144502e0@shire.net> User-Agent: Mutt/1.4.2.1i cc: questions@freebsd.org Subject: Re: SSH terminal locking up from OS X to FreeBSD 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: Wed, 23 Feb 2005 06:57:56 -0000 * Chad Leigh -- Shire.Net LLC [2005-02-22 22:58:17 -0700]: > Just for giggles, what happens when you try a different encryption > method with the ssl client? For example, -c blowfish Ok, so I tried this, but it still locks up. However, I was able to do ~C to get a command line and ~^Z to background the ssh terminal, but I was never able to re-activate it. I did manage to log the IP activity through tcp dump, and I discovered that after the 'lock up', there are no IP messages originating from the remote machine. Also, the IP blocks are of type FP, whatever that is. (Hmm, maybe I need to clear out the known hosts on the remote machine.) An abbreviated version is below. The full log file is at: http://www.freeze.org/tcpdump3b.log 00:22:59.999439 IP localhost.53245 > remotemachine.com.ssh: S 611378943:611378943(0) win 65535 00:23:00.053942 IP remotemachine.com.ssh > localhost.53245: S 77400915:77400915(0) ack 611378944 win 57344 00:23:00.054039 IP localhost.53245 > remotemachine.com.ssh: . ack 1 win 65535 00:23:00.331844 IP remotemachine.com.ssh > localhost.53245: P 1:24(23) ack 1 win 57964 00:23:04.922358 IP localhost.53245 > remotemachine.com.ssh: . ack 3512 win 65535 # Long break - remote terminal stops responding but data is still flowing as you can see. # 00:34:05.662885 IP localhost.53245 > remotemachine.com.ssh: P 1519:1559(40) ack 3512 win 65535 00:34:07.284836 IP localhost.53245 > remotemachine.com.ssh: P 1519:1559(40) ack 3512 win 65535 00:34:09.285235 IP localhost.53245 > remotemachine.com.ssh: P 1519:1559(40) ack 3512 win 65535 00:34:43.290382 IP localhost.53240 > remotemachine.com.ssh: FP 0:48(48) ack 1 win 65535 # ~? 00:35:09.294870 IP localhost.53245 > remotemachine.com.ssh: P 1519:1719(200) ack 3512 win 65535 00:37:17.308387 IP localhost.53245 > remotemachine.com.ssh: FP 1519:2655(1136) ack 3512 win 65535 #Closed terminal -- Jim Freeze