From: Ryan Anderson <ryan@michonline.com>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>,
linux-kernel@vger.kernel.org, abraham@2d3d.co.za
Subject: Re: ethtool documentation
Date: Tue, 6 Aug 2002 22:54:10 -0400 [thread overview]
Message-ID: <20020807025410.GG24032@mythical.michonline.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1020806151104.25149A-100000@chaos.analogic.com>
> The EEPROM (SEEPROM) on these NICS is used to contain the startup
> configuration bits and the IEEE Station Address. This must be a
> unique number that is assigned so that there is no other such
> number in (preferably) the world, and certainly in the LAN.
> If you let a user write to this area, you will allow the user
> to destroy the connectivity on a LAN.
>
> If you provide an ioctl() to write new SEEPROM contents, it had
> better be disabled in code that user's (any, including root)
> can execute because, if caught, your company may lose it's IEEE
> Station Addresses and never again be allowed to configure Ethernet
> Controllers.
I think you overstate the seriousness here - it's not unheard of for
manufacturers to ship hardware with duplicate MAC addresses - a trivial
search on Google turns up Cisco as one offender:
http://www.cisco.com/warp/public/770/7.html
>
> 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.
Worse than GE?
http://www.gefanuc.com/support/plc/m030202.htm
Being able to permanently fix a screwed up card that duplicated another
card on my LAN would be nice, imo.
Of course, this assumes that IEEE Station Address == MAC address.
--
Ryan Anderson
sometimes Pug Majere
next prev parent reply other threads:[~2002-08-07 2:51 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-06 15:41 ethtool documentation Randy.Dunlap
2002-08-06 19:24 ` Richard B. Johnson
2002-08-06 19:40 ` Chris Friesen
2002-08-06 19:44 ` Randy.Dunlap
2002-08-06 20:03 ` Richard B. Johnson
2002-08-06 20:04 ` Randy.Dunlap
2002-08-06 20:36 ` Ben Greear
2002-08-06 21:15 ` Tim Hockin
2002-08-07 1:42 ` Richard B. Johnson
2002-08-07 3:33 ` Tim Hockin
2002-08-06 21:58 ` Alan Cox
2002-08-06 20:42 ` Randy.Dunlap
2002-08-06 22:27 ` Alan Cox
2002-08-19 19:00 ` Mark H. Wood
2002-08-07 1:57 ` Richard B. Johnson
2002-08-07 11:47 ` Alan Cox
2002-08-07 2:54 ` Ryan Anderson [this message]
2002-08-07 5:32 ` Dax Kelson
2002-08-07 6:30 ` Jonathan Lundell
2002-08-07 11:47 ` Alan Cox
2002-08-08 1:07 ` Peter Samuelson
2002-08-07 11:18 ` Richard B. Johnson
2002-08-07 12:05 ` Abraham vd Merwe
2002-08-07 18:44 ` Bernd Eckenfels
2002-08-07 20:16 ` erik
2002-08-07 8:02 ` Abraham vd Merwe
-- strict thread matches above, loose matches on Subject: below --
2002-08-08 9:18 Helge Hafting
2002-08-07 18:16 Leif Sawyer
2002-08-06 20:57 Leif Sawyer
2002-08-07 1:51 ` Richard B. Johnson
2002-08-07 10:53 ` Jamie Lokier
2002-08-05 11:46 Abraham vd Merwe
2002-08-05 15:42 ` Jeff Garzik
2002-08-05 19:06 ` Tim Hockin
2002-08-05 19:16 ` Jeff Garzik
2002-08-05 19:30 ` Jonathan Lundell
2002-08-05 20:20 ` Jeff Garzik
2002-08-06 10:17 ` Abraham vd Merwe
2002-08-06 10:07 ` David S. Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020807025410.GG24032@mythical.michonline.com \
--to=ryan@michonline.com \
--cc=abraham@2d3d.co.za \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=root@chaos.analogic.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox