For an alternate point of view, unless does away with support for everything other systemd-networkd, please don't change. Dealing with my production systems, most of these systemd changes feel like change for change's sake, not progress. And I haven't had pleasant experiences with systemd-networkd in production environments.
On Thu, Sep 12, 2024 at 7:20 PM Uwe Sauter <[email protected]> wrote: > > Dear Proxmox team, hi all, > > > I stumbled across an article over at lwn.net: > > === > Debating ifupdown replacements for Debian trixie > > Debian does not have an official way to configure networking. Instead, it has four [1] recommended ways to configure > networking, one of which is the venerable ifupdown [2], which has been part of Debian since the turn of the century and > is showing its age. A conversation about its maintainability and possible replacement with ifupdown‑ng [3] has led to > discussions about the default network-management tools for Debian "trixie" [4] (Debian 13, which is expected in 2025) > and beyond. No route to consensus has been found, yet. > === > [1] https://wiki.debian.org/NetworkConfiguration > [2] https://salsa.debian.org/debian/ifupdown > [3] https://github.com/ifupdown-ng/ifupdown-ng > [4] https://www.debian.org/releases/trixie/ > > > Having made good experiences with systemd-networkd on Debian, Rocky Linux and Arch Linux I was wondering whether Proxmox > is working towards using systemd-networkd as the configuration tool in one of the next major versions? > > > Best, > > Uwe > > _______________________________________________ > pve-user mailing list > [email protected] > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user _______________________________________________ pve-user mailing list [email protected] https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
