Subject: ssh performance on Mac SE/30
To: None <port-mac68k@netbsd.org>
From: Ingles, Raymond <Raymond.Ingles@compuware.com>
List: port-mac68k
Date: 03/14/2003 09:50:35
 Well, I got my Mac SE/30 running NetBSD 1.6, and it works pretty well.
I'm going to use it as a webserver on my DMZ (even an SE/30 can saturate
my dinky little 128Kbit upstream on my DSL line when serving static
pages). (For now, though, it's on my LAN, plugged into the same hub as
the machine I'm ssh'ing from, so the firewall isn't an issue yet.)

 I've got an httpd working, and I'm tring to set up ssh so I can use scp
to update the website. I'm not terribly familiar with ssh, and I know
that a 16MHz 68030 is hundreds of times slower than my K6-2/500MHz, but
ssh takes what seems to be an inordinately long time to get going.

 If I try to ssh over, using "sh -vvv hostname" from my Linux box, the
process stalls for roughly five minutes on:

   debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY

 Then it proceeds, but I wasn't able to ssh as root; even given the right
password, it denied me. I didn't have time to try a regular user; it might
be configured to deny remote root logins. The main question I have is, is
the five-minute delay inevitable on an SE/30? It happens the same way
ssh'ing *out* from the SE/30, too. Is there anything I can do to speed
things up?

 If there's a better list for this, or an FM that I should R, please let
me know. Thanks!

 Sincerely,

 Ray Ingles                                         (248) 737-7300 x22317

   "I can't think of a worse way to wake up than discovering my head is
                           in a jar." - Tagon
 "Try waking up with your head in a jar and having deja-vu." - Der Trihs.
          - Schlock Mercenary, http://www.schlockmercenary.com/



The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose
it to anyone else. If you received it in error please notify us immediately
and then destroy it.