Date: Mon, 6 Jun 2005 14:55:54 +1200 From: Jonathan Chen <jonc@chen.org.nz> To: Robert Marella <rmarella@gmail.com> Cc: freebsd-questions@FreeBSD.org Subject: Re: ssh delays 40 seconds Message-ID: <20050606025554.GB81546@osiris.chen.org.nz> In-Reply-To: <42A3B9B6.5070800@gmail.com> References: <5EEBE9C3C61D1142994C6B620C51E847110B80@depot.weblinkmo.com> <17059.37867.174248.688500@jerusalem.litteratus.org> <42A3A5F4.8090807@gmail.com> <20050606023235.GA81334@osiris.chen.org.nz> <42A3B9B6.5070800@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jun 05, 2005 at 04:49:26PM -1000, Robert Marella wrote:
> Jonathan Chen wrote:
[...]
> >It's not the forward case that's the problem. The sshd daemon on the
> >server side attempts to find out where the connection is from by doing
> >a reverse-lookup. If the incoming IP hasn't got a DNS entry, the failing
> >DNS ip-lookup will time out in ~30s.
> >
>
> Thanks for responding. In all of my systems /etc/hosts is populated with
> the name and LAN IP address of all other boxes. My gateway/firewall is a
> 5.4 Rel computer. I can ping that box "it's called gateway" with ping
> gateway or ping 10.0.0.1 no problem.
What does "dig -x 10.0.0.1" on the ssh-server box give you? Looks like
you need to set up a internal DNS server to resolve these sort of
problems.
Cheers.
--
Jonathan Chen <jonc@chen.org.nz>
----------------------------------------------------------------------
Vini, vidi, velcro...
I came, I saw, I stuck around
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050606025554.GB81546>