The fixed lease range is separate from the DHCP range so how is it possible that DHCP gave that fixed IP to another device? I have fixed leases, 10.0.0.1 - .9 and DHCP leases 10.0.0.10 - .49 A device with fixed lease 10.0.0.3 will have that ip forever, used or not used.
DHCP can give a fixed lease out if the fixed lease IP has been chosen to be within the Dynamic Range. This should not be done but currently IPFire does not stop you from doing that.
If the fixed lease has not been used for a while and the lease time has expired then it can be given to any other computer as the IP is part of the Dynamic Range. That is why they should be kept separate.
I am working on a bug fix to flag up if an overlapped ip is selected.
Bernhard Bitsch thank you for the RTFM. I had already read it, I read it a second time…that is why I asked the question. But, you couldn’t have known I had read it, or that I have the wiki bookmarked, that is my fault for not mentioning it in my original post. (Or maybe I read the words and couldn’t visualize the answer to my question from them… )
Sorry, if my answer was too short.
But often there are problems resulting from configurations with non-empty dissections of dynamic and fixed sets.
Was this your problem? You didn’t specify your sets used.
Actually, for some reason I thought once an address was moved to the fixed lease list, it was removed from the dynamic list. So, the IP address in question was in the dynamic pool.