[Dnsmasq-discuss] "multiple MAC addresses in a single dhcp-host" vs "multiple dhcp-host lines with the same IP address"

Pali Rohár pali.rohar at gmail.com
Mon May 17 10:40:56 UTC 2021


On Monday 17 May 2021 10:30:40 Jesus M Diaz wrote:
> Hello,
> 
> I am having an issue with this (see *[Dnsmasq-discuss] dnsmasq not
> overriding leases for static assignments* thread), but in summary, the
> problem is that this is not working for me: I have one dhcp-host
> configuration line with multiple mac-addr for one ip-addr, but dnsmasq
> don't assign the configured ip-addr if it was previously assign.
> 
> the configuration line:
> 
> dhcp-host=*:*:*:d0:4d:e3,set:mobile,192.168.0.217,xiaomi-a2
> 
> (I have also tried to configure all the explicit mac-add, not using
> wildcards, with same result)
> 
> the log from dnsmasq:
> 
> tail -f /opt/var/log/dhcp | grep d0:4d:e3
> May 17 09:11:38 cinemateka dnsmasq-dhcp[1726]: 1039677414 DHCPREQUEST(eth0)
> 192.168.0.217 96:8d:d4:d0:4d:e3
> 
> *May 17 09:11:38 cinemateka dnsmasq-dhcp[1726]: 1039677414 DHCPNAK(eth0)
> 192.168.0.217 96:8d:d4:d0:4d:e3 address in useMay 17 09:11:38 cinemateka
> dnsmasq-dhcp[1726]: not using configured address 192.168.0.217 because it
> is leased to a4:50:46:d0:4d:e3*
> May 17 09:11:41 cinemateka dnsmasq-dhcp[1726]: 3254867558
> DHCPDISCOVER(eth0) 96:8d:d4:d0:4d:e3
> 
> *May 17 09:11:41 cinemateka dnsmasq-dhcp[1726]: 3254867558 DHCPOFFER(eth0)
> 192.168.0.234 96:8d:d4:d0:4d:e3May 17 09:11:41 cinemateka
> dnsmasq-dhcp[1726]: not using configured address 192.168.0.217 because it
> is leased to a4:50:46:d0:4d:e3*
> May 17 09:11:41 cinemateka dnsmasq-dhcp[1726]: 402483634 DHCPDISCOVER(eth0)
> 96:8d:d4:d0:4d:e3
> May 17 09:11:41 cinemateka dnsmasq-dhcp[1726]: 402483634 DHCPOFFER(eth0)
> 192.168.0.234 96:8d:d4:d0:4d:e3
> May 17 09:11:41 cinemateka dnsmasq-dhcp[1726]: 402483634 DHCPREQUEST(eth0)
> 192.168.0.234 96:8d:d4:d0:4d:e3
> May 17 09:11:41 cinemateka dnsmasq-dhcp[1726]: 402483634 DHCPACK(eth0)
> 192.168.0.234 96:8d:d4:d0:4d:e3 xiaomi-a2
> 
> So, dnsmasq clearly identifies the client and it knows there is a static
> lease configured, but it ignores it.
> 
> Where is the problem? how can I fix this?
> 
> Thanks
> Jesus M

Hello! There is similar issue also for IPv6 addresses for which I have
sent a patch more than year ago. Last reset patch is available e.g. at:
https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2020q2/014044.html
but it looks like it dropped into Simon's spambox as he did not reply to
it...

-- 
Pali Rohár
pali.rohar at gmail.com



More information about the Dnsmasq-discuss mailing list