This wishlist report is, at least should be, outdated.
I acknowledge the "this used to work" ( and even "works that way on Red Hat Enterprise Linux Seven" )
It is fairly strange (stupid?) to create a new network device (the bridge) with identity (MAC-address) stolen from one of the underlaying members (the interfaces to be bridged).
If the actual question / wish is "I want a predictable MAC-address on brigde"
that can be done. Example /etc/systemd/network/10-netplan-mybridge.netdev
----8<---8<---8<----
[NetDev]
Name=mybridge
Kind=bridge
MACAddress=aa:d1:1e:25:e2:e7
This wishlist report is, at least should be, outdated.
I acknowledge the "this used to work" ( and even "works that way on Red Hat Enterprise Linux Seven" )
It is fairly strange (stupid?) to create a new network device (the bridge) with identity (MAC-address) stolen from one of the underlaying members (the interfaces to be bridged).
If the actual question / wish is "I want a predictable MAC-address on brigde" network/ 10-netplan- mybridge. netdev --8<--- 8<---- aa:d1:1e: 25:e2:e7
that can be done. Example /etc/systemd/
----8<-
[NetDev]
Name=mybridge
Kind=bridge
MACAddress=
[Bridge] --8<--- 8<----
DefaultPVID=42
VLANFiltering=yes
----8<-
Nope, current netplan.io has yet no support for such bridge paramater.