Live data from Hacker News

Ubuntu 24.04 LTS Committing to Netplan for Network Configuration

phoronix.com

31–40 of 52 posts

Re: Ubuntu 24.04 LTS Committing to Netplan for Network Configuration

#31
post #13
post #12

Hopefully netplan sucks less by then? Seriously, current versions are barely usable, and I don’t think I’m doing anything particularly hard. Want to verify your config before committing to it? Nope. Want to delete a vlan? Not happening without bypassing netplan. Want to bring up a vlan on an interface with a long name (which is the default on a fresh Ubuntu install with a NIC in a PCIe slot)? Netplan will accept the…

I was hoping that Canonical has higher standards when it comes to server software, as opposed to something like Snapcraft, but reading this makes me think that maybe they both were developed by the same team.

They were not developed by the same team.

Source : I’m a former Canonical employee.

Re: Ubuntu 24.04 LTS Committing to Netplan for Network Configuration

#33
post #13
post #12

Hopefully netplan sucks less by then? Seriously, current versions are barely usable, and I don’t think I’m doing anything particularly hard. Want to verify your config before committing to it? Nope. Want to delete a vlan? Not happening without bypassing netplan. Want to bring up a vlan on an interface with a long name (which is the default on a fresh Ubuntu install with a NIC in a PCIe slot)? Netplan will accept the…

I was hoping that Canonical has higher standards when it comes to server software, as opposed to something like Snapcraft, but reading this makes me think that maybe they both were developed by the same team.

Snapcraft is very much a thing on Ubuntu Server as well. It will "remind" you of that often when interfacing with apt

Re: Ubuntu 24.04 LTS Committing to Netplan for Network Configuration

#34
post #11

Earlier quoted context omitted.

> Debian so far has decided to go with Netplan for their nework stack on Debian Cloud images. Seems not for long

That sentence in the article almost reads as if it's missing a crucial word ("not"). Did Debian indeed decide to go with Netplan?

The copy/pasta is accurate. Debian is adopting it[1]

[1]: https://blog.slyon.de/2023/07/10/netplan-and-systemd-network...

Re: Ubuntu 24.04 LTS Committing to Netplan for Network Configuration

#35
post #29

Earlier quoted context omitted.

Netplan has oversimplified things to cater only to the simplest of topologies. The schema seems unable to capture the richness and modularity of actual networking technologies.

Examples?

Linux allows you to bind a subnet of addresses to an interface so that an application can listen on them. The netplan syntax is poorly thought out and overloads the CIDR notation to specify both the IP and netmask, so it is impossible to specify more than a single address.

I use this functionality in production for high availability configurations and effectively have to have a cron job to use 'ip' directly to fix things up.

Re: Ubuntu 24.04 LTS Committing to Netplan for Network Configuration

#36
post #12

Hopefully netplan sucks less by then? Seriously, current versions are barely usable, and I don’t think I’m doing anything particularly hard. Want to verify your config before committing to it? Nope. Want to delete a vlan? Not happening without bypassing netplan. Want to bring up a vlan on an interface with a long name (which is the default on a fresh Ubuntu install with a NIC in a PCIe slot)? Netplan will accept the…

Netplan has oversimplified things to cater only to the simplest of topologies. The schema seems unable to capture the richness and modularity of actual networking technologies.

What sort of topologies are you attempting?

I was able to set up fiber link aggregation with triple NICs and a custom VLAN and MTU with no issues. It supports bridges and child interfaces just fine.

Can you share your details?

Re: Ubuntu 24.04 LTS Committing to Netplan for Network Configuration

#37
post #5

Ubuntu continuing to try to push their snowflakes. nmcli/nmtui works acceptably well. ifupdown-ng works great. What problem is Ubuntu trying to solve?

> What problem is Ubuntu trying to solve? They're trying for lock-in and failing. Linux networking has been a solved problem since just about forever, and all this instability will do is cause people to abandon Ubuntu in favor of something less fickle.

This, I really don't understand that they want to create a diverging solution for something that already works really well. We don't need 15 different solutions to configure networking.

Imagine looking for a Java solution and the only response you find is in Kotlin... fucking annoying as I have to learn Kotlin to convert it to Java... The same thing with network configuration, you're looking for something that works on Debian and you only find a Ubuntu solution....

Re: Ubuntu 24.04 LTS Committing to Netplan for Network Configuration

#39
post #12

Hopefully netplan sucks less by then? Seriously, current versions are barely usable, and I don’t think I’m doing anything particularly hard. Want to verify your config before committing to it? Nope. Want to delete a vlan? Not happening without bypassing netplan. Want to bring up a vlan on an interface with a long name (which is the default on a fresh Ubuntu install with a NIC in a PCIe slot)? Netplan will accept the…

Netplan has oversimplified things to cater only to the simplest of topologies. The schema seems unable to capture the richness and modularity of actual networking technologies.

If by "only the simplest of topologies" you mean: 4 physical interfaces, bonded with active/backup failover and mii-monitoring, and 20 VLANs, turning off IPv6 on my public interface...

Honestly, I really like netplan, been using it for all my systems for ~5 years now.

Re: Ubuntu 24.04 LTS Committing to Netplan for Network Configuration

#40
post #5

Ubuntu continuing to try to push their snowflakes. nmcli/nmtui works acceptably well. ifupdown-ng works great. What problem is Ubuntu trying to solve?

> What problem is Ubuntu trying to solve? They're trying for lock-in and failing. Linux networking has been a solved problem since just about forever, and all this instability will do is cause people to abandon Ubuntu in favor of something less fickle.

It would be more useful for the various major distros to pitch in for easy, simple, congruent CLI, UI, declarative, and API configuration management for common advanced configuration.

Creating artificial lock-in that doesn't work is a double-barrel footgun blast.

The Ubuntu people are like the SystemD people: they just want to reinvent things from scratch and shove it down everyone's throats without any consideration.

Post reply on HN