Hi !

Cc'ing this to NetBSD-users

On Mon, 19 Nov 2001, RJ45 wrote:
> Due to the latest ssh1 bug I Decided to sue only ssh2
> the problem is that it is terribly slow to connect to a 4000/90 using
> ssh2.
> There is some way to make it faster ??
> some hints??

It's not VAX-related, this is the fact on every platforms i think, even on
fast <censored> machines. It is just the initial handshake stuff, the
connection works fast then. (Even hardcore tunneling like NFS via tun-device
and the vtun program :)

Maybe host-lookup-stuff? It is not even NetBSD-related, it seems to be OpenSSH-
related. Would be interesting what it is, as SSH2 on other machines in my
company (i think this is not OpenSSH) works very fast, but OpenSSH on quite
fast RS/6000 (some 6-CPU stuff, very fast!) machines also is that slow with
protocol version 2.

Any hints? ssh -v didn't tell that much... The only thing to see is:

debug: Wait SSH2_MSG_KEX_DH_GEX_GROUP.
debug: Got SSH2_MSG_KEX_DH_GEX_GROUP.
** <here happens the biggest delay> **
debug: bits set: 1027/2049
debug: Sending SSH2_MSG_KEX_DH_GEX_INIT.

And top tells me about 50% load for each ssh and sshd (ssh was to localhost).

...Michael

-- 
visit http://www.bsdfans.org/   Home network powered by: NetBSD OpenBSD FreeBSD
Solaris HP-UX IRIX AIX MUNIX Tru64 Ultrix VMS SINIX Dolphin_Unix OpenStep MacOS