On 11.07.24 11:13, Marco d'Itri wrote:
On Jul 11, Philip Hands <p...@hands.com> wrote:
I've only seen netplan mentioned in passing in this thread so far.
Because I believe that Netplan is the answer to a question that nobody
asked here.
It has all the disadvantages of switching to a new configuration format,
but then it limits you to the features that it actually implements from
each backend and you have an indirection layer that must be used when
interacting with the backend daemon.
Yes, it brings a new configuration format. So do systemd-networkd and
NetworkManager.
Netplan's feature set is pretty comprehensive and certainly enough for a
default installation,
see its reference: https://netplan.readthedocs.io/en/stable/netplan-yaml/
But it's not an indirection layer that MUST be used. Should the features of
Netplan not be enough
for an advanced usecase, everybody is free to write configuration for the
underlying backend directly.
Netplan will not interfere with that and go out of the way. Just don't write
Netplan configuration
for a specific interface (or all of them) that you want to handle differently.
-- Lukas
