From owner-freebsd-questions@FreeBSD.ORG Tue Feb 22 22:31:45 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 7A4F616A4CE for ; Tue, 22 Feb 2005 22:31:45 +0000 (GMT) Received: from smtp.knology.net (smtp.knology.net [24.214.63.101]) by mx1.FreeBSD.org (Postfix) with SMTP id D387F43D55 for ; Tue, 22 Feb 2005 22:31:44 +0000 (GMT) (envelope-from dkelly@Grumpy.DynDNS.org) Received: (qmail 27514 invoked by uid 0); 22 Feb 2005 22:31:43 -0000 Received: from user-69-73-60-132.knology.net (HELO Grumpy.DynDNS.org) (69.73.60.132) by smtp6.knology.net with SMTP; 22 Feb 2005 22:31:43 -0000 Received: by Grumpy.DynDNS.org (Postfix, from userid 928) id 36D0C6178; Tue, 22 Feb 2005 16:31:43 -0600 (CST) Date: Tue, 22 Feb 2005 16:31:43 -0600 From: David Kelly To: jim@freeze.org Message-ID: <20050222223143.GA4217@Grumpy.DynDNS.org> References: <20050222211148.GA39859@freeze.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050222211148.GA39859@freeze.org> 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: Tue, 22 Feb 2005 22:31:45 -0000 On Tue, Feb 22, 2005 at 09:11:48PM +0000, jim@freeze.org wrote: > > It looks like an alergic reaction between OS X and FBSD, > but I don't have a clue where to start looking to > track this down. > > Any ideas on what this is or how to debug it would be > appreciated. Later in the thread Jim stated he had no control over the version of the FreeBSD machine. Am guessing he might not have root there. Am guessing he doesn't know what customizations may have been performed on it. I have seen similar problems where one end may have been FreeBSD. Suggest from the MacOS end to try forcing SSH protocol 1 with "ssh -1 user@othermachine" If that doesn't work try forcing version 2 with "-2". Also might try moving ~/.ssh/ out of the way on the Mac to see what happens if one starts afresh. -- David Kelly N4HHE, dkelly@HiWAAY.net ======================================================================== Whom computers would destroy, they must first drive mad.