Simon McVittie <s...@debian.org> writes: > On Tue, 09 Jul 2024 at 16:21:16 +0200, Ansgar 🙀 wrote: >> On Tue, 2024-07-09 at 22:44 +0900, Simon Richter wrote: >> > I believe NM does not have a fixed configuration format, but only a dbus >> > API. >> >> It's perfectly fine to edit configuration files for NM manually, see >> man:nm-settings-keyfile(5). > > ... and debian-installer already knows how to write out these files, > and has done so for more than a decade if I'm reading correctly. This is > not a recent innovation, and anyone who has installed our default desktop > environment in the last few years - especially if they used wifi during > installation - has been relying on this code path. > > <https://salsa.debian.org/installer-team/netcfg/> is responsible > for converting the network configuration that was used temporarily in > the d-i environment into a NM configuration file if NM is installed, > or an ifupdown configuration otherwise. Writing the equivalents into > /etc/systemd/network for systemd-networkd would presumably not be rocket > science, it's a simple .ini-like syntax similar to the one NM uses.
We're just in the process of adding support for netplan as well: https://salsa.debian.org/installer-team/netcfg/-/merge_requests/9 I've only seen netplan mentioned in passing in this thread so far. It seems like it is exactly what we need as a replacemtent for ifupdown (given that is what it's designed for AFAICT -- I've not yet tried it out myself though) and it already supports configuring systemd-networkd, so seems like a more sensible route than duplicating that effort in D-I. See: https://netplan.readthedocs.io/ Cheers, Phil. -- Philip Hands -- https://hands.com/~phil
signature.asc
Description: PGP signature
