From owner-freebsd-questions@FreeBSD.ORG Wed Feb 23 05:04: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 E4A6016A4CE for ; Wed, 23 Feb 2005 05:04:22 +0000 (GMT) Received: from freebsdportal.com (freebsdportal.com [161.58.142.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id 81E9E43D1D for ; Wed, 23 Feb 2005 05:04:22 +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 j1N54L0x043611; Wed, 23 Feb 2005 05:04:21 GMT Received: (from jdf@localhost) by freebsdportal.com (8.13.1/8.13.1/Submit) id j1N54KCS043605; Wed, 23 Feb 2005 05:04:20 GMT Date: Wed, 23 Feb 2005 05:04:20 +0000 From: Jim Freeze To: Chuck Swiger Message-ID: <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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <421BC3AB.8030203@mac.com> 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 05:04:23 -0000 * 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. -- Jim Freeze