[Dnsmasq-discuss] dnsmasq giving new addresses despite of leases file

Leonardo Rodrigues leolistas at solutti.com.br
Tue Mar 9 13:18:13 GMT 2010


>     built and running .... let's wait to see what'll happen when this 
> notebook came from another network and tries to release a wrong 
> address on our network.
>
>     and thank you very much for your attention :)

     Simon, seems its working as expected now.

this is TODAY's log

root at sede:~/backup/a/etc/dnsmasq# logread | grep dnsmasq | grep 
00:1b:9e:4f:dc:fb
Mar  9 07:36:24 sede daemon.info dnsmasq-dhcp[2393]: DHCPREQUEST(eth1) 
192.168.1.191 00:1b:9e:4f:dc:fb
Mar  9 07:36:24 sede daemon.info dnsmasq-dhcp[2393]: DHCPNAK(eth1) 
192.168.1.191 00:1b:9e:4f:dc:fb wrong address
Mar  9 07:36:24 sede daemon.info dnsmasq-dhcp[2393]: DHCPREQUEST(eth1) 
192.168.1.191 00:1b:9e:4f:dc:fb
Mar  9 07:36:24 sede daemon.info dnsmasq-dhcp[2393]: DHCPNAK(eth1) 
192.168.1.191 00:1b:9e:4f:dc:fb wrong address
Mar  9 07:36:25 sede daemon.info dnsmasq-dhcp[2393]: DHCPDISCOVER(eth1) 
00:1b:9e:4f:dc:fb
Mar  9 07:36:25 sede daemon.info dnsmasq-dhcp[2393]: DHCPOFFER(eth1) 
192.168.8.156 00:1b:9e:4f:dc:fb
Mar  9 07:36:25 sede daemon.info dnsmasq-dhcp[2393]: DHCPDISCOVER(eth1) 
00:1b:9e:4f:dc:fb
Mar  9 07:36:25 sede daemon.info dnsmasq-dhcp[2393]: DHCPOFFER(eth1) 
192.168.8.156 00:1b:9e:4f:dc:fb
Mar  9 07:36:25 sede daemon.info dnsmasq-dhcp[2393]: DHCPREQUEST(eth1) 
192.168.8.156 00:1b:9e:4f:dc:fb
Mar  9 07:36:25 sede daemon.info dnsmasq-dhcp[2393]: DHCPACK(eth1) 
192.168.8.156 00:1b:9e:4f:dc:fb notevaldinei
Mar  9 07:36:25 sede daemon.info dnsmasq-dhcp[2393]: DHCPREQUEST(eth1) 
192.168.8.156 00:1b:9e:4f:dc:fb
Mar  9 07:36:25 sede daemon.info dnsmasq-dhcp[2393]: DHCPACK(eth1) 
192.168.8.156 00:1b:9e:4f:dc:fb notevaldinei
root at sede:~/backup/a/etc/dnsmasq#



grepping this MAC address from my yesterday's backup shows that the 
offered IP is the IP of the current valid lease

root at sede:~/backup/a/etc/dnsmasq# grep 00:1b dhcpd.leases
1270401733 00:1b:9e:4f:dc:fb 192.168.8.156 notevaldinei 01:00:1b:9e:4f:dc:fb
root at sede:~/backup/a/etc/dnsmasq#


     so dnsmasq offered the IP on the current lease despite of the 
'wrong address' situation. This seems to be OK to me, that's what i 
would consider the expected behavior of a dhcp server in that situation.


-- 


	Atenciosamente / Sincerily,
	Leonardo Rodrigues
	Solutti Tecnologia
	http://www.solutti.com.br

	Minha armadilha de SPAM, NÃO mandem email
	gertrudes at solutti.com.br
	My SPAMTRAP, do not email it







More information about the Dnsmasq-discuss mailing list