[Dnsmasq-discuss] dhcp: mac address as "range selector"?
Simon Kelley
simon at thekelleys.org.uk
Sat Feb 18 10:06:26 GMT 2006
Lutz Pressler wrote:
> Hello,
>
> I have a setup with normal (workstations) and telephony devices,
> which have to get adresses from different ranges/networks on the
> same interface.
>
> This does work (since 2.26) with a configuration including
>
> dhcp-vendorclass=tel,alcatel.noe.0
> dhcp-range=net:tel,192.168.71.2,192.168.71.5,255.255.255.248,12h
> dhcp-range=192.168.169.80,192.168.169.99,255.255.255.0,12h
> dhcp-boot=net:tel,,,192.168.70.3
>
> Now I have the problem that SNOM telephones are not sending
> any vendorclass in the requests.
> I try to differenciate by ethernet address (00:04:13:*:*:*)
> as a work around.
> But how to select usage of the appropriate range?
>
> dhcp-host=00:04:13:*:*:*,net:snom,192.168.71.2
>
> does work for a single client, but
>
> dhcp-host=00:04:13:*:*:*,net:snom
>
> does not have the effect of using range and option definitions where
> network-id snom matches - which I think would be a logical extension.
> Is there a way to reach my goal that I don't see? If it's not possible
> at the moment: Simon, would you implement it?
I think it should work, but there's a limitation that only the first
matching "dhcp-host" line is used, so you couldn't have
dhcp-host=00:04:13:*:*:*,net:snom
_and_
another dhcp-host line (or /etc/ethers entry) to assign specific IP
address to a specific MAC address.
If it doesn't work, that's a bug.
>
> As a side note a related "issue": The definitions above do give "tel"
> devices an address from the normal range if the "tel" range is exhausted.
> I see no way to change that as it's not possible to negate network-id
> usage or mapping.
>
Yes it is, though the documentation is well hidden in the man page, I
will admit
dhcp-range=net:#tel,192.168.169.80,192.168.169.99,255.255.255.0,12h
Again, I've not tested that recently, so it is possible that it has
suffered bit-rot: I guess few people use it.
Cheers,
Simon.
> Thanks,
> Lutz
>
>
More information about the Dnsmasq-discuss
mailing list