| 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
| ||
|
Message-ID: <CAB=NE6UgOL_d3MYyhqiLAZw-TLsf4wDu3NTW3+Zv1rJ6Exkdhg@mail.gmail.com> Date: Tue, 18 Mar 2014 20:37:35 -0700 From: "Luis R. Rodriguez" <mcgrof@...not-panic.com> To: Stephen Hemminger <stephen@...workplumber.org> Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, kvm@...r.kernel.org, xen-devel@...ts.xenproject.org, bridge@...ts.linux-foundation.org Subject: Re: [PATCH 1/3] bridge: preserve random init MAC address On Tue, Mar 18, 2014 at 8:10 PM, Stephen Hemminger <stephen@...workplumber.org> wrote: > On Wed, 12 Mar 2014 20:15:25 -0700 > "Luis R. Rodriguez" <mcgrof@...not-panic.com> wrote: > >> As it is now if you add create a bridge it gets started >> with a random MAC address and if you then add a net_device >> as a slave but later kick it out you end up with a zero >> MAC address. Instead preserve the original random MAC >> address and use it. > > What is supposed to happen is that the recalculate chooses > the lowest MAC address of the slaves. If there are no slaves > it might as well just calculate a new random value. There is > not great merit in preserving the original defunct address. OK I'll go and add some changes for this then. Luis -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists