[Dnsmasq-discuss] Removing a feature does anyone rely on this?

[richardvoigt at gmail.com]

On Mon, Jul 2, 2012 at 11:16 AM, Helmut Hullen <Hullen at t-online.de> wrote:
> Hallo, Simon,
>
> Du meintest am 02.07.12:
>
>>>> dhcp-range may have an interface name supplied as
>>>> "interface:<interface-
>>> name>> ".
>
>>> I'd like to use this feature in many schools:
>>>
>>> eth0 and eth1 for the school clients in the LAN, eth2 for the
>>> private clients (especially in the WLAN). And eth3 for DSL/Router
>>> into the WAN.
>
> [...]
>
>> Note that you don't need to tell dnsmasq which dhcp-range goes with
>> which interface - it finds that automatically using the IP address
>> and netmask of the interfaces.
>
> May be.
> But our experiments failed.
>
> We wanted
>
>         dhcp-range=192.168.0.10,static,infinite
> #               (192.168.0.0/24) for the school computers
>         dhcp-range=192.168.18.10,192.168.31.250,30d
> #               (192.168.16.0/20) for the private machines
>
> and defined all school computers via "dhcp-host=...".
>
> Sometimes/often they got IP adresses from the "private" net.

Assign the #known (or newer, !known) tag to the private dhcp-range,
this way it won't ever be used for hosts which have static addresses.


>
> Adding/changing
>
>         dhcp-range=eth0,...
>         dhcp-range=eth1,...
>
> didn't help.
> There is a third NIC for the DSL/Router, defined as
>
>    no-dhcp-interface=eth2
>
> Viele Gruesse!
> Helmut
>
> _______________________________________________
> Dnsmasq-discuss mailing list
> Dnsmasq-discuss at lists.thekelleys.org.uk
> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss