From owner-freebsd-current@FreeBSD.ORG Tue Feb 26 00:04:08 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9056F16A404 for ; Tue, 26 Feb 2008 00:04:08 +0000 (UTC) (envelope-from derek@computinginnovations.com) Received: from betty.computinginnovations.com (mail.computinginnovations.com [64.81.227.250]) by mx1.freebsd.org (Postfix) with ESMTP id 3045313C465 for ; Tue, 26 Feb 2008 00:04:07 +0000 (UTC) (envelope-from derek@computinginnovations.com) Received: from p28.computinginnovations.com (dhcp-10-20-30-100.computinginnovations.com [10.20.30.100]) (authenticated bits=0) by betty.computinginnovations.com (8.14.2/8.13.8) with ESMTP id m1Q03vsU053426; Mon, 25 Feb 2008 18:03:58 -0600 (CST) (envelope-from derek@computinginnovations.com) Message-Id: <6.0.0.22.2.20080225180357.025db140@mail.computinginnovations.com> X-Sender: derek@mail.computinginnovations.com X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Mon, 25 Feb 2008 18:05:46 -0600 To: mouss , freebsd-current@freebsd.org From: Derek Ragona In-Reply-To: <47C34D7E.1010305@netoyen.net> References: <47C34D7E.1010305@netoyen.net> Mime-Version: 1.0 X-ComputingInnovations-MailScanner-Information: Please contact the ISP for more information X-ComputingInnovations-MailScanner: Found to be clean X-ComputingInnovations-MailScanner-From: derek@computinginnovations.com X-Spam-Status: No Content-Type: text/plain; charset="us-ascii"; format=flowed X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: ssh_exchange_identification: Connection closed by remote host X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Feb 2008 00:04:08 -0000 At 05:21 PM 2/25/2008, mouss wrote: >Hi, > >I am having an ssh issue to a freebsd 6.2 (error in subject). this >happened after a power outage at the client side (client was connected >before that), and this is the second time. Ican still connect to netbsd, >centos and debian systems from the same client. > >Is there a problem with the ssh shipped with 6.2? (BTW the system is >running pf). if so, what's the recommended way to fix this? any other ideas? > sshd has to be running on the system. Also you may need to delete any cached keys. You don't say in your post what client you are using. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.