9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Adrian Tritschler <ajft@ajft.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] unique MAC address allocation?
Date: Thu, 31 Mar 2005 09:53:13 +1000	[thread overview]
Message-ID: <424B3BE9.2020500@ajft.org> (raw)
In-Reply-To: <7844a6cbb71a5d167d58cb7c0302621b@collyer.net>

geoff@collyer.net wrote:
> MAC addresses aren't supposed to collide; they're supposed to be 
> globally unique.  So it's manufacturer's responsibility to get this 
> right.  Users who override the MAC address do so at their own risk.

Supposedly.

Unless they're the cheap taiwanese clones of NE2000 cards that my
previous employer bought about ten years ago.  The first couple worked,
since they were on different bits of cable, then everything went
pear-shaped.  50 *identical* reverse-engineered chinese copy cards anyone?

> I'm not convinced that there's a genuine problem here, let alone a 
> problem worth solving.

	Adrian

---------------------------------------------------------------
Adrian Tritschler                          mailto:ajft@ajft.org
Latitude 38°S, Longitude 145°E, Altitude 50m,      Shoe size 44
---------------------------------------------------------------


  reply	other threads:[~2005-03-30 23:53 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 [this message]
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=424B3BE9.2020500@ajft.org \
    --to=ajft@ajft.org \
    --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).