netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: Dmitry Mishin <dim@openvz.org>,
	netdev@vger.kernel.org, bridge@osdl.org, devel@openvz.org
Subject: Re: [Bridge] Bridge & it's MAC address question
Date: Fri, 15 Dec 2006 07:52:36 -0800	[thread overview]
Message-ID: <20061215075236.321e6a07@localhost.localdomain> (raw)
In-Reply-To: <20061215131908.GC11579@xi.wantstofly.org>

On Fri, 15 Dec 2006 14:19:08 +0100
Lennert Buytenhek <buytenh@wantstofly.org> wrote:

> On Mon, Oct 30, 2006 at 07:28:37AM -0800, Stephen Hemminger wrote:
> 
> > > Could somebody explain, why bridge uses minimal MAC of the attached devices?
> > > It makes this address instable, variable during bridge life-cycle, which is 
> > > not good for DHCP. For example, I want to attach multiple virtual devices to 
> > > one physical. Then, I need to make sure that after each virtual device 
> > > addition, bridge addr is not changed and still addr of the physical device.  
> > > Why not to use MAC of the first attached device?
> > 
> > The bridge physical address is the minimum of all the attached devices.
> > This is done because the STP standard requires it.  You can reset it
> > to be the same as any of the attached devices. This will not cause a
> > problem unless using STP.
> 
> You can in fact use any MAC address.  The STP standard recommends using
> the minimum address, as that is deterministic, and so it doesn't depend
> on the order in which you enslave subdevices.

So should restriction be lifted?
Please update wiki page FAQ, or I'll do it

  reply	other threads:[~2006-12-15 15:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-30 12:27 Bridge & it's MAC address question Dmitry Mishin
2006-10-30 15:28 ` Stephen Hemminger
2006-12-15 13:19   ` Lennert Buytenhek
2006-12-15 15:52     ` Stephen Hemminger [this message]
2006-12-15 16:04       ` [Bridge] " Lennert Buytenhek
2007-04-09 18:30         ` Sven Köhler

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=20061215075236.321e6a07@localhost.localdomain \
    --to=shemminger@osdl.org \
    --cc=bridge@osdl.org \
    --cc=buytenh@wantstofly.org \
    --cc=devel@openvz.org \
    --cc=dim@openvz.org \
    --cc=netdev@vger.kernel.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).