Date: Fri, 30 May 2003 18:59:18 +0200 From: =?iso-8859-1?Q?Sten_Daniel_S=F8rsdal?= <sten.daniel.sorsdal@wan.no> To: "Erwane Breton" <breton@erwane.net>, <freebsd-net@freebsd.org> Subject: RE: Collision on NIC Message-ID: <0AF1BBDF1218F14E9B4CCE414744E70F07DEB9@exchange.wanglobal.net>
next in thread | raw e-mail | index | archive | help
> > >=20
> > > Well, I don't see the problem.
> > >=20
> > > My math says that that's .03% collision rate, which is so=20
> deep in the
> > > noise as to be practically zero. What do you _think_ it=20
> should be?
> > >=20
> > Even Mr. Inventor of the ethernet himself regrets calling=20
> them collisions because
> > that term has a bad ring people unfamiliar with the=20
> technological detail.
> >=20
> > Pete
>=20
> So there are no answers or solutions ?
>=20
> Erwan
Answer:
Collisions are normal when your ethernet interface is set to =
Half-duplex.
In Half-duplex mode it can only either send or listen.
Changing both sides to full-duplex removes to collisions.
However: Changing only one side _always_ results in packet-loss!
Collisions does not mean packets lost.
10mbit Half-duplex from your computer to your ADSL modem does not mean
loss of performance.
The reason that your ADSL modem is at 10mbit Half-duplex is usually =
either;
* It does not support anything else (almost always the case)
* Auto-detect will in certain cases fail and there would be duplex =
mismatch=20
(packetloss) requiring operators assistance.
Either way, it is the way it is because then practically nothing can go =
wrong.
Solution: Do absolutly nothing.
You would (probably) have realized so many reasons not to ask this =
question if you
had spent 10 seconds on www.google.com. And don't tell me you have, =
because you havent.
- Sten
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0AF1BBDF1218F14E9B4CCE414744E70F07DEB9>