It seems like a high timeout setting for dhcpcd makes it wait extra long time even when getting an IP-addres. Here are some numbers: timeout | actual time | result 10s | 20.555s | FAILURE 10s | 20.561s | FAILURE 10s | 20.564s | FAILURE 11s | 22.541s | FAILURE 11s | 22.545s | FAILURE 12s | 16.646s | SUCCESS 12s | 16.764s | SUCCESS 12s | 16.987s | SUCCESS 20s | 20.568s | SUCCESS 20s | 20.578s | SUCCESS 25s | 25.567s | SUCCESS 25s | 25.979s | SUCCESS 30s | 29.030s | SUCCESS 60s | 28.837s | SUCCESS 60s | 28.993s | SUCCESS 60s | 29.005s | SUCCESS Timeout was set in /etc/conf.d/net as dhcpcd_eth0="-HD -t <timeout>". Time was measured with "time /etc/init.d/net.eth0 start". According to this result, I should set the timeout to 12s to get the fastest system startup. But why could it not be as fast when setting it to anything, for example the default of 60s? What is going on? Is the DHCP-server hurrying to serve an addres if the client urges it to be fast? Reproducible: Always Steps to Reproduce: DHCP Client Daemon v.2.0.0
What DHCP server is installed and is it authorative? Also, do you see the same behaviour with other DHCP clients? Others are dhclient (net-misc/dhcp) pump and udhcpc (net-misc/udhcp).
