Comment 39 for bug 1418921

Łukasz,

> What exactly are you trying to prove here?

1) dnmasq does NOT lease duplicate IPs to clients
2) nailgun should not assume the node IP is set in the stone
3) As a temporary work around (util nailgun get fixed) one could use /16 network instead of /24 one

> It's described in previous bug and it's described on dnsmasq mailing list http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2010q2/003881.html

That's not a bug, the reporter misunderstands the DHCP protocol.
The address is not assigned to the client until the server has ACK'ed it.
DHCPOFFERing the same IP to different clients is explicitly permitted by RFC 2131 [1]:

   2. Each server may respond with a DHCPOFFER message that includes an
      available network address in the 'yiaddr' field (and other
      configuration parameters in DHCP options). Servers need not
      reserve the offered network address, although the protocol will
      work more efficiently if the server avoids allocating the offered
      network address to another client.

[1] https://tools.ietf.org/html/rfc2131#section-3.1