Am 27.06.20 um 16:54 schrieb Mark Rogers: > Ah, therein lies my failing - I assumed OS supplied units wouldn't > need adapting... > > Adding After=network-pre.target to dhcpcd.service seems to have > resolved it, and taught me a lesson in the process. as often it depends - on machines with more than one network dhcpd is often bound to a specific interface which would fail when that is a bridge which don't exist before the network none of the 3 interfaces would exist here before my network-up.service dhcpd 1574 0.0 0.0 18820 10472 ? Ss Jun25 0:36 /usr/sbin/dhcpd -4 -f -cf /etc/dhcp/dhcpd-guest.conf -lf /var/lib/dhcpd/dhcpd-guest.leases -user dhcpd -group dhcpd --no-pid br-guest dhcpd 1575 0.0 0.0 19196 10764 ? Ss Jun25 0:37 /usr/sbin/dhcpd -4 -f -cf /etc/dhcp/dhcpd.conf -user dhcpd -group dhcpd --no-pid br-lan dhcpd 1589 0.0 0.0 19204 10848 ? Ss Jun25 0:31 /usr/sbin/dhcpd -4 -f -cf /etc/dhcp/dhcpd-vmware.conf -lf /var/lib/dhcpd/dhcpd-vmware.leases -user dhcpd -group dhcpd --no-pid vmnet8 _______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel