{"version":"1.0","provider_name":"Ami Sapphire's Notices","provider_url":"http:\/\/cwcyrix.nsupdate.info\/gnu-social\/public\/","type":"link","title":"Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Tuesday, 05-May-2026 01:15:21 EDT","author_name":"Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)","author_url":"http:\/\/cwcyrix.nsupdate.info\/gnu-social\/public\/index.php\/amisapphire","url":"http:\/\/cwcyrix.nsupdate.info\/gnu-social\/public\/notice\/239","html":"A bit of Ubuntu Server network config history:<br \/>\n<br \/>\nUbuntu 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.<br \/>\n<br \/>\nWith 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.<br \/>\n<br \/>\nWith 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.)<br \/>\n<br \/>\n--<br \/>\n<br \/>\nThat 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."}