[FreeNX-kNX] why is initial authentication/connecting so slow?

Ben Voigt bvoigt at kas.com
Wed Feb 23 00:46:11 UTC 2005


Seems a very long time for an ssh connection.  Is the daemon running or are
you using xinetd?  Are you using an exceptionally long key length?

The "authentication completed" stage also takes the most time by far on my
system, but it's maybe 3-4 seconds.  Each other stage is about half of a
second or at most one second.

Do you have any background anti-virus that would scan executables and shell
script before executing?

****************************

Ben Voigt
University of Pennsylvania
Electrical Engineering PhD Candidate

voigt at seas.upenn.edu <mailto:voigt at seas.upenn.edu>
BVoigt at kas.com <mailto:BVoigt at kas.com>

Support a Constitutional Amendment to protect the Pledge of Allegiance and
National Motto.
Click here for more information. <http://www.wepledge.com/>

****************************


-----Original Message-----
From: Tomasz Chmielewski [mailto:mangoo at interia.pl]
Sent: Tuesday, February 22, 2005 9:42 AM
To: Gian Filippo Pinzari
Cc: FreeNX-kNX
Subject: Re: [FreeNX-kNX] why is initial authentication/connecting so
slow?


Gian Filippo Pinzari wrote:

>> What is a ssh log? A normal system log that logs ssh connections?
>> There's only normal stuff in it.
>>
>> What is the session output?
>
>
> You are new to NX, aren't you. Check the .nx directory in your home.
> Use the 'find' utility to locate the files.

not anymore :)

OK, found them.

Hmm, I don't know, these files look pretty normal and I don't see
anything unusual there.
I can attach them if you want.


>>> Can it be that the slowness is related to resolving entries
>>> when xauth is run on the client?
>>
>>
>> I don't know?
>> How to check it?
>
>
> Try running the 'xauth list' and the 'xauth add ...' command. That's
> the way nxclient checks or creates the X cookie.
>
>> What "resolving entries" do you refer to?

there are few entries when I do 'xauth list'; 'xauth add ...' and then
'xauth list' work fast, everything is added and listed.

I removed this file, and now there is only one entry in it:

there are entries with a hostname:

my_hostname/unix:13   MIT-MAGIC-COOKIE-1   some-hex-value


I can ping my_hostname (it's in /etc/hosts), it doesn't resolve though
through 'host my_hostname' (and I think it shouldn't anyway).


> xauth tries to reverse the names. This can take long if there are
> many entries in .Xauthority and/or if any of them can't be resolved.

As I said there were only a few entries, now there is on with a name
from /etc/hosts, so everything should be OK.
Both hosts are in /etc/hosts on respective machines and can ping each
other using hostnames.


These are the times of different stages when connecting using
nomachine's nxclient:

Connecting to...		2 s
Waiting authentication		12 s
Authentication completed	20 s
Negotiating link parameters and rest 10 s

So in total 45 seconds or more.
This may vary a bit.

So I repeat my question: how long do these all parts take for you?


Normal ssh login takes 2-3 seconds (it takes that long/short whether I
use a key or a password).


Tomek
_______________________________________________
FreeNX-kNX mailing list
FreeNX-kNX at kde.org
https://mail.kde.org/mailman/listinfo/freenx-knx
--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 266.4.0 - Release Date: 2/22/2005




More information about the FreeNX-kNX mailing list