la 25.10.2025 klo 15.34 Marvin Gülker ([email protected]) kirjoitti: > > Dear all, > > I used ifupdown just out of habit like I always did. So, what I did now is to > remove ifupdown alltogether and replaced it with pure dhcpcd, which is > started on boot via a systemd service file dhcpcd.service, which seems > to do just the correct things. Installing it pulled in and enabled > wpa_supplicant > for some reason, which I do not need on a server, but that was just a > oneliner to disable wpa_supplicant.service again. My machine now > properly pulls both an IPv4 and IPv6 address via DHCP. > > So, my problem is “solved” now. I leave it to you to decide what to do > with the interaction of ifupdown and dhcpcd.
For most cases, using a daemonized dhcpcd indeed is the best approach precisely because it seamlessly handles IPv4 and IPv6 configuration. IMHO, nowadays ifupdown only is useful for cases where someone needs to create bridges or vlans using a simplified syntax. For everything else, dhcpcd already covers most usage cases, including static IP addresses and IPv6PD. If it ever offered the capability of creating bridges and vlans, dhcpcd would be a perfect ifupdown replacement. Martin-Éric
