la 5.9.2026 klo 18.05 Kyle Rose ([email protected]) kirjoitti: > > On Sat, Sep 5, 2026 at 10:59 AM Martin-Éric Racine > <[email protected]> wrote: >> >> 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. > > > The reason I went with manager mode is that the dhcpcd owners at some point > announced that they were going to stop supporting multiple instances of > dhcpcd on the same machine, so if you want multiple WANs managed by dhcpcd > you'd need to use manager mode going forward. And I found it worked well, > assuming I set up the virtual interfaces beforehand, which I did via ifupdown > because that's what I had experience with.
Upstream is still toying with eventually deprecating the possibility of running multiple instances of dhcpcd on the same host, but it hasn't happened yet. Even then, calling dhcpcd with the interface as a command argument e.g. via ifupdown would still work. > It's possible I want to just jettison ifupdown entirely and use a custom > script to handle it at boot time: I don't love that, but the cross-purposes > between all of these packages might make the result too fragile to rely on, > especially across upgrades that might make a machine suddenly unreachable on > boot. That's why I'd really love for dhcpcd to eventually become capable of setting up bridges and vlans. Once it can do that, ditching ifupdown and using dhcpcd.conf instead of /etc/network/interfaces would make sense. Even better would be to teach dhcpcd to read and use /etc/network/interfaces as-is to configure multiple interfaces. Since the file is generated by ifupdown at install time, it's never deleted, even after purging ifupdown. This would provide the smoothest transition from ifupdown+dhcpd to dhcpcd in manager mode. Debian could just deprecate ifupdown and install dhcpcd in manager mode from that point on. Martin-Éric
