Issues with static assignment of 192.168.1.100 via DHCP

[caeci11ius]

OK, I've been having some issues with DHCP for the last two versions, but now I've narrowed the problem down a little further.

The system in question is running Ubuntu server 10.04...

There's no issues with getting an IP until I set it up to assign the same IP via DHCP every time. I've set it to assign this system 192.168.1.100...set it to any other value and it works fine, but it just won't assign that particular value. I thought it might be something to do with the range I had set up (192.168.1.100 - 200) but when I changed it to .99 - .200 it still wouldn't work. Incidentally, assigning .99 to the same machine works ok.

Any ideas why 192.168.1.100 would be special here and not want to assign? I've changed it to 192.168.1.190 in the meantime and now it's working fine...very, very weird...

[pbix]

In Gargoyle DHCP is managed by dnsmasq. I checked the source code and there is nothing special about the address in question. I doubt this issue is with dnsmasq.

It maybe that some other client has the address in question assigned. You can check /tmp/dhcp.leases to see what addresses are assigned.

You can also go to google and review 'man dnsmasq'. You may want to inspect the logread output for any error messages there or perhaps one of the command line options could help you figure out what is going on.

Good luck and please report back what you find.