Date: Mon, 03 Sep 2001 09:02:30 +0800 From: Kelvin Ng Chee Hoong <nchee_hoong@pacific.net.sg> To: Devin Smith <devin-smith@rintrah.org> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: SSH Connection slow? Message-ID: <3B92D6A6.7000602@pacific.net.sg> References: <200108250404.f7P441w65664@grumpy.dyndns.org> <20010826035816.31719@mail.rintrah.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--------------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
<html>
<head>
</head>
<body>
<br>
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 .<br>
<br>
May be you can approach to your friendly system administrator to configure
DNS reversing lookup for your particular host .<br>
<br>
Please correct me if I'm wrong ........ sshd does DNS reversing lookup of
the client host whenever establishing TCP connection with client <br>
Devin Smith wrote:<br>
<blockquote type="cite" cite="mid:20010826035816.31719@mail.rintrah.org">
<blockquote type="cite">
<pre wrap="">Joseph Koenig writes:<br></pre>
<blockquote type="cite">
<pre wrap="">I recently installed FreeBSD 4.3 on a new server and any ssh connections<br>are slow. It takes about 5-10 seconds for the username/password box to<br>pop up. Once I enter the information, it takes about 5 seconds for the<br>login to finish and for me to be able to see anything in my terminal. Is<br>there any reason for this? This connection is being done over a local<br>network, so network lag really shouldn't be a problem. Any ideas? Thanks,<br></pre>
</blockquote>
<pre wrap="">That's about right for a 5x86/133. Once the connection is made the <br>encryption tasks are lesser. Run "systat -v" in an ssh window while you <br>open another to the same machine. You'll see a CPU utilization spike.<br><br></pre>
</blockquote>
<pre wrap=""><!---->That sounds a bit off to me. I had a similar problem when I misconfigured<br>djbdns on my server which were cleared up when I got all hosts (and the<br>name servers) to resolve themselves properly. You might want to go over<br>your DNS setup. A quick test would be to disable DNS entirely on each<br>machine and rely on the hosts files. i.e. change each /etc/host.conf to<br>contain:<br><br>host<br>#bind<br><br><br>and each /etc/hosts to contain:<br><br>10.0.0.1 server.yourdomain server<br>10.0.0.2 client.yourdomain client<br><br><br>--devin smith<br><br><br>To Unsubscribe: send mail to <a class="moz-txt-link-abbreviated" href="mailto:majordomo@FreeBSD.org">majordomo@FreeBSD.org</a><br>with "unsubscribe freebsd-questions" in the body of the message<br><br></pre>
</blockquote>
<br>
</body>
</html>
--------------030501080405010204060909--
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?3B92D6A6.7000602>