<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFCC">
I still think it is completely doable. I include my own dhcpd.conf:<br>
<br>
~~~~~~~~~~~~~~~~~~~~<br>
# File: dhcpd.conf<br>
# Computer: Revo.s-carlsen.dk<br>
#<br>
#<br>
# Global parameters<br>
max-lease-time 1800;<br>
default-lease-time 1800;<br>
# Common settings.<br>
log-facility local0;<br>
server-name "revo.s-carlsen.dk";<br>
get-lease-hostnames false;<br>
<br>
# ddns update.<br>
ddns-update-style interim;<br>
deny client-updates;<br>
<br>
# class definitions<br>
class "gateway-1" {<br>
match hardware;<br>
}<br>
<br>
<br>
class "gateway-2" {<br>
match hardware;<br>
}<br>
<br>
<br>
class "gateway-4" {<br>
match hardware;<br>
}<br>
<br>
<br>
<br>
# Subnet Declarations<br>
shared-network hjemme{<br>
authoritative;<br>
subnet 192.168.16.0 netmask 255.255.255.0{<br>
option lpr-servers 192.168.16.38;<br>
option domain-name "s-carlsen.dk";<br>
option domain-name-servers 192.168.16.32;<br>
option subnet-mask 255.255.255.0;<br>
option ntp-servers 192.168.16.32;<br>
# B-NODE: Broadcast - no WINS<br>
option netbios-node-type 1;<br>
option smtp-server 192.168.16.32;<br>
pool{<br>
option routers 192.168.16.1;<br>
allow members of "gateway-1";<br>
range 192.168.16.50 192.168.16.127;<br>
}<br>
pool{<br>
option routers 192.168.16.2;<br>
allow members of "gateway-2";<br>
range 192.168.16.128 192.168.16.199;<br>
}<br>
pool{<br>
option routers 192.168.16.4;<br>
allow members of "gateway-4";<br>
range 192.168.16.200 192.168.16.240;<br>
}<br>
}<br>
subnet 192.168.61.0 netmask 255.255.255.0{<br>
max-lease-time 300;<br>
default-lease-time 150;<br>
pool{<br>
deny known-clients;<br>
deny members of "gateway-1";<br>
deny members of "gateway-2";<br>
deny members of "gateway-4";<br>
range 192.168.61.100 192.168.61.150;<br>
}<br>
}<br>
subnet 192.168.122.0 netmask 255.255.255.0{<br>
}<br>
}<br>
<br>
include "/etc/dhcp/subclass.conf";<br>
~~~~~~~~~~~~~~~~~~~~<br>
<br>
As you see I have a shared network, my unknown clients go to there
and have no router or anything.<br>
<br>
My known clients are grouped in those 3 classes, in my case by a
match hardware but anything could be used.<br>
<br>
In my main subnet 192.168.16.0/24 I have 3 pools each with its own
router and range.<br>
<br>
My thinking is that if you simply use the same setup, except your
class definitions are based on the hostname, it should work the same.<br>
<br>
This is a working setup, this mail is written from the network set
up this way.<br>
<br>
<br>
<div class="moz-cite-prefix">On 14/10/13 21.08, Prunk Dump wrote:<br>
</div>
<blockquote
cite="mid:CALr0QzFp_tnM4GmLEo2f_nnMZ7-1EN9iQxJDTBEKGsMyM68Nfg@mail.gmail.com"
type="cite">
<pre wrap="">2013/10/14 Doug Barton <a class="moz-txt-link-rfc2396E" href="mailto:dougb@dougbarton.us"><dougb@dougbarton.us></a>:
</pre>
<blockquote type="cite">
<pre wrap="">On 10/14/2013 11:46 AM, Sten Carlsen wrote:
</pre>
<blockquote type="cite">
<pre wrap="">
You may want to look at the man page for dhcpd.conf, the following
example is taken from that:
subnet 10.0.0.0 netmask 255.255.255.0 {
option routers 10.0.0.254;
# Unknown clients get this pool.
pool {
option domain-name-servers bogus.example.com;
max-lease-time 300;
range 10.0.0.200 10.0.0.253;
allow unknown-clients;
}
# Known clients get this pool.
pool {
option domain-name-servers ns1.example.com, ns2.example.com;
max-lease-time 28800;
range 10.0.0.5 10.0.0.199;
deny unknown-clients;
}
}
As you see here you can put options in subnets as well as pools. The
common options like router is in the subnet and the the more specific
options are in the pools together with the allows and denys.
</pre>
</blockquote>
<pre wrap="">
Wouldn't that require host declarations to define the known hosts?
Doug
_______________________________________________
dhcp-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:dhcp-users@lists.isc.org">dhcp-users@lists.isc.org</a>
<a class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/dhcp-users">https://lists.isc.org/mailman/listinfo/dhcp-users</a>
</pre>
</blockquote>
<pre wrap="">
My problem is that the ranges :
-> 172.16.0.1 to 172.16.199.254 (my PEDA domain)
-> 172.16.200.1 to 172.16.255.254 (my ORPEO domain)
are not "subnets". So I can't regroup my classes like this.
My two domains live in 172.16.0.0/16 !
ps : Effectively, "match class hosts" are not recognized as "known hosts"
Thanks for the help !
_______________________________________________
dhcp-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:dhcp-users@lists.isc.org">dhcp-users@lists.isc.org</a>
<a class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/dhcp-users">https://lists.isc.org/mailman/listinfo/dhcp-users</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Best regards
Sten Carlsen
No improvements come from shouting:
"MALE BOVINE MANURE!!!"
</pre>
</body>
</html>