Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!newsfeed.internetmci.com!news.dti.ad.jp!nspixp!np0.iij.ad.jp!nf3.iij.ad.jp!nr0.iij.ad.jp!news.iij.ad.jp!iijnet!tom!usenet From: nao@tom-yam.or.jp (HAMADA Naoki) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: 3C590: no collisions? Date: 15 Jun 1997 01:55:57 GMT Organization: Tom Yam, Edogawa, JAPAN Lines: 15 Message-ID: <NAO.97Jun15105557@miffy.tom-yam.or.jp> References: <33A027F2.41C67EA6@we.lc.ehu.es> NNTP-Posting-Host: miffy.tom-yam.or.jp In-reply-to: "Jose M. Alcaide"'s message of Thu, 12 Jun 1997 18:46:42 +0200 Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:42964 In article <33A027F2.41C67EA6@we.lc.ehu.es> "Jose M. Alcaide" <jose@we.lc.ehu.es> writes: >Curiously, "netstat -i" _always_ shows 0 collisions on the vx0 >ethernet interface (3COM 590, FreeBSD 2.2.1). However, other hosts >attached to the same (saturated) segment have about 5% collision rate. >I suspect that the vx driver does not increment the collision >counter. A colleague has another FreeBSD box with a 3C900 (also >vx driver), and it also shows 0 collisions. Isn't surprising? 3COM's Etherlink III and later cards are so intelligent that they deal with collisions automatically without reporting to the host. Instead they have statistic registers, which are ignored by the drivers for now. - nao