On Mon, 15 Jul 2024 at 14:36, Lukas Märdian <sl...@debian.org> wrote: > = "How to do networking on Debian?" = > > If we have to tell our users and sysadmins to do "X" on Debian server systems > (using ifupdown or potentially sd-networkd), while doing "Y" on Debian desktop > systems (using NetworkManager), while doing "Z" on Debian cloud systems (using > Netplan), while doing something totally different on RaspberryPi (or alike) > boards > that run a Debian server setup, but using WiFi as their primary network > interface, > that's just a really bad user experience. > > Using Debian should NOT feel like using different distros. And we really need > a > common way to do network configuration. With Netplan we can tell people to > just use > use the "dhcp4: true" setting (for example), which will work on all Debian > systems > and is automatically translated to the corresponding backend for > server/desktop/cloud/embedded usecases. > > All while giving sysadmins the flexibilty to fully utilize the underlying > network > daemon directly, if they feel like writing native configuration for it (or > don't > like Netplan).
Assuming that's really needed, and it's far from clear that different use cases should really use the exact same things, using network-manager everywhere would achieve the exact same result, without pulling in additional dependencies, and without being tied to the internal decisions made in Canonical that we cannot do anything to influence. Again, not your fault, but existing examples don't exactly inspire a lot of confidence in that regard: mir, upstart, unity, lxd...
