Very Computer

hey all!  I'm new to the forum sheet.  But I thought I would give it a
shot.  I'm trying to set up my gigabit card on Linux 2.4.  I can ping
it but I can't rlogin or FTP to it.  When I try to rlogin it takes
foreer and then drops at the end anyway.  I thought since it's a
gigabit card I would try to login from my PC which also has a gigabit
card.  So I telneted into it and it all works fine.

My problem from what i gather is that the gigabit card on the Linux 2.4
box is only operating at certain settings i.e. only 1000 and full
duplex instead of Auto negotiate and full and both duplex.

I can't seem to configure it adn the readme file is kinda skimpy.  I'm
not very Linux oriented but I can get around and follow some what
simple directions.

Any ideas?

thanks in advance!

Mr. Tweak

Gigabit ethernet cards must autonegotiate if you wish to use them at
gigabit speeds.  It is part of the spec (for gigabit copper that is).
So, don't "ever" hardcode a gigabit NIC or switch port.

Now, more broadly for 100BT and autoneg:

How Autoneg is supposed to work:

When both sides of the link are set to autoneg, they will "negotiate"
the duplex setting and select full duplex if both sides can do
full-duplex.

If one side is hardcoded and not using autoneg, the autoneg process
will "fail" and the side trying to autoneg is required by spec to use
half-duplex mode.

If one side is using half-duplex, and the other is using full-duplex,
sorrow and woe is the usual result.

So, the following table shows what will happen given various settings
on each side:

                 Auto       Half       Full

   Auto        Happiness   Lucky      Sorrow

   Half        Lucky       Happiness  Sorrow

   Full        Sorrow      Sorrow     Happiness

Happiness means that there is a good shot of everything going well.
Lucky means that things will likely go well, but not because you did
anything correctly :) Sorrow means that there _will_ be a duplex
mis-match.

When there is a duplex mismatch, on the side running half-duplex you
will see various errors and probably a number of late collisions. On
the side running full-duplex you will see things like FCS errors.
Note that those errors are not necessarily conclusive, they are simply
indicators.  

Further, it is important to keep in mind that a "clean" ping (or the
like - eg "linkloop") test result is inconclusive here - a duplex
mismatch causes lost traffic _only_ when both sides of the link try to
speak at the same time. A typical ping test, being synchronous, one at
a time request/response, never tries to have both sides talking at the
same time.

rick jones
--
oxymoron n, commuter in a gas-guzzling luxury SUV with an American flag
these opinions are mine, all mine; HP might not want them anyway... :)
feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH...

So put it to Auto.  Ok, would that explain the lag to rlogin and how
it's easy to telnet in from my windows machine?  I thought it would be
speed oriented but the duplex makes more sense.

If so, what would the commands be to configure it.  The readme file
doesn't give much help on syntax and how to put it into the
modules.conf file.

Thanks!

Mr. Tweak

Hello,

Just an update, I set the card to AUTO on Speed and Duplexing.  It
still won't let me rlogin.  Is there a security feature that I need to
shutdown?  I used to be able to rlogin and ftp with no problems at all
before this card.  And even when I installed this card the first day it
ran great.  I rebooted the machine and that's when all hell broke
loose.

Even if I put the old card back in, it won't let me rlogin or ftp.

Thanks in advance!

Mr.  Tweak

Well, at least that means the NICs were OK.  IIRC rlogin and ftp are
disabled by default on most linux distros because passwords are sent
in the clear.  There may be more about that and/or how to
enable/disable them in their respective manpages.

rick jones
--
a wide gulf separates "what if" from "if only"
these opinions are mine, all mine; HP might not want them anyway... :)
feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH...

Well, I just discovered that I can log in from other Linux boxes and
out to other Linux boxes but I can't log into old Sun OS 414 (Old
unix).

is there some setting when you put in a new card that it needs to be
reset on the Unix side or the Linux side???  I'm getting confused.
Nothing is making sense.

For some reason, also, when I set my gigabit card to Auto for speed and
the Both for Duplexing it defaults to Full and 1000 when it shows the
card booting up when I do an ifconfig eth0 up.  It also says between
the speed and duplexing that AutoNegotiation is up.

Oh heck, I have no idea LOL.

Unix can be so useful some times and then others it's just totally not
user friendly.

Sigh,

Mr. Tweak

Quote:> Just an update, I set the card to AUTO on Speed and Duplexing.  It
> still won't let me rlogin.  Is there a security feature that I need to

    That's not a useful description of the problem. When you try to rlogin,
what happens? Does a 'netstat' show that the machine is listening? Is
'rlogin' even enabled?

    DS

Hello,

Well, I ran a netstat -a from my linux box and it seemed pretty skimpy
compared to my other linux and unix boxes.  But it definitely didn't
show the unix machines that it was trying to rlogin to.  It seems that
a lot of the them where it says listening are actually blank.  Is there
a refresh command to rescan the network?

Or am I heading in the wrong direction?

Mr. Tweak