Must be the hub portion that causes it... On all of the machines I checked, I don't have any collisions. Here's an Intel EEpro100 under Linux plugged directly into a cat 6509: [root at mail /root]# uptime 8:49pm up 206 days, 12:47, 1 user, load average: 0.00, 0.00, 0.00 [root at mail /root]# /sbin/ifconfig eth0 Link encap:Ethernet HWaddr 00:B0:D0:49:96:AB inet addr:10.10.220.100 Bcast:209.54.52.255 Mask:255.255.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:699886627 errors:0 dropped:0 overruns:0 frame:0 TX packets:727509085 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:16 Base address:0xb000 Another: 9:40pm up 22 days, 9:03, 4 users, load average: 0.09, 0.15, 0.10 eth0 Link encap:Ethernet HWaddr 00:B0:D0:49:CE:77 inet addr:10.10.220.101 Bcast:10.10.255.255 Mask:255.255.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:36665671 errors:0 dropped:0 overruns:0 frame:0 TX packets:49380623 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:16 Base address:0x9000 Here's a 3c905: [root at austad /root]# uptime 9:00pm up 17 days, 2:49, 2 users, load average: 0.00, 0.00, 0.00 [root at austad /root]# /sbin/ifconfig eth0 Link encap:Ethernet HWaddr 00:50:DA:BA:F7:D2 inet addr:10.1.150.90 Bcast:10.1.150.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:7415958 errors:0 dropped:0 overruns:1 frame:0 TX packets:2497135 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:9 Base address:0x1080 For fun, a Sun enterprise 250: bash-2.03# uptime 8:58pm up 10 day(s), 1:36, 1 user, load average: 0.17, 0.14, 0.15 bash-2.03# netstat -I hme0 Name Mtu Net/Dest Address Ipkts Ierrs Opkts Oerrs Collis Queue hme0 1500 arpanet mpls-collect 9773979 0 14480760 0 0 0 And a Sun enterprise 420: bash-2.02# uptime 9:01pm up 128 day(s), 7:29, 1 user, load average: 0.18, 0.16, 0.17 bash-2.02# netstat -I hme0 Name Mtu Net/Dest Address Ipkts Ierrs Opkts Oerrs Collis Queue hme0 1500 nyc-collect nyc-collect 99094772 0 70500620 0 0 0 > -----Original Message----- > From: David Dyer-Bennet [mailto:dd-b at dd-b.net] > Sent: Thursday, March 08, 2001 5:51 PM > To: tclug-list at mn-linux.org > Subject: Re: [TCLUG] how to tell the kernel eth0 is half-duplex > > > "Austad, Jay" <austad at marketwatch.com> writes: > > > You shouldn't see any collisions at all on your network > interface, I just > > checked 7 or 8 different boxes of mine, some have been up > for 6 months or > > more serving Real Video content out at around 5-10 Mb/sec > during the day, > > and I don't show any collisions at all on them. > > > > Chances are that your duplex is mismatched. Maybe a cheap > NIC could do it > > too.. probably doesn't hurt anything if you only have .1% though. > > > > Running a real 3c59x, I show: > > gw:Mail# w > 5:47pm up 15 days, 1:25, 5 users, load average: 2.39, 2.16, 2.11 > > gw:Mail# ifconfig > eth0 Link encap:Ethernet HWaddr 00:A0:24:D1:4F:3A > inet addr:63.224.10.74 Bcast:63.224.10.79 > Mask:255.255.255.248 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:12906269 errors:5 dropped:0 overruns:0 frame:5 > TX packets:14615922 errors:0 dropped:0 overruns:0 > carrier:431 > collisions:39926 txqueuelen:100 > Interrupt:10 Base address:0x9400 > > So, small percentage of collisions, but definitely non-zero. > > This system is going into the 100 megabit portion of a 10/100 "hub > with switch" (amazingly weird intermediate hardware generation; it has > a 10mb collision domain and a 100mb collision domain with a switch > connecting them) which is connected to a real 10/100 switch which is > finally connected to a Cisco 675 DSL router (most of the traffic on > this system is external). > -- > David Dyer-Bennet / Welcome to the future! / > dd-b at dd-b.net > SF: http://www.dd-b.net/dd-b/ Minicon: http://www.mnstf.org/minicon/ Photos: http://dd-b.lighthunters.net/ _______________________________________________ tclug-list mailing list tclug-list at mn-linux.org https://mailman.mn-linux.org/mailman/listinfo/tclug-list