Insert delay in dhcp3-relay ?
zekkerj at gmail.com
Tue May 10 21:29:27 UTC 2011
2011/5/8 Benjamin <hexor38 at gmail.com>
> Le 05/05/2011 09:05, dhcp-users-request at lists.isc.org a écrit :
> You may care to look at the min-secs statement. Adding this to the
>> subnet declaration for the 'remote' subnet on each server should
>> achieve what you want.
>> The min-secs statement
>> min-secs seconds;
>> Seconds should be the minimum number of seconds since a client
>> trying to acquire a new lease before the DHCP server will
>> respond to
>> its request. The number of seconds is based on what the
>> reports, and the maximum value that the client can report is
>> seconds. Generally, setting this to one will result in the
>> server not responding to the client's first request, but
>> responding to its second request.
>> This can be used to set up a secondary DHCP server which
>> offers an address to a client until the primary server has
>> given a chance to do so. If the primary server is down, the
>> will bind to the secondary server, but otherwise clients
>> always bind to the primary. Note that this does not, by
>> permit a primary server and a secondary server to share a
>> pool of
>> dynamically-allocatable addresses.
>> -- Simon Hobson
> This is the function I need ! but ... I have test it, and it don't work, I
> put the min-secs in my range but the DHCP send an offer without delay
> (min-secs delay).
> Have you got an idea why the delay don't work ? ( I have tested out of the
> range (at the start of dhcpd.conf) but it's the same result...)
Shouldn't the clients still be bound to the secondary server when they
reboot with a valid lease? If I understood the documentation, in this case,
instead of broadcasting to find a new lease (and server), they'll unicast to
the last server...
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the dhcp-users