[Dnsmasq-discuss] Update dnsmasq.leases after lease removed using dhcp_release utility?
DPolhamus at simventions.com
Fri Jan 10 18:20:59 GMT 2014
Thank you for the quick reply and sorry for not being clear.
The problem is the former. The client attempts to renew the lease and it _doesn't_ reappear in the leases file. The desired result is that it _would_ reappear.
I toggled the --dhcp-authoritative flag and that appears to give me the desired functionality and is safe for our configuration. Thank you for the help!
From: dnsmasq-discuss-bounces at lists.thekelleys.org.uk [mailto:dnsmasq-discuss-bounces at lists.thekelleys.org.uk] On Behalf Of Simon Kelley
Sent: Friday, January 10, 2014 1:07 PM
To: dnsmasq-discuss at lists.thekelleys.org.uk
Subject: Re: [Dnsmasq-discuss] Update dnsmasq.leases after lease removed using dhcp_release utility?
On 10/01/14 17:33, Drew Polhamus wrote:
> I am running dnsmasq 2.66 on Fedora 19. I am using the dhcp_release
> utility to manually expire a lease without restarting the dnsmasq
> service. I see the release occur and the lease info is also removed
> from the dnsmasq.leases file. However, when the same client again does
> a DHCPREQUEST, the leases file does not get updated as expected.
I'm not clear on what's happening, and what you want to happen. Is the problem that the client attempts to renew the lease and it _doesn't_ reappear, or that the client renews the lease and it does re-appear?
I think that either of these behaviours is available, controlled by the --dhcp-authoritative flag.
> Is this
> working as expected or possibly a bug based on cached information
> within dnsmasq? My software is using the dnsmasq.leases file to
> determine which clients are currently connected and is expecting that
> file to be up-to-date. Thanks for the help.
> Dnsmasq-discuss mailing list
> Dnsmasq-discuss at lists.thekelleys.org.uk
Dnsmasq-discuss mailing list
Dnsmasq-discuss at lists.thekelleys.org.uk
More information about the Dnsmasq-discuss