Re: slow ethernet

["Dom De Vitto" <dom@DeVitto.com>]

Adam,
For want of flogging a dead horse.
Everybody usually starts with auto at both ends, then when/if it
screws up they check interface errors, notice weirdness and try fixing
one/both ends. Which seems/does solve the problem.

People aren't taking the time-consuming option first!
They are fixing a fault caused by dodgy autoneg at both ends,
which is almost always the default.

Dom
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Dom De Vitto                                       Tel. 07855 805 271
http://www.devitto.com                         mailto:dom@devitto.com
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Where do you want to go today?  Same as every day.... Windows Update.

-----Original Message-----
From: owner-misc@openbsd.org [mailto:owner-misc@openbsd.org] On Behalf Of
Adam
Sent: Tuesday, February 17, 2004 4:07 AM
To: Misc @OpenBSD
Subject: Re: slow ethernet

On Mon, Feb 16, 2004 at 08:05:20PM -0500, Greg Wooledge wrote:
> 
-snip a huge long explanation proving himself wrong

Dude, this is exactly why so many people think autoneg is broken, and its
really because *they* are broken.  Auto means auto, on both ends.
Of course you will get duplex mismatches if you force one side to something
random and hope the other side guesses the right thing.  Set both sides to
auto and it will be fine.

Adam