From owner-freebsd-questions@FreeBSD.ORG Mon Sep 20 04:04:47 2004 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 12DC916A4CE for ; Mon, 20 Sep 2004 04:04:47 +0000 (GMT) Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5B9143D2D for ; Mon, 20 Sep 2004 04:04:46 +0000 (GMT) (envelope-from subhro.kar@gmail.com) Received: by mproxy.gmail.com with SMTP id v18so1460220rnb for ; Sun, 19 Sep 2004 21:04:45 -0700 (PDT) Received: by 10.38.8.54 with SMTP id 54mr21479rnh; Sun, 19 Sep 2004 21:04:45 -0700 (PDT) Received: by 10.38.206.15 with HTTP; Sun, 19 Sep 2004 21:04:45 -0700 (PDT) Message-ID: Date: Mon, 20 Sep 2004 09:34:45 +0530 From: Subhro To: Lowell Gilbert In-Reply-To: <44r7oxye40.fsf@be-well.ilk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <44r7oxye40.fsf@be-well.ilk.org> cc: Pota Kalima cc: " " cc: Kevin Stevens Subject: Re: Ssh connection X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Subhro List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Sep 2004 04:04:47 -0000 On 19 Sep 2004 20:32:15 -0400, Lowell Gilbert wrote: > Kevin Stevens writes: > > > On Sep 19, 2004, at 10:17, Pota Kalima wrote: > > > > > On 19/9/04 5:56 pm, "Kevin Stevens" wrote: > > >> > > >> What happens if you try to ssh to the machine from itself? > > >> > > >> KeS > > >> > > > > > > Tried to ssh to machine itself and got the following: > > > > > > $ Ssh 192.168.0.5 > > > The authenticity of host '192.168.0.5 (192.168.0.5)' can't be > > > established. > > > DSA key fingerprint is 42:98:e3:11: > > > Are you sure you want to continue connecting (yes/no)? Yes > > > Warning: Permanently added '192.168.0.5' (DSA) to the list of known > > > hosts. > > > > > > [There was a prolonged pause here, I almost rebooted the machine] > > > > > > Sep 19 18:10:00 localhost sshd[581]: fatal: Timeout before > > > authentification > > > for 192.168.0.5 > > > Connection closed by 192.168.0.5 > > > > Well, there you go. Better get it working locally before worrying > > about connecting from other machines - at least it's easier to > > troubleshoot that way. You can start adding -v's to your session > > command to get more details. > > I suspect that making sshd log more verbosely will be important, not > just seeing the error messages from ssh. > > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > I have encountered the same problem. The workaround on my problem was to allow a line ipfw add 7000 allow tcp from me to any out xmit fxp0 keep-state It is needless to mention that I was trying to ssh in on a Intel NIC. Regards S. -- Subhro Sankha Kar School of Information Technology Block AQ-13/1 Sector V ZIP 700091 India