11–20 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.
Seems not for long
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 configuration, but it won’t work, and you’ll have to do quite a bit of digging to find out why your vlan doesn’t exist as far as the kernel is concerned.
The latter one is nasty if you upgrade Ubuntu on a system where the management interface is on a vlan.
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…
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
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.
Ubuntu continuing to try to push their snowflakes. nmcli/nmtui works acceptably well. ifupdown-ng works great. 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.
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 really like "netplan try" actually. Maybe not exactly the same thing, but it has saved me once or twice.
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…
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…
There is a -state parameter for netplan apply which allows deleting VLANs, which has worked for me every time so far. What's the exact issue?
I never ran into your last issue, so I can't comment on that.