Problems with collisions on eth0

Problems with collisions on eth0

Post by Axel Stallknec » Wed, 02 Dec 1998 04:00:00



Hi, folks.

I have problems with a lot of collisions on my primary network
interface. There are a lot (about 50) client PC's in the network
with different OS. Is it possible to detect which PC produces
all the trouble ?

Thanks, Axel.

 
 
 

Problems with collisions on eth0

Post by John Thoma » Fri, 04 Dec 1998 04:00:00


If you are concerned, go buy a small switch and segment your network a
bit.

> Hi, folks.

> I have problems with a lot of collisions on my primary network
> interface. There are a lot (about 50) client PC's in the network
> with different OS. Is it possible to detect which PC produces
> all the trouble ?

> Thanks, Axel.


 
 
 

Problems with collisions on eth0

Post by Owen Hughe » Fri, 04 Dec 1998 04:00:00



> Hi, folks.

> I have problems with a lot of collisions on my primary network
> interface. There are a lot (about 50) client PC's in the network
> with different OS. Is it possible to detect which PC produces
> all the trouble ?

> Thanks, Axel.

Well, if you are running Samba and have any Win95/98 PC's using it, you
will likely find the Win PCs are at fault, compliments of Microsoft.
Microsoft's TCP stack is.... I don't want to go on about that. :) Check
the "SPEED.TXT" document that comes with Samba if you're running it.
There's the mention of a neat utility called "mtuspeed" in there. Get
it. It can help greatly.
 
 
 

1. eth0: IPX collision errors

Howdy all,

     I have a LanCity cable modem attached to a 3c509b card. Everything
has been working fine for at least a month, until yesterday. Can anyone
tell me what is going on? I haven't done anything on my end in a while.

error message hitting every 10 seconds:

     IPX: Network number collision 3412
             eth0 802.2 and eth0 EtherII

/sbin/ifconfig output of network devices. Note that eth0 lists
three IPX items, all at the same hardware address.

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Bcast:127.255.255.255  Mask:255.0.0.0
          UP BROADCAST LOOPBACK RUNNING  MTU:3584  Metric:1
          RX packets:64 errors:0 dropped:0 overruns:0
          TX packets:64 errors:0 dropped:0 overruns:0

eth0      Link encap:10Mbps Ethernet  HWaddr 00:A0:24:D5:12:3F
          inet addr:24.1.66.13  Bcast:24.1.79.255  Mask:255.255.240.0
          IPX/Ethernet II addr:00A024D5123F
          IPX/Ethernet 802.2 addr:00003412:00A024D5123F
          IPX/Ethernet 802.3 addr:00000002:00A024D5123F
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2634 errors:0 dropped:0 overruns:0
          TX packets:143 errors:0 dropped:0 overruns:0
          Interrupt:11 Base address:0x270


has chosen not to support anything but Windows, so I'm on my own on
this one.

Lloyd

Lloyd B. Eldred, Ph.D.       <*>      

     --= Yes, as a matter of fact, I _am_ a rocket scientist. =--

2. Debian 3.0r0 / LILO

3. high collision rate on eth0

4. Compiling X apps with shared libs.

5. IPX: Network number collision 863207 and eth0 802.3

6. KDE through eXceed (on NT)

7. eth0 collisions high..what gives?

8. X loads slow when ppp0 is up

9. SE toolkit collision stats vs. wire collision stats

10. rh7.1: delaying eth0 initialization?? eth0 startup fail?

11. eth0 shuts down with NETDEV WATCHDOG: eth0: transmit timed out error.

12. "eth0" vs. "eth0:1"

13. Possible? eth0:1 ... eth0:50000