Re: looking for ethernet errors, collisions
- From: RW <fbsd06@xxxxxxxxxxxxxxxxxxx>
- Date: Thu, 24 May 2007 00:25:43 +0100
On Sat, 19 May 2007 21:10:25 -0400
"Michael P. Soulier" <msoulier@xxxxxxxxxxxxxxxx> 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.
netstat -i on my desktop PC shows collisions on the ppp tun0
interface. I haven't a clue what that means.
_______________________________________________
freebsd-questions@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: looking for ethernet errors, collisions
- From: Javier Henderson
- Re: looking for ethernet errors, collisions
- References:
- looking for ethernet errors, collisions
- From: Michael P. Soulier
- RE: looking for ethernet errors, collisions
- From: Ted Mittelstaedt
- Re: looking for ethernet errors, collisions
- From: Michael P. Soulier
- looking for ethernet errors, collisions
- Prev by Date: Interrupt storm on an MS-1029 (AMD64)
- Next by Date: Re: looking for ethernet errors, collisions
- Previous by thread: RE: looking for ethernet errors, collisions
- Next by thread: Re: looking for ethernet errors, collisions
- Index(es):
Relevant Pages
|