Leonardo Rodrigues wrote:
Hi,
with ISC DHCP i can have two expire times on the leases:
default-lease-time 86400;
max-lease-time 259200;
the default-lease-time is the one sent to the client ... and the
max-lease-time is the one used to keep to calculate the expire time of
Hi,
with ISC DHCP i can have two expire times on the leases:
default-lease-time 86400;
max-lease-time 259200;
the default-lease-time is the one sent to the client ... and the
max-lease-time is the one used to keep to calculate the expire time of
the leases that will be writt
Em 09/03/2010 10:47, Simon Kelley escreveu:
Great, that fix will go into the 2.53 release. Thanks for your help.
you're welcome and thanks for dnsmasq :)
--
Atenciosamente / Sincerily,
Leonardo Rodrigues
Solutti Tecnologia
http://www.solutti.com.br
Perette Barella wrote:
> On 2010年03月05日, at 12:16, Jan 'RedBully' Seiffert wrote:
>> And there is always the risk the new dnsmasq will not come up,
>> because you made a silly typo in the config, or something like
>> that. Depending on how fast you can rectify the situation, now you
>> have a real
Leonardo Rodrigues wrote:
>
>
> so dnsmasq offered the IP on the current lease despite of the
> 'wrong address' situation. This seems to be OK to me, that's what i
> would consider the expected behavior of a dhcp server in that situation.
>
Great, that fix will go into the 2.53 release.
built and running let's wait to see what'll happen when this
notebook came from another network and tries to release a wrong
address on our network.
and thank you very much for your attention :)
Simon, seems its working as expected now.
this is TODAY's log
root@sede:~/bac
