la 5.9.2026 klo 17.17 Kyle Rose ([email protected]) kirjoitti: > > On Sat, Sep 5, 2026 at 9:44 AM Martin-Éric Racine <[email protected]> > wrote: >> >> In any case, you're not the first one who runs into problems with >> dhcpcd in manager mode AND ifupdown both installed. Given this, I'll >> probably make bin:dhcpcd explicitly Conflicts with ifupdown. > > > Fair. I'll probably then have uplinkmgr provide its own service file for > dhcpcd which will allow me to order it relative to ifupdown however I need to.
For now, I'll at least remove all references to networking.service in both systemd units that we ship. From my perspective, the only important part is that we need to be have succesfully configured the network before reaching the global network.target that we declare as want/before. Whether networking.service or anything else also expects to have succeeded before network.target should not be our concern. Daniel/others are welcome to prove me wrong. > If you do this, though, I am curious how someone would use dhcpcd in manager > mode for any kind of non-trivial topology. E.g., how would a router configure > internal interfaces to prepare them for dhcpcd-mediated PD? Aside from a flat > custom script one-shot at boot time, are there recommended ways of > configuring interfaces other than ifupdown that won't then conflict with > dhcpcd's management of the WAN interfaces? I have a hard time believing that, > for example, NetworkManager or systemd-networkd will play nicely with > dhcpcd's manager mode: they also seem to want to control everything. That is precisely the problem: dhcpcd in manager mode, networkd and network-manager all try to control everything. However, calling dhcpcd via ifupdown's dhcp method keeps things inside a narrow manageable scope. Martin-Éric
