From: Michael Zappe <zapman@zappe.us>
To: 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 17:20:51 -0700 [thread overview]
Message-ID: <424B4263.60804@zappe.us> (raw)
In-Reply-To: <20050331005435.G22455@mrwint.cisco.com>
Derek Fawcus wrote:
>On Wed, Mar 30, 2005 at 11:00:08AM -0700, Michael Zappe wrote:
>
>
>>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??),
>>
>>
>
>Pick a random number, set the local allocation bit (second bit on wire)
>and then test the address to see if anyone responds to it.
>
>Didn't DECnet do something like that?
>
>
>
Yeah, but you're not guaranteed a reply to the packet. It's a distinct
possibility that if you pick an address and a protocol, the other
machines stack may disregard it, i.e. blackholing pings, etc. There's
no good way to detect the collision. Theoretically you could use LLC to
check, but I wouldn't count on that being implemented correctly, if at
all... :-) If you're using locally administered addresses, you can
assume that valid NICs aren't going to have this address, and the chance
of a collision is low. (N in 16 million for N machines with the same
OUI.) So I guess that would work! :-)
DECnet actually had a deterministic algorithm for assigning MAC
addresses. You had an area number that was 6 bits, and a 10 bit node
number. Then you appended this to AA:00:04:00 to get the MAC address.
Multiple interfaces on the same machine all used the same MAC.
>DF
>
>
>
>>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
>>
>>
next prev parent reply other threads:[~2005-03-31 0:20 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
2005-03-30 23:54 ` Derek Fawcus
2005-03-31 0:20 ` Michael Zappe [this message]
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=424B4263.60804@zappe.us \
--to=zapman@zappe.us \
--cc=9fans@cse.psu.edu \
/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).