Re: ethtool documentation

[Richard B. Johnson]

On Tue, 6 Aug 2002, Chris Friesen wrote:

> "Richard B. Johnson" wrote:
> 
> > Because of this, there is no such thing as 'unused eeprom space' in
> > the Ethernet Controllers. Be careful about putting this weapon in
> > the hands of the 'public'. All you need is for one Linux Machine
> > on a LAN to end up with the same IEEE Station Address as another
> > on that LAN and connectivity to everything on that segment will
> > stop. You do this once at an important site and Linux will get a
> > very black eye.
> 
> Can't we already tell cards (some of them anyway) what MAC address to use when
> sending packets?  This doesn't overwrite the EEPROM, but it does last for that
> session...
> 
> Chris

Sure you can. And it was assumed that the MAC address provided by
the manufacturer would always be used by the software for the MAC
address on the wire. However, 'software engineers' have decided
that they don't have to follow the rules, so they provide hooks
so you can use a MAC address of anything.  They even call it
"Local Administration...", which decoded means; "Screw the
committee".

But....
If you ever sell a controller that contains an address that was
not allocated to the 'producer', somebody is going to get very
angry. This means, to me, that if you ever write a new MAC address
to that card/board, you had better throw it away when you are done.

It's easier to make sure that the MAC address doesn't get changed.
You still "screw the comittee" locally, but you don't modify the
hardware.

Cheers,
Dick Johnson
Penguin : Linux version 2.4.18 on an i686 machine (797.90 BogoMips).
The US military has given us many words, FUBAR, SNAFU, now ENRON.
Yes, top management were graduates of West Point and Annapolis.