Netplan 1.0 Is Ready To Go For Ubuntu 24.04 LTS

[billyswong]

In this case it isn't replacing anything. It sits above the existing tools. I've never looked into the driving force behind creating it. The last time I had to mess with it was when I debootstrapped a minimal Mantic install when playing with ZFSBootMenu. Had to start dhcpcd manually to get an IP address initially. Then installed network-manager and created a Netplan config like this to let NetworkManager manage all the network devices automatically.

# Let NetworkManager manage all devices on this system
network:
version: 2
renderer: NetworkManager​

Speaking of Mantic, the new default setting in Ubuntu is to store network-manager config into netplan too

https://blog.slyon.de/2023/11/12/netplan-brings-consistent-network-configuration-across-desktop-server-cloud-and-iot/

[Developer12]

Netplan is simply a configuration/management tool on top of existing network utilities. It does not replace any of them. It was originally designed for enterprise situations where you want to copy a network configuration across a hundred workstations easily.

I'm talking about iproute2 not netplan.

[Developer12]

you can use ifconfig the same has always, simpley install nettools, this is a extra

Sure, but they're unmaintained and sooner or later they will disapear. A wrapper could be a simple shell script with a much lower maintenance burden.

[SpyroRyder]

LightDM is also still very alive and is nowadays the standard DM for most Linux Desktop environments: Xfce, Mate, Cinnamon, Unity, Budgie Desktop, LXDE. Only Gnome and KDE have different standard DMs.

Youre leaving out the part where kde and gnome together are at least 85% of whats used by linux users when taken as a whole

[Ananace]

I guess the main question there would be, have you actually looked into netplan and it's configuration tools, or have you just continued to try and force NetworkManager configurations on machines that utilize NetPlan and are running into the issue where netplan is managing those settings?

Yep, we were doing pure netplan on Ubuntu for a year or two, but it ended up costing us way too much in technician time, having to run techs over to restart peoples workstations because netplan had broken their network connection got old really quickly.
And the fact that the same base template could result in wildly different results for the resulting config on some machines wasn't helpful either, made debugging broken networking a royal pain, so we would just reinstall those machines a few times until netplan finally decided to generate valid configuration instead.

[aviallon]

Yaaay, another bugged tool that was totally uncalled for, spurring completely out of "not invented here" syndrome, replacing network-manager just for the sake of replacing it.

Upstart (OpenRC, systemd?), Mir (Xorg, Wayland?), Bazaar (Mercury, Git?), Ubuntu Touch (don't even go there), Unity (insert the other 9 million DEs here), LightDM (GDM, whatever, pick any), Snap (Flatpak, AppImage), UFW (firewalld), autoinstall (cloud-init), AppArmor (SELinux), so many success stories of Canonical trying to reinvent the wheel... and failing miserably.

Actually, AppArmor IS useful, especially in situations where SELinux is a pain or can't work (nested containers, ...)

[Old Grouch]

just hope that you didn't spell something wrong and loose all network).

I see what you did there.

[Old Grouch]

Why are you using Ubuntu in an enterprise environment if you don't like Canonical and their tools? Why aren't you using RHEL instead?

Do you prefer to hit yourself with a hammer or a mallet? It's a question of choosing whichever toolset has the fewest problems for your use-case. None are perfect.

[jabl]

I think netplan is a bit of a make-work project, extra complexity for its own sake. Originally IIRC they developed netplan because they wanted to use NetworkManager (NM) on desktop and systemd-networkd on servers, with the justification that NM is focused on desktop use cases. Meanwhile server-focused distros like RHEL use NM all the time, so this justification doesn't hold water. They could just have went with NM on both desktop and server, and forgot about netplan altogether.

[Avamander]

Is netplan able to generate wpa_supplicant conf files, systemd-networkd .network files and systemd-resolved .conf files?

For home use that's really all that's needed.

Yes. Just set the renderer to systemd-networkd.