la 5.9.2026 klo 16.30 Kyle Rose ([email protected]) kirjoitti:
>
> On Sat, Sep 5, 2026 at 9:17 AM Martin-Éric Racine <[email protected]> 
> wrote:
>>
>> > 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.
>>
>> Desipite this, dhcpcd is capable of waiting for interfaces to be up
>> before it delegates a prefix, so After or Before both work, which is
>> why I agreed to change it now, even though whatever changes Daniel has
>> in mind for the next ifupdown haven't materialized yet.
>
>
> Ok, I'll have to test this. I ran into a problem at some point in the recent 
> past in which I found my `pre-up sysctl -q something.addr_gen_mode=1` command 
> to disable automatic LL address generation wasn't being respected, and I 
> presumed it was because dhcpcd was touching that interface before ifupdown 
> configured it.

That is extremely unlikely caused by dhcpcd. The only aspect of LL6
that dhcpcd touches is that upstream implements his own homebrewed
code to generate stable-security LL6 addresses instead of letting the
kernel handle it via "net.ipv6.conf.*.addr_gen_mode=3". Nonetheless,
even that can be disabled using the "slaac hwaddr" configuration
option.

>> Anyhow, I suggest purging bin:dhcpcd and only keeping bin:dhcpcd-base.
>> Keeping bin:dhcpcd really doesn't make sense if you use ifupdown,
>> since it results in two instances of dhcpcd trying to control the
>> interfaces: one launched by the systemd unit and one by any instance
>> of the dhcp method in /etc/network/interface.
>
>
> I don't use the dhcp method at all. For context, this is what I've been 
> developing over the past few months:
>
> https://github.com/squarooticus/uplinkmgr
>
> I explicitly don't want ifupdown touching my WAN interfaces, because I need 
> dhcpcd to manage them according to a configuration written by uplinkmgr.

That would still be doable via a pre-up command in
/etc/network/interface on whichever interface calls the dhcp method.

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.

Martin-Éric

Reply via email to