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

[Jima]

  Some shots in the dark... :-)

On Thu, 14 Jun 2007, Dermot Bradley wrote:
> Now if I change the dhcp-range line to be
>
>   dhcp-range=net:aastra,10.10.10.50,10.10.10.80,12h
>
> then dnsmasq will provide DHCP allocations to "unknown" Aastra devices
> as well as any existing entries in /etc/ethers.
>
> However I want to do this sort of thing for *multiple* vendors.

  I've never tried this, but do either of these work?

dhcp-range=net:aastra,net:elmeg,net:grandstream,net:snom,10.10.10.50,10.10.10.80,12h

or:

dhcp-range=net:aastra,10.10.10.50,10.10.10.80,12h
dhcp-range=net:elmeg,10.10.10.50,10.10.10.80,12h
dhcp-range=net:grandstream,10.10.10.50,10.10.10.80,12h
dhcp-range=net:snom,10.10.10.50,10.10.10.80,12h

(or maybe with different IP ranges...not sure)

  According to the man page: "The optional network-id is a alphanumeric 
label which marks this network so thatdhcp options may be specified on a 
per-network basis.  When it is prefixed with net: then its meaning changes 
from setting a tag to matching it. Only one tag may be set, but more than 
one tag may be matched."  That, to me, suggests that my first suggestion 
ought to work.

> Secondly, I notice that DNSMASQ recently added TFTPD functionality. I've
> been using TFTPD-HPA so far but was considering using DNSMASQ for this
> in future. However I now need some specific functionality that neither
> DNSMASQ or TFTPD-HPA provide and so I've switched to WVTFTPD. This
> functionality allows the tftpd server to map tftp filename requests to
> differing actual filenames based on the requestor's IP address.

  You can't pass the filename-to-request to the client via DHCP? :-(

      Jima