From owner-freebsd-questions@FreeBSD.ORG Wed Feb 23 05:58:22 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 4444A16A4CE for ; Wed, 23 Feb 2005 05:58:22 +0000 (GMT) Received: from hobbiton.shire.net (hobbiton.shire.net [166.70.252.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D75543D2F for ; Wed, 23 Feb 2005 05:58:22 +0000 (GMT) (envelope-from chad@shire.net) Received: from [67.161.222.227] (helo=[192.168.99.68]) by hobbiton.shire.net with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.43) id 1D3pXO-0009vP-F5; Tue, 22 Feb 2005 22:58:19 -0700 In-Reply-To: <20050223050420.GA38709@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> Mime-Version: 1.0 (Apple Message framework v619.2) Message-Id: <4e89e37f3eff3502b8959501144502e0@shire.net> From: Chad Leigh -- Shire.Net LLC Date: Tue, 22 Feb 2005 22:58:17 -0700 To: Jim Freeze X-Mailer: Apple Mail (2.619.2) X-SA-Exim-Connect-IP: 67.161.222.227 X-SA-Exim-Mail-From: chad@shire.net Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.0.0 (2004-09-13) on hobbiton.shire.net X-Spam-Status: No, score=-0.1 required=5.0 tests=AWL,BAYES_50 autolearn=disabled version=3.0.0 X-Spam-Level: X-SA-Exim-Version: 4.1+cvs (built Mon, 23 Aug 2004 08:44:05 -0700) X-SA-Exim-Scanned: Yes (on hobbiton.shire.net) cc: FreeBSD Questions 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 05:58:22 -0000 On Feb 22, 2005, at 10:04 PM, Jim Freeze wrote: > * Chuck Swiger [2005-02-22 18:43:39 -0500]: > >> Jim Freeze wrote: >> Show us what SSH shows when the connection locks up. In particular, >> try >> doing a "~?" after you get the connection lockup and see >> whether >> you get a menu of escape sequences back. > > Hmm, I never knew about that. > So, I finally got tcpdump working, and after the terminal locks > up, hitting return produces no affect on the command line, but the ssh > connection is still open because I can see data go by on my tcpdump > window. And, I DO get the menu of escape sequences back after typing > "~?", but I was not successful in getting anything to work. > In fact, the tcpdump messages pretty much stopped after a few > key strokes. > Just for giggles, what happens when you try a different encryption method with the ssl client? For example, -c blowfish man ssh for more details Chad