I an using Ubuntu Server as a KVM-host, relying on multiple anonymous bridges, and am suffering from this bug under 18.04.
For others needing a workaround: I do configure the bridges with netplan.io as usual and bring up the bridges by defining in file
/etc/systemd/network/10-netplan-brUp.network ---------------------------------------------- [Match] Name=brLAN* Name=brDMZ*
[Network] LinkLocalAddressing=no ConfigureWithoutCarrier=true ----------------------------------------------
bringing up multiple bridges following the naming scheme brLAN0, brLAN1, ... , brDMZ0, brDMZ1, ...
I do prefer this solution over some other workarounds using systemd service files or others, that I found on the net. Maybe this helps...
I an using Ubuntu Server as a KVM-host, relying on multiple anonymous bridges, and am suffering from this bug under 18.04.
For others needing a workaround: I do configure the bridges with netplan.io as usual and bring up the bridges by defining in file
/etc/systemd/ network/ 10-netplan- brUp.network ------- ------- ------- ------- ------- ----
-------
[Match]
Name=brLAN*
Name=brDMZ*
[Network] sing=no tCarrier= true ------- ------- ------- ------- ------- ----
LinkLocalAddres
ConfigureWithou
-------
bringing up multiple bridges following the naming scheme brLAN0, brLAN1, ... , brDMZ0, brDMZ1, ...
I do prefer this solution over some other workarounds using systemd service files or others, that I found on the net. Maybe this helps...