From owner-freebsd-questions@FreeBSD.ORG Mon Jun 6 20:17:07 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 1FE4C16A41C for ; Mon, 6 Jun 2005 20:17:07 +0000 (GMT) (envelope-from rmarella@gmail.com) Received: from ms-smtp-02-eri0.socal.rr.com (ms-smtp-02-qfe0.socal.rr.com [66.75.162.134]) by mx1.FreeBSD.org (Postfix) with ESMTP id E10EA43D48 for ; Mon, 6 Jun 2005 20:17:06 +0000 (GMT) (envelope-from rmarella@gmail.com) Received: from [10.0.0.101] (cpe-66-8-186-59.hawaii.res.rr.com [66.8.186.59]) by ms-smtp-02-eri0.socal.rr.com (8.12.10/8.12.7) with ESMTP id j56KGuX7015506; Mon, 6 Jun 2005 13:16:56 -0700 (PDT) Message-ID: <42A4AF37.6020708@gmail.com> Date: Mon, 06 Jun 2005 10:16:55 -1000 From: Robert Marella User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050512 X-Accept-Language: en-us, en MIME-Version: 1.0 To: luke 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> <20050606025554.GB81546@osiris.chen.org.nz> <42A3BCF9.8090200@gmail.com> <42A3CBF8.5020809@daleco.biz> <5fee5e3005060612044d4197fe@mail.gmail.com> In-Reply-To: <5fee5e3005060612044d4197fe@mail.gmail.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: Jonathan Chen , freebsd-questions@freebsd.org Subject: Re: ssh delays 40 seconds (SOLVED???) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jun 2005 20:17:07 -0000 luke wrote: > also, you might want to look into the UseDNS option in the sshd_config > file. this will cause the server to not perform dns lookups on > connecting hosts. > Luke Okay, that takes care of the delay. I had to change it to "no" on all boxes that I ssh into. Does this have any negative ramifications? My firewall excludes all incoming (at this time) so I am not too worried about being compromised. It still leaves the question in my pea brain as to why it has worked for 6 months and just started this nonsense in the last week or so. Did something change with 5.4? Thanks for responding. I want to thank everyone else for responding also. The consensus was that I need DNS/named working on my gateway/firewall so I will be reading and studying to have that working in the near future. Robert