Description of problem: If NetworkManager controls the network, dhcpd daemon does not start at boot time. syslog error: ============================================== May 17 19:35:42 juice dhcpd: No subnet declaration for eth0 (no IPv4 addresses). May 17 19:35:42 juice dhcpd: ** Ignoring requests on eth0. If this is not what May 17 19:35:42 juice dhcpd: you want, please write a subnet declaration May 17 19:35:42 juice dhcpd: in your dhcpd.conf file for the network segment May 17 19:35:42 juice dhcpd: to which interface eth0 is attached. ** May 17 19:35:42 juice dhcpd: May 17 19:35:42 juice dhcpd: May 17 19:35:42 juice dhcpd: Not configured to listen on any interfaces! ============================================== Machine is configured correctly: 1. upon boot, manually restarting dhcpd works 2. if NetworkManager is chkconfig_ed off and network init script enabled instead, there are no problems with dhcpd on boot I am guessing this should be filed here rather than under dhcpd component? Version-Release number of selected component (if applicable): NetworkManager-0.7.0-0.9.3.svn3623.fc9.i386 How reproducible: Always Steps to Reproduce: 1. see above 2. 3. Actual results: see above Expected results: successful dhcpd start at boot time Additional info:
latest updates in f8 and f9 updates will honor the NETWORKWAIT=yes option from /etc/sysconfig/network, which will cause the startup to block until dhcpd is ready or until 10 seconds is up. You can also use NETWORKDELAY=<seconds> to wait longer if for example your DHCP server takes a long time. Ideally dhcpd would wait around until the network it was supposed to use showed up, but I guess it's a bit braindead.