3 ms·
Regardless of the styling, Netplan is such a footgun! I'm not convinced they'd define a sane schema for either. Like you've noticed... the trying logic is nai
by bravetraveler 3y ago
Regardless of the styling, Netplan is such a footgun!
I'm not convinced they'd define a sane schema for either.
Like you've noticed... the trying logic is naive. IIRC if this passes the mild sniff test it will go ahead and apply.
It can't realize changes on specific/named interfaces -- it insists on all or nothing.
- amluto 3y agoIn my rather short experience with netplan, I found: As above, you can’t ask netplan to sanity check a config. You can’t create a draft configuration, apply it, and save it if it works well. Every self-respecting network config system since at least Cisco IOS can do this (and does it by default!). Interface renaming can’t filter by being a physical interface, which means that the system tries, and fails, to rename VLANs, because their MAC matches something that should be renamed. (networkd can handle this, but the networkd config written by netplan is wrong.) Deleting virtual interfaces (e.g. VLANs) seems to be essentially unsupported, at least on 20.04. I think it’s slightly, but only slightly, better in newer releases. Not impressed.
- bravetraveler 3y agoOuch, quite a lot of 'learning'! Color me unimpressed, too. I've grown to enjoy NetworkManager. I know, like all things, that is probably controversial to some. Two things I really appreciate about it: - You can 'up' a connection/interface in an idempotent way; only changing whatever is needed. - it's *very* scriptable. Values can be given with +/- operators I was surprised/frustrated with networkd initially, but enjoy it now. It getting involved with packet forwarding was an unwanted surprise during a modernization effort.