DHCP server won't start at boot; starts fine afterwards

Tim Wunder (Lists) tim at thewunders.org
Thu Dec 24 08:57:43 PST 2009


Interesting problem that I'm not sure how to address:
When I boot my Fedora 11 box, dhcpd fails to start (it tries, but
instead of [OK] during bootup, the boot screen displays [FAILED].

The interesting thing is that once the computer is booted, I can login
as root and perform a 'service dhcpd start' and dhcpd starts right up
with no error messages.

dhcpd.conf:
$ cat /etc/dhcp/dhcpd.conf
ddns-update-style interim;
option routers 10.0.0.1;
option subnet-mask 255.255.255.0;
option domain-name-servers 208.67.222.222, 208.67.220.220;
option ip-forwarding on;

subnet 10.0.0.0 netmask 255.255.255.0 {
        range 10.0.0.100 10.0.0.110;
        default-lease-time 1200;
        max-lease-time 9200;
        host greg {
                hardware ethernet 00:0d:88:46:5a:18;
                fixed-address 10.0.0.120;
        }
}

ifconfig:
eth0      Link encap:Ethernet  HWaddr 00:17:31:90:38:E7
          inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::217:31ff:fe90:38e7/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:209791 errors:0 dropped:0 overruns:0 frame:0
          TX packets:183267 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:228487092 (217.9 MiB)  TX bytes:28960699 (27.6 MiB)
          Interrupt:26 Base address:0x2000

eth1      Link encap:Ethernet  HWaddr 00:17:31:90:2C:C8
          inet addr:10.0.0.1  Bcast:10.0.0.255  Mask:255.255.255.0
          inet6 addr: fe80::217:31ff:fe90:2cc8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:51993 errors:0 dropped:0 overruns:0 frame:0
          TX packets:64539 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:7359620 (7.0 MiB)  TX bytes:50188580 (47.8 MiB)
          Interrupt:25



192.168.1.2 connects to my FiOS router and 10.0.0.1 serves the internal
network.

The system is running squid/dansguardian in a transparent proxy
configuration to provide an internet filter, and they start and run just
fine.

This is in /var/log/messages (sorry for the nast word wrap):

Dec 23 18:03:39 home dhcpd: No subnet declaration for eth1 (no IPv4
addresses).
Dec 23 18:03:39 home dhcpd: ** Ignoring requests on eth1.  If this is
not what
Dec 23 18:03:39 home dhcpd:    you want, please write a subnet
declaration
Dec 23 18:03:39 home dhcpd:    in your dhcpd.conf file for the network
segment
Dec 23 18:03:39 home dhcpd:    to which interface eth1 is attached. **

Dec 23 18:03:39 home dhcpd:

Dec 23 18:03:39 home dhcpd:

Dec 23 18:03:39 home dhcpd: Not configured to listen on any interfaces!

Dec 23 18:03:39 home dhcpd:

Dec 23 18:03:39 home dhcpd: This version of ISC DHCP is based on the
release available
Dec 23 18:03:39 home dhcpd: on ftp.isc.org.  Features have been added
and other changes
Dec 23 18:03:39 home dhcpd: have been made to the base software release
in order to make
Dec 23 18:03:39 home dhcpd: it work better with this distribution.

Dec 23 18:03:39 home dhcpd:

Dec 23 18:03:39 home dhcpd: Please report for this software via the Red
Hat Bugzilla site:
Dec 23 18:03:39 home dhcpd:     http://bugzilla.redhat.com

Dec 23 18:03:39 home dhcpd:

Dec 23 18:03:39 home dhcpd: exiting.



Any clues?

Tim
-- 
Fedora release 11 (Leonidas), Linux 2.6.30.9-90.fc11.x86_64
KDE: 4.3.3 (KDE 4.3.3)
 15:21:08 up  5:31,  5 users,  load average: 1.18, 1.17, 1.12
"It's what you learn after you know it all that counts" John Wooden



More information about the Linux-users mailing list