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. > > 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?
I would never use dhcpcd in manager mode if there's non-physical interfaces involved because dhcpcd lacks the ability to setup bridges and vlans, while ifupdown can do vlans out of the box and bridges with a simple plugin. Here's what I use with ifupdown: $ cat /etc/dhcpcd.conf require dhcp_server_identifier option domain_name_servers, domain_name, domain_search, interface_mtu option classless_static_routes, routers, sixrd, ntp_servers duid slaac private noipv4ll release timeout 0 vendorclassid interface enp3s0 ia_pd 1 br0 $ cat /etc/network/interfaces source /etc/network/interfaces.d/* allow-hotplug /en* iface enp3s0 inet dhcp post-up /usr/libexec/IPv4-MASQ_IPv6-Bridge $IFACE iface enp2s0 inet manual iface enp4s0 inet manual iface enp5s0 inet manual iface enp6s0 inet manual auto br0 iface br0 inet static bridge_ports regex (wl|enp6s|enp5s|enp4s|enp2s).* address 172.16.1.1 Another method, on a really complex host, would be to use dhcpcd as a backend for Netplan, instead of ifupdown. I personally have no experience of this, but it apparently works well. Martin-Éric
