Re: looking for ethernet errors, collisions

2007-05-24 Thread Tom Judge
Chuck Swiger wrote: On May 23, 2007, at 4:25 PM, RW wrote: Well, there are plenty there on my sis0 interface (internal). [EMAIL PROTECTED] ~]$ netstat -i NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll sis0 1500 00:0a:e6:4a:56:c2 37989565 3980 36808783 57

Re: looking for ethernet errors, collisions

2007-05-23 Thread Javier Henderson
On Thu, 24 May 2007 00:25:43 +0100, RW wrote: > On Sat, 19 May 2007 21:10:25 -0400 > "Michael P. Soulier" <[EMAIL PROTECTED]> 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 >

Re: looking for ethernet errors, collisions

2007-05-23 Thread Chuck Swiger
On May 23, 2007, at 4:25 PM, RW wrote: Well, there are plenty there on my sis0 interface (internal). [EMAIL PROTECTED] ~]$ netstat -i NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll sis0 1500 00:0a:e6:4a:56:c2 37989565 3980 36808783 5749 6492857 sis0 150

Re: looking for ethernet errors, collisions

2007-05-23 Thread RW
On Sat, 19 May 2007 21:10:25 -0400 "Michael P. Soulier" <[EMAIL PROTECTED]> 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 plent

RE: looking for ethernet errors, collisions

2007-05-19 Thread Ted Mittelstaedt
turday, May 19, 2007 6:10 PM > To: Ted Mittelstaedt > Cc: freebsd-questions@freebsd.org > Subject: Re: looking for ethernet errors, collisions > > > On 17/05/07 Ted Mittelstaedt said: > > > Note that error counters are often bogus because so > > many cards today fil

Re: looking for ethernet errors, collisions

2007-05-19 Thread Michael P. Soulier
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). [EMAIL PROTECTED] ~]$ netstat -i NameMtu Network

RE: looking for ethernet errors, collisions

2007-05-17 Thread Ted Mittelstaedt
Note that error counters are often bogus because so many cards today filter errors out in hardware, long before the OS driver gets them. Ted > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Michael P. > Soulier > Sent: Thursday, May 17, 2007 8:26 AM >

RE: looking for ethernet errors, collisions

2007-05-17 Thread Michael K. Smith - Adhost
Hi: > -Original Message- > From: [EMAIL PROTECTED] [mailto:owner-freebsd- > [EMAIL PROTECTED] On Behalf Of Alex Zbyslaw > Sent: Thursday, May 17, 2007 9:09 AM > To: Michael P. Soulier > Cc: freebsd-questions@freebsd.org > Subject: Re: looking for ethernet errors, coll

Re: looking for ethernet errors, collisions

2007-05-17 Thread Alex Zbyslaw
Michael P. Soulier wrote: Hi, I'm used to this showing on the interface in the ifconfig output on Linux, but on FreeBSD it doesn't seem to show errors, collisions, etc. What's the standard way to show that on FreeBSD? "netstat -i" sounds like what you want. --Alex ___