I have multiple machines (desktop and server versions) running 20.04 that have recently broken netplan configurations using bridged networks for the primary interface.
network: version: 2 ethernets: enp37s0: # lan1: #match: # macaddress: MAX_ADDRESS dhcp4: no optional: true bridges: br0: # interfaces: [lan1] interfaces: [enp37s0] addresses: [10.0.0.87/24] gateway4: 10.0.0.1
This had been working with macaddress matching. The interface
lan1 would be brought up, added to the bridge, not assigned any IP address, and br0 would be assigned the static IP I configured.
During a recent update/reboot
enp37s0 would not get added to the bridge. Removing the macaddress matching and specifying the interface by name would assign it to the bridge but it would still request a DHCP IP for the physical nic. On boot I now have br0 with a static IP and
enp37s0 attached to it but also with a DHCP assigned IP which breaks networking and networking is unusable until I manually remove the DHCP assigned IP on
What the heck changed and why isn't this basic VM host type config tested?