From owner-freebsd-questions Sun Sep 2 17:56:33 2001 Delivered-To: freebsd-questions@freebsd.org Received: from sunny.pacific.net.sg (sunny.pacific.net.sg [203.120.90.127]) by hub.freebsd.org (Postfix) with ESMTP id A1C9737B403 for ; Sun, 2 Sep 2001 17:56:26 -0700 (PDT) Received: from smtp1.pacific.net.sg (smtp1.pacific.net.sg [203.120.90.70]) by sunny.pacific.net.sg with ESMTP id f830uPV16338; Mon, 3 Sep 2001 08:56:25 +0800 (SGT) Received: from pacific.net.sg ([203.208.143.98]) by smtp1.pacific.net.sg with ESMTP id f830sms14259; Mon, 3 Sep 2001 08:54:48 +0800 Message-ID: <3B92D6A6.7000602@pacific.net.sg> Date: Mon, 03 Sep 2001 09:02:30 +0800 From: Kelvin Ng Chee Hoong User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.2) Gecko/20010726 Netscape6/6.1 X-Accept-Language: zh-TW,en MIME-Version: 1.0 To: Devin Smith Cc: freebsd-questions@FreeBSD.ORG Subject: Re: SSH Connection slow? References: <200108250404.f7P441w65664@grumpy.dyndns.org> <20010826035816.31719@mail.rintrah.org> Content-Type: multipart/alternative; boundary="------------030501080405010204060909" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --------------030501080405010204060909 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Disable DNS lookup may solve the slow access to sshd but it may not a good solution to do that if your FBSD machine is connnected to the Internet . You can't surfing Internet or sending/retrieving email without DNS . May be you can approach to your friendly system administrator to configure DNS reversing lookup for your particular host . Please correct me if I'm wrong ........ sshd does DNS reversing lookup of the client host whenever establishing TCP connection with client Devin Smith wrote: >>Joseph Koenig writes: >> >>>I recently installed FreeBSD 4.3 on a new server and any ssh connections >>>are slow. It takes about 5-10 seconds for the username/password box to >>>pop up. Once I enter the information, it takes about 5 seconds for the >>>login to finish and for me to be able to see anything in my terminal. Is >>>there any reason for this? This connection is being done over a local >>>network, so network lag really shouldn't be a problem. Any ideas? Thanks, >>> >>That's about right for a 5x86/133. Once the connection is made the >>encryption tasks are lesser. Run "systat -v" in an ssh window while you >>open another to the same machine. You'll see a CPU utilization spike. >> >That sounds a bit off to me. I had a similar problem when I misconfigured >djbdns on my server which were cleared up when I got all hosts (and the >name servers) to resolve themselves properly. You might want to go over >your DNS setup. A quick test would be to disable DNS entirely on each >machine and rely on the hosts files. i.e. change each /etc/host.conf to >contain: > >host >#bind > > >and each /etc/hosts to contain: > >10.0.0.1 server.yourdomain server >10.0.0.2 client.yourdomain client > > >--devin smith > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message > --------------030501080405010204060909 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit
Disable DNS lookup may solve the slow access to sshd but it may not a good solution  to do that if your FBSD machine is connnected to the Internet . You can't surfing Internet or sending/retrieving email without DNS  .
   
May be you can approach to your friendly system administrator to configure DNS reversing lookup for your particular host .

Please correct me if I'm wrong ........ sshd does DNS reversing lookup of  the client host whenever establishing TCP connection with client
Devin Smith wrote:
Joseph Koenig writes:
I recently installed FreeBSD 4.3 on a new server and any ssh connections
are slow. It takes about 5-10 seconds for the username/password box to
pop up. Once I enter the information, it takes about 5 seconds for the
login to finish and for me to be able to see anything in my terminal. Is
there any reason for this? This connection is being done over a local
network, so network lag really shouldn't be a problem. Any ideas? Thanks,
That's about right for a 5x86/133. Once the connection is made the 
encryption tasks are lesser. Run "systat -v" in an ssh window while you 
open another to the same machine. You'll see a CPU utilization spike.

That sounds a bit off to me. I had a similar problem when I misconfigured
djbdns on my server which were cleared up when I got all hosts (and the
name servers) to resolve themselves properly. You might want to go over
your DNS setup. A quick test would be to disable DNS entirely on each
machine and rely on the hosts files. i.e. change each /etc/host.conf to
contain:

host
#bind


and each /etc/hosts to contain:

10.0.0.1                server.yourdomain     server
10.0.0.2               client.yourdomain         client


--devin smith


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message


--------------030501080405010204060909-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message