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-next>] [day] [month] [year] [list]
Message-ID: <20061215131908.GC11579@xi.wantstofly.org>
Date:	Fri, 15 Dec 2006 14:19:08 +0100
From:	Lennert Buytenhek <buytenh@...tstofly.org>
To:	Stephen Hemminger <shemminger@...l.org>
Cc:	Dmitry Mishin <dim@...nvz.org>, netdev@...r.kernel.org,
	bridge@...l.org, devel@...nvz.org
Subject: Re: Bridge & it's MAC address question

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.
-
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