Conversation

Notices

1. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Tuesday, 05-May-2026 00:46:40 EDT Clarissa Walker
   More tidying up the (quite) ancient scripts:
   
   * httpd.service no longer uses the apachectl script and now uses the httpd executable instead.
   * the netplan 00-installer-config.yaml file had a forgotten change for one of the network adapters.
   
   For the network setup, it's quite jank: IPv4 is handled by netplan and IPv6 is handled by systemd-network. This is due to a historical (2017) setup. Initial IPv4 migration to systemd-network actually broke this a few years ago (around 2019), and I never attempted to fix this since. It should be possible now, though. I also learned to not uninstall netplan at that time...
   • Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Tuesday, 05-May-2026 01:15:21 EDT Clarissa Walker

     in reply to
     A bit of Ubuntu Server network config history:
     
     Ubuntu Server, like a lot of distros, stored network configurations under a single filename: /etc/network/interfaces. Of course, starting and stopping them was a bit different.
     
     With version 17.04, they changed it to netplan. Both IPv4 and IPv6 are handled there, and configs were stored under the /etc/netplan directory. Starting and stopping network interfaces changed as well.
     
     With version 19.04, they changed it again to systemd-network. They helpfully migrated the configs to the appropriate /etc/systemd/network directory and had 'netplan' in the filenames. (Uninstalling netplan would be a bad idea here; you need renderer: networkd in a netplan .yaml file instead.)
     
     --
     
     That same year, I spent over 30 minutes attempting to migrate IPv4 over (IPv6 was successfully migrated and was disabled in netplan) but eventually gave up, mainly because I knew no better of the systemd-network formatting back then. So this pretty jank network interface setup that stayed for six years is a result of the double migration of interfaces.