Date: Wed, 23 May 2007 16:51:37 -0700 From: Chuck Swiger <cswiger@mac.com> To: RW <fbsd06@mlists.homeunix.com> Cc: freebsd-questions@freebsd.org Subject: Re: looking for ethernet errors, collisions Message-ID: <404317EA-2E8C-45CD-9418-6493610D4D69@mac.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 May 23, 2007, at 4:25 PM, RW wrote: >> 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. Even though all modern NICs will happily do full-duplex operation when connected via a switch, people still use hubs rather than switches, sometimes.... :-) You can still get ethernet collisions on a hub. > netstat -i on my desktop PC shows collisions on the ppp tun0 > interface. I haven't a clue what that means. I admit that this one is a bit puzzling to me, too. -- -Chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?404317EA-2E8C-45CD-9418-6493610D4D69>