Date: Mon, 31 Mar 2003 09:06:44 -0600 From: David Kelly <dkelly@hiwaay.net> To: "Jack L. Stone" <jackstone@sage-one.net> Cc: freebsd-questions@freebsd.org Subject: Re: Interface collisions Message-ID: <20030331150644.GB61141@grumpy.dyndns.org> In-Reply-To: <3.0.5.32.20030331082034.01414bf8@sage-one.net> References: <3.0.5.32.20030331082034.01414bf8@sage-one.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Mar 31, 2003 at 08:20:34AM -0600, Jack L. Stone wrote: > For the first time within the past few days, I've noticed collisions being > reported on the public NIC for one of the servers. I'm not sure if it means > the switch or the NIC is the culprit, so not sure which component may need > to be replaced. > > Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll > rl1 1500 <Link#2> 00:40:33:5b:bb:5f 6816063 0 7494432 0 66977 Lets see, 67e3 packets had to be retried within their first 64 octets out of 7.5e6 sent. Actually thats pretty darn good. But ideally if you are connected to a full duplex switch it should not happen. "Ideally". I have no idea how a switch behaves when its caches are momentarily full but I would guess forcing a "collision" might be a politer means with faster recovery to back off senders than to simply drop the packet. Then again a RealTek NIC is the scum at the bottom of the NIC bucket. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030331150644.GB61141>