Date: Mon, 26 Mar 2001 08:42:59 +1200 From: Jonathan Chen <jonathan.chen@itouch.co.nz> To: Odhiambo Washington <wash@iconnect.co.ke> Cc: freebsd-questions@freebsd.org Subject: Re: Host Keys - ssh Message-ID: <20010326084259.A6377@itouchnz.itouch> In-Reply-To: <20010323102839.A19983@poeza.iconnect.co.ke>; from wash@iconnect.co.ke on Fri, Mar 23, 2001 at 10:28:39AM %2B0300 References: <20010322161057.A8986@poeza.iconnect.co.ke> <20010323085408.B24064@itouchnz.itouch> <20010323102839.A19983@poeza.iconnect.co.ke>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Mar 23, 2001 at 10:28:39AM +0300, Odhiambo Washington wrote:
[...]
> Hi Jon,
>
> Thanks for the info. It is *exactly* what I was looking for.
> I had a problem (and it still persists) with ssh taking so long to connect
> to a host on the same net and I thought it could be something to do with
> the host keys, since there is a time I had to revive my FBSD box using a
> dump|restore from a neighbor host.
> Now I am wondering if there is a reason ssh should take so long (even
> longer than a minute) to negotiate a connection with a host on the same
> LAN/net.
>
> Host A ------------>Host B (takes so long)
> 212.22.163.113 212.22.163.2
>
> Host A -------------> Host C
> 212.22.163.107 (connects instantly)
>
What does "dig -x 212.22.163.2" produce? Perhaps there is no reverse
DNS entry for that IP address.
Hope this helps.
--
Jonathan Chen <jonathan.chen@itouch.co.nz>
----------------------------------------------------------------------
"A person should be able to do a small bit of everything,
specialisation is for insects"
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010326084259.A6377>