Re: proposal: dhcpcd-base as standard DHCP client starting with Trixie
On Wed, Jul 12, 2023 at 12:26:52PM +0100, Simon McVittie wrote:
> > From the discussions above, it seems that NetworkManager is relevant as well,
> > though, and is being pulled in whenever a desktop task is installed (in
> > addition to ifupdown or future systemd-networkd).
>
> What happens at the moment is:
>
> - if the tasks install NetworkManager, then d-i translates the install-time
> networking into NetworkManager configuration, together with essentially
> blank ifupdown configuration that makes ifupdown mostly a no-op (it
> might still try to bring up `lo`, but systemd brings that up as an "API"
> interface anyway, and probably so does NM if systemd didn't already)
Something also enables the ifupdown plugin in NM (and does something about
managed=true/false? I'm not familiar with this integration). If we remove
ifupdown this should be changed I think.
> - otherwise, d-i translates the install-time networking into ifupdown
> configuration
>
> Doing that, but with s/ifupdown/systemd-networkd/ throughout, makes
> sense to me. Is that what others in this thread had in mind?
>
> The practical result would be NM on desktop/laptop class systems, and
> systemd-networkd on server/embedded systems, which as it happens is what
> I'm already doing on my own machines.
I also wonder how complicated would it be to get WiFi configured in the
GUI-less setup. Currently it's easy if NM was installed for some reason
(with nmtui) and not easy otherwise.
Reply to: