Not configured to listen on any interfaces! and No subnet declaration for start

[Glenn Satchell]

If you look at the dhcpd man page, dhcpd takes an optional parameter
which is the name of the interface to listen on. I'm going to make a
wild guess here, but I bet you typed

  dhcpd start

when you really meant or needed, was

  service dhcpd start

or

  /etc/init.d/dhcpd start

and the dhcpd you ran was the executable in /usr/sbin rather than the
script in the start up directory. The exe then interprets the word
"start" as the name of an ethernet interface, doesn't find it and
barfs.

Simple solution is to use the explicit startup commands.

regards,
-glenn

>Date: Fri, 4 Apr 2008 17:25:26 -0700 (PDT)
>From: hong zhang <henryzhang62 at yahoo.com>
>Subject: Not configured to listen on any interfaces! and No subnet declaration 
for start 
>To: dhcp-users at isc.org
>
>List,
>
>dhcpd returns "No subnet declaration for start " and
>"Not configured to listen on any interfaces".
>
>Please let me know how to make it work.
>
>Here is my dhcpd.conf.
>
>#ddns-update-style none;
>#ignore client-updates;
>
>allow booting;
>allow bootp;
>
>next-server s227;
>default-lease-time 360;
>max-lease-time 720;
>
>option subnet-mask		255.255.0.0;
>
>subnet 190.0.0.0 netmask 255.255.0.0 {
>	range 190.0.0.100 190.0.0.110;
>	range 190.0.0.204 190.0.0.213;
>
>	filename "pxelinux.0";
>#	filename "elilo.efi";
>
>}
>
>
>------henry
>
>
>      
________________________________________________________________________________
____
>You rock. That's why Blockbuster's offering you one month of Blockbuster Total 
Access, No Cost.  
>http://tc.deals.yahoo.com/tc/blockbuster/text5.com
>