Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 6 Jul 2011 14:54:21 -0700
From:      YongHyeon PYUN <pyunyh@gmail.com>
To:        David Christensen <davidch@broadcom.com>
Cc:        Charles Sprickman <spork@bway.net>, David Christensen <davidch@freebsd.org>, "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>
Subject:   Re: bce packet loss
Message-ID:  <20110706215421.GC5559@michelle.cdnetworks.com>
In-Reply-To: <5D267A3F22FD854F8F48B3D2B523819385C32D912B@IRVEXCHCCR01.corp.ad.broadcom.com>
References:  <alpine.OSX.2.00.1107042113000.2407@freemac> <20110706201509.GA5559@michelle.cdnetworks.com> <5D267A3F22FD854F8F48B3D2B523819385C32D9115@IRVEXCHCCR01.corp.ad.broadcom.com> <20110706214016.GB5559@michelle.cdnetworks.com> <5D267A3F22FD854F8F48B3D2B523819385C32D912B@IRVEXCHCCR01.corp.ad.broadcom.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jul 06, 2011 at 02:47:24PM -0700, David Christensen wrote:
> > > > Data sheet says IfHCInBadOctets indicates number of octets received
> > > > on the interface, including framing characters for packets that
> > > > were dropped in the MAC for any reason.
> > >
> > > The IfHcInBadOctets counter says the controller received X bytes
> > > that were bad on the wire (collisions, FCS errors, etc.).  A value
> > 
> > I thought that too. But other counters such as FCS, FAE, Collisions,
> > Jabbers were all zero.
> > 
> 
> Also includes frames dropped due to an incorrect destination MAC
> address (i.e. perfect MAC filter mismatch).  This means the NIC 

Thanks, that explains it. :-)

> received a unicast frame for a MAC address that doesn't match the
> NIC's MAC address.  Very common on a hub and occurs occasionally
> on switches as well.
> 
> Dave
> 
> 



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110706215421.GC5559>