netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: Mark Smith <random@72616e646f6d20323030342d30342d31360a.nosense.org>
Cc: manfred@colorfullife.com, Gary.Spiess@Intermec.com, netdev@oss.sgi.com
Subject: Re: [PATCH] natsemi update 1/4 Use assigned MAC address
Date: Mon, 7 Jun 2004 14:46:54 -0700	[thread overview]
Message-ID: <20040607144654.540e7eee@dell_ss3.pdx.osdl.net> (raw)
In-Reply-To: <20040608071252.77f9d69e.random@72616e646f6d20323030342d30342d31360a.nosense.org>

On Tue, 8 Jun 2004 07:12:52 +0930
Mark Smith <random@72616e646f6d20323030342d30342d31360a.nosense.org> wrote:

> Hi Manfred, Gary, Stephen,
> 
> "But: I'm not sure that the change is required. What about just
> setting the mac to 0, and the actual mac address is set from user
> space? It's possible to set the mac address with"
> 
> Could I suggest if this is the solution implemented, setting the
> first octet of the MAC address to 0x02, as in a Locally Assigned
> MAC address ?
> 
> If an interface with an all zero's MAC address is added to a
> bridge, running the Spanning Tree Protocol (STP), it will always
> attempt to take over as the root bridge, unless STP root bridge
> priorities are being used. This would disrupt traffic on the
> attached LAN.

Actually, it won't let you add any interface to a bridge without
a valid ether address now (ie non-zero and not multicast).

> Ideally, assigning "zero" a MAC address which has almost no
> chance of disrupting STP or any other protocol could be useful.
> Maybe fe:ff:ff:ff:ff:ff ?
> 
> I think this would fit in with the "be conservative in what you
> send, liberal in what you receive" philosophy.
> 
> Regards,
> Mark.
> 
> ps, please CC on any replies, I'm not subscribed to the list yet.

  reply	other threads:[~2004-06-07 21:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-07 21:42 [PATCH] natsemi update 1/4 Use assigned MAC address Mark Smith
2004-06-07 21:46 ` Stephen Hemminger [this message]
2004-06-07 22:11   ` Mark Smith
2004-06-07 21:48 ` Stephen Hemminger
  -- strict thread matches above, loose matches on Subject: below --
2004-06-04 19:51 Gary N Spiess
2004-06-06 13:30 ` Manfred Spraul
2004-06-07 17:58   ` Gary N Spiess
2004-06-07 18:16     ` Stephen Hemminger
2004-06-07 21:12       ` Gary N Spiess
2004-06-08 18:31   ` Jeff Garzik

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=20040607144654.540e7eee@dell_ss3.pdx.osdl.net \
    --to=shemminger@osdl.org \
    --cc=Gary.Spiess@Intermec.com \
    --cc=manfred@colorfullife.com \
    --cc=netdev@oss.sgi.com \
    --cc=random@72616e646f6d20323030342d30342d31360a.nosense.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).