SSH - slowly (or not at all) connects [a little long]

Robert B. wrote:
> On Sun, 01 Feb 2004 20:50:47 -0500, CL (dnoyeB) Gilbert
> <CheckMyGPGKey@ThisOneIsFake.com> wrote:
>
>> i think the first name should be localhost.localdomain for the
>> 127.0.0.1 address. put the klaster2 in the other slots. Doubt if
>> this is the issue, but it does affect a few things. Namely, you are
>> assigning the klaster2 name twice, which is improper.
>
>
> I'll try it. I I'll also try to install the original drivers. For now,
> the NICs work on the Fedora's drivers.
>
>

You definitely need to fix that hosts file. cant have 2 entries for
same computer, plus you are essentially mising the loalhost.localdomain
entry since its not leftmost, and that will slow things down. How does
it behave if you use ipaddress for connection?

--
Respectfully,


CL Gilbert

"Verily, verily, I say unto you, He that entereth not by the door() into
the sheepfold{}, but climbeth up some other *way, the same is a thief
and a robber." John 10:1

GnuPG Key Fingerprint:
82A6 8893 C2A1 F64E A9AD 19AE 55B2 4CD7 80D2 0A2D

For a free Java interface to Freechess.org see
http://www.rigidsoftware.com/Chess/chess.html

On Wed, 04 Feb 2004 13:06:34 -0500, CL (dnoyeB) Gilbert
<CheckMyGPGKey@ThisOneIsFake.com> wrote:

> Robert B. wrote:
>> On Sun, 01 Feb 2004 20:50:47 -0500, CL (dnoyeB) Gilbert
>> <CheckMyGPGKey@ThisOneIsFake.com> wrote:
>>
>>> i think the first name should be localhost.localdomain for the
>>> 127.0.0.1 address. put the klaster2 in the other slots. Doubt if
>>> this is the issue, but it does affect a few things. Namely, you are
>>> assigning the klaster2 name twice, which is improper.
>>
>>
>> I'll try it. I I'll also try to install the original drivers. For now,
>> the NICs work on the Fedora's drivers.
>>
>>
>
> You definitely need to fix that hosts file. cant have 2 entries for
> same computer, plus you are essentially mising the loalhost.localdomain
> entry since its not leftmost, and that will slow things down. How does
> it behave if you use ipaddress for connection?

After all, what have I tried:
- I've fixed the hosts file,
- I've tried to comment out the hardware addresses from the
/etc/sysconfig/network-scripts/ifcfg-ethX,
Nothing helped to solve the problem.
There is also one thing: in the routing table there is a network:
169.254.0.0
I found this is so-called linksys address, and it appears automatically in
the
table.
One thing I've done that seemed to help _partially_ was to enter all the 8
HW addresses
of the NICs into the appropriate /etc/ethers files and to execute at
system startup
/sbin/arp -f command. It seems that it solved the problem with ssh
connection, but
only between the internal (192.168.0.X) numbers. The connection with the
use of the
other interfaces with the external IP numbers is now impossible at all.
And this is
again strange for me. I also think that this partial solution is not
elegant...
Looks like I have to learn more about networking...

--
Regards,
Robert B.
rpbyc@op.pl

Robert B. wrote:
> On Wed, 04 Feb 2004 13:06:34 -0500, CL (dnoyeB) Gilbert
> <CheckMyGPGKey@ThisOneIsFake.com> wrote:
>
>> Robert B. wrote:
>>
>>> On Sun, 01 Feb 2004 20:50:47 -0500, CL (dnoyeB) Gilbert
>>> <CheckMyGPGKey@ThisOneIsFake.com> wrote:
>>>
>>>> i think the first name should be localhost.localdomain for the
>>>> 127.0.0.1 address. put the klaster2 in the other slots. Doubt if
>>>> this is the issue, but it does affect a few things. Namely, you are
>>>> assigning the klaster2 name twice, which is improper.
>>>
>>>
>>>
>>> I'll try it. I I'll also try to install the original drivers. For now,
>>> the NICs work on the Fedora's drivers.
>>>
>>>
>>
>> You definitely need to fix that hosts file. cant have 2 entries for
>> same computer, plus you are essentially mising the
>> loalhost.localdomain entry since its not leftmost, and that will slow
>> things down. How does it behave if you use ipaddress for connection?
>
>
> After all, what have I tried:
> - I've fixed the hosts file,
> - I've tried to comment out the hardware addresses from the
> /etc/sysconfig/network-scripts/ifcfg-ethX,
> Nothing helped to solve the problem.
> There is also one thing: in the routing table there is a network:
> 169.254.0.0

that is the address cards will take when they can not find a DHCP server.

> I found this is so-called linksys address, and it appears automatically
> in the
> table.
> One thing I've done that seemed to help _partially_ was to enter all the
> 8 HW addresses
> of the NICs into the appropriate /etc/ethers files and to execute at
> system startup
> /sbin/arp -f command. It seems that it solved the problem with ssh
> connection, but
> only between the internal (192.168.0.X) numbers. The connection with the
> use of the
> other interfaces with the external IP numbers is now impossible at all.
> And this is
> again strange for me. I also think that this partial solution is not
> elegant...
> Looks like I have to learn more about networking...
>

Sounds like you are having DHCP issues to me. are you assigning your IP
addresses statically? or by a DHCP server? perhaps you have more than
one dhcp server active?


--
Respectfully,


CL Gilbert

"Verily, verily, I say unto you, He that entereth not by the door() into
the sheepfold{}, but climbeth up some other *way, the same is a thief
and a robber." John 10:1

GnuPG Key Fingerprint:
82A6 8893 C2A1 F64E A9AD 19AE 55B2 4CD7 80D2 0A2D

For a free Java interface to Freechess.org see
http://www.rigidsoftware.com/Chess/chess.html

On Fri, 06 Feb 2004 23:13:24 -0500, CL (dnoyeB) Gilbert
<CheckMyGPGKey@ThisOneIsFake.com> wrote:

> Sounds like you are having DHCP issues to me. are you assigning your IP
> addresses statically? or by a DHCP server? perhaps you have more than
> one dhcp server active?

I am assigning the IP addresses statically. There probably is running a
DHCP server
in the external network, but I don't use it.


--
Regards,
Robert B.
rpbyc@op.pl