Date: Tue, 22 Feb 2005 22:58:17 -0700 From: Chad Leigh -- Shire.Net LLC <chad@shire.net> To: Jim Freeze <jim@freeze.org> Cc: FreeBSD Questions <questions@freebsd.org> Subject: Re: SSH terminal locking up from OS X to FreeBSD Message-ID: <4e89e37f3eff3502b8959501144502e0@shire.net> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 22, 2005, at 10:04 PM, Jim Freeze wrote: > * Chuck Swiger <cswiger@mac.com> [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 "<RETURN>~?" 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 > "<RETURN>~?", 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4e89e37f3eff3502b8959501144502e0>