[Dnsmasq-discuss] sometimes dhcp-script does not trigger on lease renewal

[Simon Kelley]

On 03/08/13 14:30, bugs at innuce.ch wrote:
>
>> If the expiry time of the lease doesn't change, then the script will
>> not be run. It's possible that the client is asking for the remaining
>> time to run on the lease when it "renews" rather than actually
>> extending it. That would explain what you're seeing.
>
> Clients are requesting a new lease.
>
>>
>>>
>>> I've run dnsmasq in no-daemon mode and with option --dhcp-log. the log
>>> didn't give me any hints. Do you have any??
>>
>> Look in the dnsmasq lease file, the first field is the expiry time. If
>> that doesn't change when the client renews, then that's the problem.
>>
>>
>>
>> Thinks:
>>
>> Does openWRT use the "Broken RTC" mode? I think it does. In that case,
>> dnsmasq doesn't store the expiry time in the leasefile, it stores the
>> lease length. That's much more likely not to change on a renewal.
>> Essentailly, the script gets called when the lease database changes,
>> and in Broken RTC mode, renewal doesn't change the lease database.
>>
> I've checked /tmp/dhcp.leases file, lease time changes, but script does
> not trigger ....
>>
>>

Please could you post all the output of

dnsmasq -v


Cheers,

Simon.