9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Michael Zappe <zapman@zappe.us>
To: fgergo@gmail.com,
	Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] unique MAC address allocation?
Date: Wed, 30 Mar 2005 11:00:08 -0700	[thread overview]
Message-ID: <424AE928.6000501@zappe.us> (raw)
In-Reply-To: <bb1951070503300225251fd4fe@mail.gmail.com>

fgergo@gmail.com wrote:

>Not really plan9 specific, but
>1. does anybody know if and how MAC addresses are allocated to network
>card manufacturers?
>2. do manufacturers guarantee the uniqueness of MAC addresses they build?
>3. is it still true (was it ever true), that if I bought 2 NIC's,
>they'll have different MAC addresses?
>4. is it the responsibility of the OS to override the default MAC
>address if another card with the same (possibly overriden) MAC address
>was present on the LAN?
>
> thanks: gergo
>
>
Well, since my company makes network cards, I can probably help you
here! ;-)  Each vendor registers one or more 3 octet OUIs  from the
IEEE, which is used as the first 3 octets of a MAC address.  The
remaining 3 are up to the vendor to use.  Theoretically, all MAC
addresses are supposed to be unique.  For one vendor code you only have
16 million addresses available, so there is the possibility of wrap
around with MAC addresses -- it's up to the vendor to comply.  (Once you
have a practical deployed base of 90%, you can request a new OUI.) For
all practical purposes, you can assume that MAC addresses are unique.

For this part here is a good tutorial:
http://standards.ieee.org/regauth/oui/tutorials/lanman.html

As to question 4, nope.  The OS has no good way of determining a new MAC
address to override to (The OS doesn't have an OUI, and then how do you
pick the serial number after that??), and it's not considered a real
problem because of the uniqueness of MACs.  Not to mention you don't
even want to think about how a switch could get confused by the whole
situation... :-)

    Mike


  parent reply	other threads:[~2005-03-30 18:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-30 10:25 fgergo
2005-03-30 10:45 ` McLone
2005-03-30 11:20 ` geoff
2005-03-30 11:27   ` Charles Forsyth
2005-03-30 13:00     ` fgergo
2005-03-30 13:19       ` Artem Letko
2005-03-30 13:20       ` geoff
2005-03-30 23:53         ` Adrian Tritschler
2005-03-30 18:00 ` Michael Zappe [this message]
2005-03-30 23:54   ` Derek Fawcus
2005-03-31  0:20     ` Michael Zappe
2005-03-31  5:34       ` Martin C. Atkins
2005-03-31 14:54         ` Derek Fawcus
2005-03-31 15:00           ` boyd, rounin
2005-03-31  6:50     ` boyd, rounin
2005-03-31  6:53 boyd, rounin

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=424AE928.6000501@zappe.us \
    --to=zapman@zappe.us \
    --cc=9fans@cse.psu.edu \
    --cc=fgergo@gmail.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;
as well as URLs for NNTP newsgroup(s).