[Dnsmasq-discuss] Restricting dhcp-range to certain MAC prefixes?

Simon Kelley simon at thekelleys.org.uk
Fri Jun 22 11:49:30 BST 2007

Dermot Bradley wrote:
>>I put up a test release at
>>which implements the --tftp-unique-root flag which adds the address of
>>the client to the effective filename for TFTP.
> Thanks
> I'm just starting to have a look at that now. So what happens if I
> enable
> "--tftp-unique-root" and then a request comes in from a device where I
> don't have a directory created for its IP? Is it possible to have a
> default directory for all "unknown" devices?

That's no currently implemented, but it should be possible.
> Also related to my earlier question about restricting the DHCP range to
> specific MAC address prefixes. I how have 4 dhcp-range entries for Snom,
> Elmeg, Aastra, and Grandstream devices working fine. What happens if I
> now enable "--dhcp-authoritative" on this machine? Will dnsmasq then
> become authoritative for just those MAC prefixes (which is I want)
> or for any request on the network (which I assume it won't)?

dhcp-authoritative is not relevant here: that affects how dnsmasq deals 
with clients which have a lease (presumably from another DHCP server), 
but are unknown to dnsmasq.

If you want dnsmasq to ignore hosts which don't match one of you MAC 
prefixes, add


which says to ignore anything which isn't aastra, and isn't elmeg and .....

> SLA Mobile APAC, part of Stirk, Lamont & Associates Ltd.
> Registered Address: Thomas Andrews House, Queens Road, Belfast,  BT3 9DU
> Registered in Northern Ireland, Number: NI 47983. VAT Number: 832 2778 22

More information about the Dnsmasq-discuss mailing list