Bug 447036 - dhcpd does not start at boot if NetworkManager is enabled
dhcpd does not start at boot if NetworkManager is enabled
Product: Fedora
Classification: Fedora
Component: NetworkManager (Show other bugs)
i386 Linux
low Severity high
: ---
: ---
Assigned To: Dan Williams
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-05-17 04:00 EDT by Vladimir Kosovac
Modified: 2008-09-22 20:24 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-09-22 20:24:36 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Vladimir Kosovac 2008-05-17 04:00:15 EDT
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):


How reproducible:


Steps to Reproduce:
1. see above
Actual results:
see above

Expected results:
successful dhcpd start at boot time

Additional info:
Comment 1 Dan Williams 2008-09-22 20:24:36 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.