DHCPD starting before ETH0 gives error.

DHCPD is configured to only listen on eth0.

When it starts at boot time it states that there is no subnet for
0.0.0.0 defined in my dhcpd.conf file, so it exits.

This is because DHCPD is starting up at the same time as ETH0, and ETH0
is not yet up on the proper network.

If I start DHCPD after boot, it works just fine.

So the question is how to properly setup DHCPD so it starts on boot.

Should I define the subnet 0.0.0.0?

subnet 0.0.0.0 netmask 255.255.255.0 { }

Should I set DHCPD not to autostart, but have it start in rc.local?

What's the best way to handle this?

Thanks;

Edwin.

On Fri, 18 Nov 2005 08:13:03 -0800, edavid3001 shouted Hoy......

> DHCPD is configured to only listen on eth0.
>
> When it starts at boot time it states that there is no subnet for
> 0.0.0.0 defined in my dhcpd.conf file, so it exits.
>
> This is because DHCPD is starting up at the same time as ETH0, and ETH0
> is not yet up on the proper network.
>
> If I start DHCPD after boot, it works just fine.
>
> So the question is how to properly setup DHCPD so it starts on boot.
>
> Should I define the subnet 0.0.0.0?
>
> subnet 0.0.0.0 netmask 255.255.255.0 { }
>
> Should I set DHCPD not to autostart, but have it start in rc.local?
>
> What's the best way to handle this?
>
> Thanks;
>
> Edwin.

I would start it from /etc/rc.d/rc3.d at the proper time.
That is after the network has come up, say some place about S30ish.
The network on my scratch built system starts at S20. YMMV.

--
Some of us cynics would say that playing games is what Microsoft is
good at; and that people who use Linux have real work to do.

Tayo'y Mga Pinoy

Baho Utot <baho-(E-Mail Removed)> writes:

>On Fri, 18 Nov 2005 08:13:03 -0800, edavid3001 shouted Hoy......

>> DHCPD is configured to only listen on eth0.
>>
>> When it starts at boot time it states that there is no subnet for
>> 0.0.0.0 defined in my dhcpd.conf file, so it exits.

That is the default route.

>>
>> This is because DHCPD is starting up at the same time as ETH0, and ETH0
>> is not yet up on the proper network.

So, put in a delay in starting up dhcpd. Ie, put in a test to see if
default route is defined until route -n|grep '^0.0.0.0 ' ;do sleep 1; done
assuming of course that network is started before dhcpcd. ( you might want
to put a count in there so it would not hang waiting for default route
forever)


>>
>> If I start DHCPD after boot, it works just fine.
>>
>> So the question is how to properly setup DHCPD so it starts on boot.
>>
>> Should I define the subnet 0.0.0.0?
>>
>> subnet 0.0.0.0 netmask 255.255.255.0 { }

That makes no sense whatsoever. There exists no subnet which starts 0.0.0.


>>
>> Should I set DHCPD not to autostart, but have it start in rc.local?

Well it is started somewhere. Probably in /etc/rc3.d
Give it a higher number.
>>
>> What's the best way to handle this?
>>
>> Thanks;
>>
>> Edwin.

>I would start it from /etc/rc.d/rc3.d at the proper time.
>That is after the network has come up, say some place about S30ish.
>The network on my scratch built system starts at S20. YMMV.