Openssh Slow on 5.07
willjay
is very slow to login and screen updates freeze for periods of 4 - 5
seconds.
What's my options.
Thanks
wj
Skot
OpenSSH is no slower than Telnet on a new P4. Maybe you need new
hardware, I would think.
Skot.
Jean-Pierre Radley
| I just installed 5.07 on a Compaq Pentium Pro Quad 200mz Proliant. Openssh
| is very slow to login and screen updates freeze for periods of 4 - 5
| seconds.
What platform are you coming *from*, and is going to the 5.0.7 box any
slower or faster using ssh vs. telnet?
--
JP
willjay
Openssh is much slower than telnet. I tested telnet and it works just fine.
I check Tinyterm and Anzio and both have the hesitation. Are there any
tunable parameters?
Thanks
wj
"Jean-Pierre Radley" <j...@jpr.com> wrote in message
news:2003071620...@jpradley.jpr.com...
Jean-Pierre Radley
| "Jean-Pierre Radley" <j...@jpr.com> wrote in message
| news:2003071620...@jpradley.jpr.com...
|
| > willjay typed (on Thu, Jul 17, 2003 at 03:40:31PM -0400):
| >
| > | I just installed 5.07 on a Compaq Pentium Pro Quad 200mz
| > | Proliant. Openssh is very slow to login and screen updates freeze
| > | for periods of 4 - 5 seconds.
| >
| > What platform are you coming *from*, and is going to the 5.0.7 box
| > any slower or faster using ssh vs. telnet?
Top-posting reverted. :-)
| I'm coming from 5.06 with ssh installed. ssh worked fine on this
| Proliant
|
| Openssh is much slower than telnet. I tested telnet and it works just
| fine. I check Tinyterm and Anzio and both have the hesitation. Are
| there any tunable parameters?
I run ssh and telnet from 5.0.6 to 5.0.7, or the other way around, and see
abolutely no speed differences.
--
JP
Bill Vermillion
<wil...@excite.com> wrote:
>I just installed 5.07 on a Compaq Pentium Pro Quad 200mz
>Proliant. Openssh is very slow to login and screen updates
>freeze for periods of 4 - 5 seconds.
Overall slow - or just a very long time to get logged in.
If the latter the machine doesn't have enough horsepower.
I used to get slow logins in a remote machine and a HW upgrade
impoved the login time dramatically.
--
Bill Vermillion - bv @ wjv . com
willjay
that is, and I do see a big difference. What happens is the screen updates,
and hesitates for about 1 or 2 sec then finishs. It is consistently
hesitant, not under loads, that is.
"Jean-Pierre Radley" <j...@jpr.com> wrote in message
news:20030717005...@jpradley.jpr.com...
willjay
is why my store bought ssh works fine and Openssh does not.
"Bill Vermillion" <b...@wjv.comREMOVE> wrote in message
news:HI5Bp...@wjv.com...
Mike Brown
Is this on a LAN or a WAN/VPN/internet connection? A quad PP200 should have
lots of power to run an ssh session. I am wondering if you are seeing a
MTU problem instead. If you are running through routers etc., then try
reducing the MTU to 1380 from 1500.
Mike
--
Michael Brown
The Kingsway Group
Stephen M. Dunn
$I just installed 5.07 on a Compaq Pentium Pro Quad 200mz Proliant. Openssh
$is very slow to login and screen updates freeze for periods of 4 - 5
$seconds.
I have a client who recently upgraded from an older machine
(5.0.5, PIII 700 or thereabouts, openssh 3.3 or 3.4) to a new
single-processor Xeon 2.4 GHz with a gig of RAM and 5.0.7.
When I say upgraded, it was done as a fresh install on the new
box, and then I manually imported users via ap, moved files,
updated config files, etc. so I'm confident that I didn't whack
part of the new OS or openssh with old stuff.
Both the client and server parts of openssh are slower on this
machine than on the older machine. Connecting to a remote machine
via ssh results in a 15-30 second (haven't actually timed it)
delay after providing the user name and password, before the
next thing shows up (the TERM= line from the .profile). Connecting
to the new machine from a remote machine is somewhat slower; there's
a delay of a few seconds (maybe 5 or so - again, haven't timed it)
after providing either a user name and password or user name and
the password for a private keyfile.
It's not a big deal for me since I rarely need to ssh from that
box to another and I can deal with a 5-second delay when I connect
in from elsewhere. One of these days I may try turning on debugging
to see if I can figure out at what point it's bogging down.
In both cases, I haven't noticed anything unusual once the
login has completed - screen updates etc. seem to work just as
well as they did on the older box.
--
Stephen M. Dunn <ste...@stevedunn.ca>
>>>----------------> http://www.stevedunn.ca/ <----------------<<<
------------------------------------------------------------------
Say hi to my cat -- http://www.stevedunn.ca/photos/toby/
Bela Lubkin
Stephen, your case sounds like a DNS problem. If your DNS was
completely failing, you would see 60-second pauses. Short pauses smell
like you have two "nameserver" lines in /etc/resolv.conf, and the first
one points to an IP address that isn't there at all. If it pointed to a
live machine that wasn't serving DNS, queries would get an immediate
negative response and the querant would immediately move on to the 2nd
server. If there's no machine at the IP address (or it's behind a
firewall that doesn't transmit ICMP error packets), you'll get a 5-10
second timeout before the querant moves on to the next choice.
I have no idea about the original poster's pauses. He should do some
basic performance analysis -- check for maxed-out CPU, that sort of
thing.
>Bela<
Will Jay
It is an WAN/internet connection. Please explain MTU? It is thur a
router. Actually it's very complicated connection. However, telnet is
working fine. Just Openssh is working slowly.
Jean-Pierre Radley
Is compression enabled or disabled in the sshd.config file?
It's a good speed-up if you're using PPP over modems and telephone
lines. It's not useful otherwise.
--
JP
Mike Brown
From some of the additional info it looks like MTU is a long shot, but
it is very easy to test. If you type in "ifconfig -a" the system will
report back its network settings, including the MTU. Choose the interface
that is supporting the default route, such as net0, and type
"ifconfig net0 mtu 1380".
Then open a ssh connection and see if its better.