From: Artem Letko <aletko@gmail.com>
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 08:19:46 -0500 [thread overview]
Message-ID: <1055b16f05033005197c1c311d@mail.gmail.com> (raw)
In-Reply-To: <bb195107050330050032c26a94@mail.gmail.com>
Ethernet assumes unique MACs. Save yourself some time and look up
Ethernet II encapsulation. Isn't that the one Plan9 uses anyway?
On Wed, 30 Mar 2005 15:00:57 +0200, fgergo@gmail.com <fgergo@gmail.com> wrote:
>
> I was probably not precise and the question was not well thought
> through. What I wanted to ask was:
> I did override the MAC address - for some obscure reason, I can't
> remember - some 12 years ago on DOS via the packet driver interface,
> but is it the OS's responsibility to detect and possibly deal with MAC
> address collision or would the Ethernet layer take care of it?
>
> Instead of googling for "MAC address" etc., I should have searched for
> "Ethernet standard", days ago.
> The pages I needed were http://standards.ieee.org/faqs/OUI.html and
> http://standards.ieee.org/getieee802/802.3.html . Now I only have to
> read thorugh the standard. Probably the subject is not worth it (~1500
> pages?).
>
> The OS can take care of the problem, if the driver supports MAC
> address collision detection.
>
next prev parent reply other threads:[~2005-03-30 13:19 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 [this message]
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
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=1055b16f05033005197c1c311d@mail.gmail.com \
--to=aletko@gmail.com \
--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).