lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 15 Dec 2006 07:52:36 -0800
From:	Stephen Hemminger <shemminger@...l.org>
To:	Lennert Buytenhek <buytenh@...tstofly.org>
Cc:	Dmitry Mishin <dim@...nvz.org>, netdev@...r.kernel.org,
	bridge@...l.org, devel@...nvz.org
Subject: Re: [Bridge] Bridge & it's MAC address question

On Fri, 15 Dec 2006 14:19:08 +0100
Lennert Buytenhek <buytenh@...tstofly.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
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ