I have followed the instructions in the /etc/network/interfaces file to ditch netplan and use ifupdown:
# To re-enable ifupdown on this system, you can run: # sudo apt install ifupdown As an extra measure I have removed netplan packages completely: ~# grep netplan .bash_history apt remove nplan netplan.io I have opened the bug against systemd, because I think it is the one responsible for the issue, but I could be wrong. It could be the unattended-upgrades package with the combination of systemd as well, or something different. I have written down the way my network configuration works so that enough information of my system is available - especially in this case where networking itself seems to have a hiccup. Weirdly enough my virtual bridge (configured via the same /etc/network/interfaces file) supporting my VMs running on the server has not lost its IP configuration. This + Joi's experience indicate to me that this is not an issue of how the network configuration is applied on the server, it is an issue of something on a lower level possibly, and the loss of network connection is just an inconvenient result, and not the issue itself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823871 Title: After unattended-upgrade of systemd IP configuration removed from interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
