On Sat, Sep 5, 2026 at 2:38 AM Martin-Éric Racine <[email protected]> wrote:
> On Fri, 04 Sep 2026 08:46:01 -0400 Kyle Rose <[email protected]> wrote: > > Package: dhcpcd > > Version: 1:10.3.2-6 > > Severity: normal > > > > Dear Maintainer, > > > > `dhcpcd.service` has `Before=networking.service`, which is basically > exactly opposite what you want in most cases. > > See bug #1121016 for details. Now I'm curious what ifupdown is planning for 0.9. It seems to me that it should stick to simple behaviors and leave anything complex to something with an interface more expressive than `ifup -a`. If they insist, I can see two possible paths forward: 1. Have `dhcp` method interfaces brought up automatically only if dhcpcd is already running in manager mode, and then have two oneshot services each run `ifup -a`, once `Before=dhcpcd.service` and again `After=dhcpcd.service`. 2. Replicate all of dhcpcd's configuration options in an interface stanza, with `ifup -a` managing `dhcpcd@` service instances for each such interface, doing some dependency ordering based on prefix delegation, etc., to ensure interfaces are configured in the proper order. This seems... really complex for something like ifupdown to do without breaking some decades-long reliance interest. Either way, I think a unilateral `Before=networking.service` is wrong, with your observation that "none of the interfaces that dhcpcd would delegate an IPv6 prefix to would be up yet" right on the money.
