On Thursday 08 August 2002 12:15, KEVIN ZEMBOWER wrote:
>Thank you to all who responded, especially Christopher, Jousha and
> Mike. Most of you suggested checking the NIC and switchport for
> mismatches.
>
>This is a portion of "ifconfig eth0":
>admin:/proc/net # ifconfig eth0
>eth0      Link encap:Ethernet  HWaddr 00:90:27:B6:FB:E7
>          inet addr:172.16.2.7  Bcast:172.16.255.255 
> Mask:255.255.0.0 UP BROADCAST RUNNING MULTICAST  MTU:1500 
> Metric:1 RX packets:259376827 errors:0 dropped:0 overruns:0
> frame:0 TX packets:188989102 errors:0 dropped:0 overruns:0
> carrier:65070
>          collisions:54220248 txqueuelen:100
>          RX bytes:2574728265 (2455.4 Mb)  TX bytes:2729800656
> (2603.3 Mb)
>
>This is the system on the 100Base-T line connected directly to a
> Cisco switch, which should be set at full duplex. Does the fact
> that they're any collisions at all indicate that this is not
> working in full duplex mode? The collisions are 21% of the number
> of RX packets, and 28% of the TX packets. Are these numbers
> excessive?
>
Oh, my, yes.  Here at home, on a 10baseT half duplex system where 
one would expect more collisions, I have only this since the alst 
reboot to install 2.4.19 a few days back.
[root@coyote root]# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:50:BA:5D:EB:7D
          inet addr:192.168.1.3  Bcast:192.168.1.255  
Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:30543 errors:0 dropped:0 overruns:0 frame:0
          TX packets:40816 errors:0 dropped:0 overruns:0 carrier:0
          collisions:766 txqueuelen:100
          RX bytes:21113140 (20.1 Mb)  TX bytes:16369601 (15.6 Mb)
          Interrupt:12 Base address:0x2000

[root@coyote root]#
------------
Admittedly, thats only about 1% of the data you've moved, but take 
note of another item in your list "carrier:65070".

I'd call that a bad cable (or network card but it doesn't smell like 
that to me) if its a direct connection, or maybe the hub/switch if 
its not.

>At one time I knew of a program or command that you could run to
>display the settings of the NIC, like auto-negotiate and so forth.
> For the life of me I can remember it now. Any suggestions for
> determining this information?

Other  than ifconfig, I can't think of anything that would basicly 
show you the same as kde's information screens can.  And I don't 
think even thats shows this stuff,  darn it.

-- 
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz  512M
99.10% setiathome rank, not too shabby for a WV hillbilly