From: Rick Jones <rick.jones2@hp.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: netdev@vger.kernel.org
Subject: Re: [RFC] ethernet: avoid pre-assigned OUI values in random_ether_addr
Date: Fri, 13 May 2011 18:00:48 -0700 [thread overview]
Message-ID: <1305334848.8149.729.camel@tardy> (raw)
In-Reply-To: <1305333898.8149.715.camel@tardy>
> Well, then by a quick glance at
> http://standards.ieee.org/develop/regauth/oui/oui.txt it looks like
> there are more to add... (some overlap with your list, I've not checked
> the entire thing, how the name conflicts should be resolved I've no
> idea)
>
> raj@tardy:~$ grep ^02- oui.txt
> 02-07-01 (hex) RACAL-DATACOM
> 02-1C-7C (hex) PERQ SYSTEMS CORPORATION
> 02-60-86 (hex) LOGIC REPLACEMENT TECH. LTD.
> 02-60-8C (hex) 3COM CORPORATION
> 02-70-01 (hex) RACAL-DATACOM
> 02-70-B0 (hex) M/A-COM INC. COMPANIES
> 02-70-B3 (hex) DATA RECALL LTD
> 02-9D-8E (hex) CARDIAC RECORDERS INC.
> 02-AA-3C (hex) OLIVETTI TELECOMM SPA (OLTECO)
> 02-BB-01 (hex) OCTOTHORPE CORP.
> 02-C0-8C (hex) 3COM CORPORATION
> 02-CF-1C (hex) COMMUNICATION MACHINERY CORP.
> 02-E6-D3 (hex) NIXDORF COMPUTER CORPORATION
>
> The ieee's list doesn't have any 52's though.
It does have some A's though:
~$ grep ^.[26AE]- oui.txt
[the aforementioned 02's]
AA-00-00 (hex) DIGITAL EQUIPMENT CORPORATION
AA-00-01 (hex) DIGITAL EQUIPMENT CORPORATION
AA-00-02 (hex) DIGITAL EQUIPMENT CORPORATION
AA-00-03 (hex) DIGITAL EQUIPMENT CORPORATION
AA-00-04 (hex) DIGITAL EQUIPMENT CORPORATION
which if I've not botched my bits has the locally administered bit set.
rick
next prev parent reply other threads:[~2011-05-14 1:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-14 0:17 [RFC] ethernet: avoid pre-assigned OUI values in random_ether_addr Stephen Hemminger
2011-05-14 0:28 ` Rick Jones
2011-05-14 0:32 ` Stephen Hemminger
2011-05-14 0:44 ` Rick Jones
2011-05-14 1:00 ` Rick Jones [this message]
2011-05-14 6:28 ` Bill Fink
2011-05-16 14:29 ` Rick Jones
2011-05-15 19:46 ` Eric Dumazet
2011-05-15 20:20 ` Joe Perches
2011-05-15 21:10 ` Eric Dumazet
2011-05-16 15:46 ` Stephen Hemminger
2011-05-20 19:01 ` Stephen Hemminger
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=1305334848.8149.729.camel@tardy \
--to=rick.jones2@hp.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.