Looking at the code, the only obvious explanation is if you are
over-riding the hostname in the dnsmasq configuration, ie with dhcp-host.

In that case the client-provided name is ignored, including for the
purposes of dhcp-name-match. (This may be a bug, but it is also an
explanation.)


Simon


On 22/10/2019 15:43, James Feeney wrote:
> dnsmasq 2.80-4
> Arch Linux
> 
> /etc/dnsmasq.conf
> dhcp-name-match=set:printer,NPI*
> 
> $ journalctl -ab
> ...
> client provides name: NPI8C840E.prime
> ...
> tags: known, enp4s0
> 
> Uhm - so, did I miss something?  Or, is "dhcp-name-match=" broken?
> Why is the tag "printer" not been appended to the list of tags?
> 
> The similar "dhcp-vendorclass=" seems to work as expected.
> Is "dhcp-name-match=" different in some way?
> 
> 
> Thanks
> James
> 
> _______________________________________________
> Dnsmasq-discuss mailing list
> Dnsmasq-discuss@lists.thekelleys.org.uk
> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
> 


_______________________________________________
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

Reply via email to