On 2012-07-02 18:16, Helmut Hullen wrote:
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=...".
I (and many IPCop installations too) am using something like this for a
long time, without any problems:
# network: GREEN - 1, 192.168.1.200/24
dhcp-range=GREEN_1,192.168.1.101,192.168.1.199,28800
dhcp-option=GREEN_1,option:domain-name,olaf.local
dhcp-option=GREEN_1,option:dns-server,192.168.1.200
dhcp-option=GREEN_1,option:ntp-server,192.168.1.200
# network: BLUE - 1, 192.168.2.200/24
dhcp-range=BLUE_1,192.168.2.101,192.168.2.199,28800
dhcp-option=BLUE_1,option:domain-name,olaf.local
dhcp-option=BLUE_1,option:dns-server,192.168.2.200
dhcp-option=BLUE_1,option:ntp-server,192.168.1.200
Static hosts and options are defined in seperate files using
dhcp-hostsfile= and dhcp-optsfile=
There are several additional network cards, for internet connectivity,
PPPoE interface, DMZ, etc. DHCP assignments "just work".
Olaf
PS: I'd probably need to change and use set:<tag> and tag:<tag> to be
more precise.
_______________________________________________
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
