[Dnsmasq-discuss] DHCPDELINE --> disabling DHCP static address

[Simon Kelley]

André Steffensen wrote:
> Why did my dnsmasq do that by itself and where do I un-ignore the client? :)
>  
> Log from my Syslog:
> Dec 26 21:22:01 gw-klint dnsmasq[2069]: DHCPREQUEST(eth1) 
> 192.168.101.169 00:14:bf:3d:d9:25
> Dec 26 21:22:01 gw-klint dnsmasq[2069]: DHCPACK(eth1) 192.168.101.169 
> 00:14:bf:3d:d9:25 jpv11th
> Dec 26 23:19:50 gw-klint dnsmasq[2069]: DHCPREQUEST(eth1) 
> 192.168.101.169 00:14:bf:3d:d9:25
> Dec 26 23:19:50 gw-klint dnsmasq[2069]: DHCPACK(eth1) 192.168.101.169 
> 00:14:bf:3d:d9:25 jpv11th
> Dec 26 23:21:07 gw-klint dnsmasq[2069]: DHCPREQUEST(eth1) 
> 192.168.101.169 00:14:bf:3d:d9:25
> Dec 26 23:21:07 gw-klint dnsmasq[2069]: DHCPACK(eth1) 192.168.101.169 
> 00:14:bf:3d:d9:25 jpv11th
> Dec 26 23:21:07 gw-klint dnsmasq[2069]: DHCPDECLINE(eth1) 
> 192.168.101.169 00:14:bf:3d:d9:25
> Dec 26 23:21:07 gw-klint dnsmasq[2069]: disabling DHCP static address 
> 192.168.101.169
> Especially the last two lines? Can't figure out how it did happen by 
> itself, and can't find any traces in /etc/dnsmasq.conf or in 
> /etc/dnsmasq/dhcp.conf.
>  
> Result is that client cannot get DHCP anymore. :)
>  
> I spend quite some time investigating, but can't find any traces 
> anywhere.... Buuuwhooo?!?! :(
>  

The DECLINE comes from the DHCP client, not from dnsmasq. The client is 
announcing that it no longer accepts that address, so dnsmasq deletes 
the lease, and changes things so that the client will be offered a 
different address in the future.

The client should still be able to get a lease for a different address.

What's the client? It seems to be sending _both_ ACCEPT and DECLINE 
messages, which is very strange behavior, to say the least.

To remove the block on the static address, it's enough to restart dnsmasq.

Cheers,

Simon.