Hi,
I just found another interesting thing in dnsmasq:
dnsmasq[5181]: DHCPDISCOVER(br-lan) 00:13:AA:BB:CC:DD
dnsmasq[5181]: DHCPOFFER(br-lan) 192.168.0.5 00:13:AA:BB:CC:DD
dnsmasq[5181]: DHCPREQUEST(br-lan) 192.168.0.5 00:13:AA:BB:CC:DD
dnsmasq[5181]: DHCPNAK(br-lan) 192.168.0.5 00:13:AA:BB:CC:DD address reserved
dnsmasq[5181]: DHCPREQUEST(br-lan) 192.168.0.5 00:13:AA:BB:CC:DD
dnsmasq[5181]: DHCPNAK(br-lan) 192.168.0.5 00:13:AA:BB:CC:DD address reserved
dnsmasq[5181]: DHCPDISCOVER(br-lan) 00:13:AA:BB:CC:DD
dnsmasq[5181]: DHCPOFFER(br-lan) 192.168.0.5 00:13:AA:BB:CC:DD
dnsmasq[5181]: DHCPREQUEST(br-lan) 192.168.0.5 00:13:AA:BB:CC:DD
dnsmasq[5181]: DHCPNAK(br-lan) 192.168.0.5 00:13:AA:BB:CC:DD address reserved
As you can see, dnsmasq offers an IP address but when the client tries to use
it, it gets an DHCPNAK...
The reason is another configuration error on my side:
/etc/ethers:
00:13:AA:BB:CC:DD 192.168.0.5
...
00:13:EE:FF:GG:HH 192.168.0.5
...
It would be nice if dnsmasq could detect such a situation and handle it more
gracefully...
fs
