21–30 of 52 posts
On the server side, this is one of the reasons my company is quickly moving all Ubuntu servers to Debian. It is so much easier to just edit /etc/network/interfaces.
network/interfaces feels so archaic. Then you add bonding, multiple interfaces, custom metrics, and IPv6 and you need to pray before reloading.
Anyway, to each its own I guess.
On the server side, this is one of the reasons my company is quickly moving all Ubuntu servers to Debian. It is so much easier to just edit /etc/network/interfaces.
I prefer plain Systeme-networkd. Basically you just create a network unit file and configure the interface with it. Basically like network/interfaces, just a little bit more cleaned up
On the server side, this is one of the reasons my company is quickly moving all Ubuntu servers to Debian. It is so much easier to just edit /etc/network/interfaces.
> Debian so far has decided to go with Netplan for their nework stack on Debian Cloud images. Seems not for long
Did Debian indeed decide to go with Netplan?
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…
Earlier quoted context omitted.
I prefer plain Systeme-networkd. Basically you just create a network unit file and configure the interface with it. Basically like network/interfaces, just a little bit more cleaned up
netplan can actually use systemd-networkd as a backend. It will just generate the unit files, and let systemd do the job.
If netplan would be an api driven tool via dbus or other ipc‘s to drive an ui I would understand the need. But as cli tool?! It’s a little bit stupid
Earlier quoted context omitted.
I prefer plain Systeme-networkd. Basically you just create a network unit file and configure the interface with it. Basically like network/interfaces, just a little bit more cleaned up
netplan can actually use systemd-networkd as a backend. It will just generate the unit files, and let systemd do the job.
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…
Good luck configuring wifi without netplan. Netplan is ok.
My laptop sure, but I have network manager on a gui for that. My netplan config on my laptop is literally
# Let NetworkManager manage all devices on this system
network:
version: 2
renderer: NetworkManagerHopefully 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…
Good luck configuring wifi without netplan. Netplan is ok.
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.
Earlier quoted context omitted.
netplan can actually use systemd-networkd as a backend. It will just generate the unit files, and let systemd do the job.
but what’s the point. It’s not that much work to create a unit file and configuration is always better in text form. If netplan would be an api driven tool via dbus or other ipc‘s to drive an ui I would understand the need. But as cli tool?! It’s a little bit stupid