Am 22.04.20 um 16:44 schrieb Peter Morrow: > I'm trying to optimise our boot process and have started to look at > the time it takes for the network to come up (a single interface to be > routable) when using systemd-networkd: > > So, here systemd-networkd-wait-online.service seems to run for 3.5s - > I had initially though this is due to the RTT for DHCP but in doing a > packet capture for DHCP this isn't the case: > > Can anyone offer any suggestions for where I should look to try to > speed things up here? it *is* dhcp - it's that simple 10.587s network-up.service 9.116s network-wan-dhcp.service "network-wan-dhcp.service" in our case is simply started by "network-up.service" which is a simple selfmade unit using ip-commands and nothing else there is no way to make that simpler as in my setup [root@srv-rhsoft:~]$ systemctl status network-wan-dhcp.service ● network-wan-dhcp.service - Internet DHCP-Client Loaded: loaded (/etc/systemd/system/network-wan-dhcp.service; static; vendor preset: disabled) Active: active (running) since Tue 2020-04-21 19:24:58 CEST; 21h ago Main PID: 1296 (dhclient) Tasks: 1 (limit: 512) Memory: 4.6M CPU: 86ms CGroup: /system.slice/network-wan-dhcp.service └─1296 /usr/sbin/dhclient -4 -q --no-pid --request-options subnet-mask,routers br-wan _______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel