linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kent Borg <kentborg@borg.org>
To: "Howard, Marc" <Marc.Howard@kla-tencor.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Where to Put Ethernet MAC Addresses?
Date: Wed, 1 Oct 2003 17:12:47 -0400	[thread overview]
Message-ID: <20031001171247.I688@borg.org> (raw)
In-Reply-To: <2965658600EF2F41A0BEE2200DC0EE510499B0A7@ca1xpr01.kla-tencor.com>; from Marc.Howard@kla-tencor.com on Wed, Oct 01, 2003 at 01:43:43PM -0700


On Wed, Oct 01, 2003 at 01:43:43PM -0700, Howard, Marc wrote:
> I also select as the first 3 bytes of the MAC address the address
> assigned to a defunct company and the lower 3 bytes derived from the
> serial number.

I kinda like that outlaw approach, it fits in with one of my pet
notions: why must ethernet hardware be issued strictly unique MAC
addresses?  It is important that a given MAC address be unique on a
single network, but once a packet hits a router, it is OK to have a
duplicate on the next network, right?  (OK, maybe the router keeps a
single ARP table for all its directly connected networks and the
collision risk is one ply larger.)  If decent random numbers are
available (as they can be with Linux), why not adopt a random MAC
address?  Notwithstanding the "birthday paradox", 48 bits (or is it
effectively 47?) is still a whopping *big* space.  Given a decently
chosen random MAC address, how big does a network of random MAC
addresses have to be for the chance of a collision to be at all
dangerous?


Thanks,

-kb

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-10-01 21:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-01 20:43 Where to Put Ethernet MAC Addresses? Howard, Marc
2003-10-01 21:12 ` Kent Borg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-10-02 13:36 ARIBAUD Albert
2003-10-02  7:18 ARIBAUD Albert
2003-10-01 19:32 Kent Borg
2003-10-01 19:44 ` Gary Thomas
2003-10-01 19:48 ` Bret Indrelee
2003-10-01 20:27 ` Dan Malek
2003-10-03 13:33 ` Kent Borg

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=20031001171247.I688@borg.org \
    --to=kentborg@borg.org \
    --cc=Marc.Howard@kla-tencor.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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).