Date: Mon, 20 Sep 2004 09:34:45 +0530 From: Subhro <subhro.kar@gmail.com> To: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> Cc: Kevin Stevens <freebsd@pursued-with.net> Subject: Re: Ssh connection Message-ID: <b2807d04040919210419193e33@mail.gmail.com> In-Reply-To: <44r7oxye40.fsf@be-well.ilk.org> References: <BD737DD7.2F92%hpota@mac.com> <BA36931E-0A60-11D9-AABF-000A959CEE6A@pursued-with.net> <44r7oxye40.fsf@be-well.ilk.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 19 Sep 2004 20:32:15 -0400, Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> wrote: > Kevin Stevens <freebsd@pursued-with.net> writes: > > > On Sep 19, 2004, at 10:17, Pota Kalima wrote: > > > > > On 19/9/04 5:56 pm, "Kevin Stevens" <freebsd@pursued-with.net> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b2807d04040919210419193e33>