netdev - Re: Bridge connectivity interruptions while devices join or leave the bridge

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]

Message-ID: <20180919100358.0ea95c20@xeon-e3>
Date:   Wed, 19 Sep 2018 10:03:58 -0700
From:   Stephen Hemminger <stephen@...workplumber.org>
To:     Ido Schimmel <idosch@...sch.org>
Cc:     Johannes Wienke <jwienke@...hfak.uni-bielefeld.de>,
        netdev@...r.kernel.org
Subject: Re: Bridge connectivity interruptions while devices join or leave
 the bridge

On Wed, 19 Sep 2018 19:45:08 +0300
Ido Schimmel <idosch@...sch.org> wrote:

> On Wed, Sep 19, 2018 at 01:00:15PM +0200, Johannes Wienke wrote:
> > This behavior of inheriting the mac address is really unexpected to us.
> > Is it documented somewhere?  
> 
> Not that I'm aware, but it's a well established behavior.

Not documented, has always been that way. It seems to be part of 802 standard maybe?
Anyway, if you set a MAC address of the bridge device it makes it sticky;
i.e it won't change if ports of bridge change.