Public bug reported:
After upgrading from a fully patched ubuntu-server 18.04 to 20.04 and
rebooting I noticed that some of my bridge interfaces defined in
/etc/network/interfaces would not come up while others would.
Bridges brought up at boot:
br_ext_prim
br_ext_sec
br_int_50
br_nat
Bridges m
Added the full syslog output covering the two boots aswell.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874515
Title:
20.04 does not bring up certain bridges
To manage notifications about this b
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1874515/+attachment/5358620/+files/20200423_syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874515
Title
Also noted behavior. After updating to 20.04 DHCP leases are not renewed
after boot. Unsure if related to above issues, but might be in the
ballpark.
Prior to the upgrade:
Apr 22 14:57:58 fancy dhclient[3068]: DHCPACK of 158.174.x.x from 212.116.x.x
Apr 22 19:35:49 fancy dhclient[3068]: DHCPREQUE
The difference between bridges managing to come up correctly and the
ones which does not seem to be that bridges defined as "inet manual"
fails and the ones defined as "inet static" succeeds. An example of a
bridge coming up correctly with a similar setup without the post-up
brctl addbr command;
Modifying /etc/network/interfaces to include the following post-up
completed networking startup successfully;
auto int0.51
iface int0.51 inet manual
vlan-raw-device int0
pre-up ifconfig $IFACE up
post-up brctl addbr br_nat_ext
post-down ifconfig $IFACE down
auto br
