Comment 18 for bug 1418921

So I was looking at this bug and in looking into the "dhcp-sequential-ip" option for dnsmasq, the documentation seems to indicate that you shouldn't use it because it will cause ips to change if you let the lease expire. Specifically, the documentation[1] says:

--dhcp-sequential-ip
Dnsmasq is designed to choose IP addresses for DHCP clients using a hash of the client's MAC address. This normally allows a client's address to remain stable long-term, even if the client sometimes allows its DHCP lease to expire. In this default mode IP addresses are distributed pseudo-randomly over the entire available address range. There are sometimes circumstances (typically server deployment) where it is more convenient to have IP addresses allocated sequentially, starting from the lowest available address, and setting this flag enables this mode. Note that in the sequential mode, clients which allow a lease to expire are much more likely to move IP address; for this reason it should not be generally used.

My assumption is that a node fails to checkin for a while and then the ip gets assigned to the next device checking in. Then when the first node comes back it gets a different ip address. Where there any network/power interruptions on these nodes for ~1 hour (I think is default lease TTL)? It might be beneficial to remove the dhcp-sequential-ip configuration from dnsmasq which would reduce the likelihood of this occurring. Alternatively increasing the lease TTL might also reduce the likelihood of this occurring when a node is off/unavailable for extended periods of time. Can anyone confirm the case where one of these nodes might have been off/not checking in to provisioning for an extended amount of time?

[1] http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html