Re: proposal: Hybrid network stack for Trixie
On fre, 2024/09/20 at 13:12:36 +0200, Lukas Märdian wrote:
[snip]
> # Proposal
> My proposal is to enable a hybrid network stack, using systemd-networkd (on
> server/cloud/container/embedded systems) and NetworkManager (on desktop/laptop
> systems) unified through a common layer of Netplan configuration on top, to
> avoid fragmentation. This utilizes 3 tools that are under active upstream
> development and are already used as defaults in certain variants of Debian
> today. Furthermore, it allows people to control this stack on the native
> systemd-networkd/NetworkManager layer directly, while at the same time
> providing a way to describe network configuration that is common across Debian.
>
> I've repeated the reasons why I think a hybrid stack using Netplan is a
> feasible solution many times in previous threads, therefore I'd like to refer
> to a list of frequently asked questions, instead of spreading more reasons
> across more replies: https://wiki.debian.org/Netplan/FAQ
If at all possible, permit it to also run without systemd and/or
Network-Manager in the mix, for use-cases where all the bells and whistles
(and complications, and deep integration into things it does not need to
integrate into, nor necessarily should integrate into, like SSH server)
is not required.
To have Netplan as an option (which should be the case for systemd and
Network-Manager as well, options) seems very sensible IMHO.
> # Why
> The ifupdown package is a Debian only solution that is becoming a maintenance
> burden. We've had plenty of discussions over the years and consensus is that we
> want to get rid of it.
> Some variations of Debian have already moved forward with choosing a different
> stack, such as desktop/laptop installations (using NetworkManager) and cloud
> images (using Netplan+systemd-networkd). Also, ifupdown-ng exists as a modern
> re-implementation of the classic tooling, that strives to become drop-in
> [compatible].
Question: is ifupdown-ng geared at replacing ifupdown as soon as the next
major release, and should those that today use ifupdown migrate to
ifupdown-ng proactively? And does Netplan generate ifupdown-ng
configuration, or it this strictly a helper-tool for systemd/NM?
> # Compatibility
> We do not want to break existing systems or people that want to keep using the
> classic way of /etc/network/interfaces.
Very glad to hear that.
--
Kind regards,
/S
Reply to: