Date: Wed, 23 May 2007 19:55:07 -0400 From: Javier Henderson <javier@kjsl.com> To: RW <fbsd06@mlists.homeunix.com> Cc: freebsd-questions@freebsd.org Subject: Re: looking for ethernet errors, collisions Message-ID: <20070523195507215788.be3245e3@kjsl.com> In-Reply-To: <20070524002543.7f6d6b34@gumby.homeunix.com.> References: <20070517152529.GA15636@tigger.digitaltorque.ca> <BMEDLGAENEKCJFGODFOCMEBCCAAA.tedm@toybox.placo.com> <20070520011025.GX11625@tigger.digitaltorque.ca> <20070524002543.7f6d6b34@gumby.homeunix.com.>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 24 May 2007 00:25:43 +0100, RW wrote: > On Sat, 19 May 2007 21:10:25 -0400 > "Michael P. Soulier" <msoulier@digitaltorque.ca> wrote: > >> On 17/05/07 Ted Mittelstaedt said: >> >>> Note that error counters are often bogus because so >>> many cards today filter errors out in hardware, long before >>> the OS driver gets them. >> >> Well, there are plenty there on my sis0 interface (internal). >> >> [msoulier@kanga ~]$ netstat -i >> Name Mtu Network Address Ipkts Ierrs Opkts >> Oerrs Coll >> sis0 1500 <Link#1> 00:0a:e6:4a:56:c2 37989565 3980 36808783 >> 5749 6492857 >> sis0 1500 192.168.1 kanga 12380344 - >> 9255757 - >> > > > What are collisions in this context? > > Traditional ethernet collisions aren't possible on modern hardware, > since there's never more than one output writing to each twisted-pair. You can have collisions if the duplex settings don't match. -jav
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070523195507215788.be3245e3>