Check for a bad cable, cable length, cable rating (CAT 5), bad port on the
hub, another NIC that is spraying junk onto the network.
-Paul
On Tue, 26 May 1998, Tigran Aivazian wrote:
> Date: Tue, 26 May 1998 15:26:34 +0100 (BST)
> From: Tigran Aivazian <tigran@sco.COM>
> To: linux-net@vger.rutgers.edu
> Subject: 3c509 <-> eepro100 on a private LAN: lots of collisions.
>
> Hello guys,
>
> What can cause such a huge number of collisions on a LAN consisting of two
> nodes: eepro100 (Linux 2.0.32) and 3c509 revG (Linux 2.0.32):
>
> eth0 Link encap:Ethernet HWaddr 00:A0:C9:49:B0:5F
> inet addr:150.126.4.166 Bcast:150.126.4.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:698610 errors:0 dropped:0 overruns:0 frame:2
> TX packets:1245716 errors:0 dropped:0 overruns:0 carrier:0
> Collisions:957285
> Interrupt:11 Base address:0xff40
>
> Or isn't 957285 huge?
>
> Regards,
>
> -----------------------------------------------------
> Tigran A. Aivazian | http://www.sco.com/
> Escalations Research Group | Email: tigran@sco.com
> Santa Cruz Operation Ltd |
> United Kingdom |
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to majordomo@vger.rutgers.edu
>
----------------------------------------------------------------------------
Paul Kanz
Conix Consulting
pkanz@conix.com
----------------------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.rutgers.edu