SSH login very slow

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
NotDashEscaped: You need GnuPG to verify this message

In comp.os.linux.networking Kimmo Koivisto <kimmo.koivisto@surfeu.fi> suggested:
> GVK wrote:
>> Kimmo Koivisto wrote:
[..]
>> Well, adding the client IP to server's /etc/hosts helped :)
>> It's working well and good now. But how about the rest of the clients?
>> They all are facing the same problem. Let's say the clients use IPs
>> 172.16.19.*...anyway I can make it faster for all of them?
[..]

> Okay, now we can be sure that the problem is that reverse DNS is not
> working.

> There is two solutions, maybe more, but here are those:

> 1) If the network (172.16.19.*) is in your control, you can set up (or fix
> existing) DNS which resolves those addresses to names. You don't have to
> have real domain, just set up private DNS server. Setting up properly
> configured DNS makes network work smoother.
[..]

> UseDNS no

> If this does not work, setting up DNS could be the best thing. Or you can
> add all 172.16.19.* addresses to the hosts file (with shell script of
> course).

Likely to improve things for ssh, but then running DNS will
prevent him from running from one problem into another, there's a
great DNS HOWTO (www.tldp.org) guiding through all steps in
setting up a simple local DNS server for your own zone.

The only proper way to go.

--
Michael Heiming (GPG-Key ID: 0xEDD27B94)
mail: echo zvpunry@urvzvat.qr | perl -pe 'y/a-z/n-za-m/'
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFA4JbiAkPEju3Se5QRAssmAJ4iWjpCquZUGm8slnkbeo kPC+WbdQCgk3QZ
vBvRrINzYgK4bbEiLENHvPE=
=hMgb
-----END PGP SIGNATURE-----