<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffcc" text="#000000">
Just a silly question:<br>
When you tried to put the servers in the pools, did you remove the
classes? If you didn't, there is still multiple places from where to
get the info.<br>
<br>
If tftp server option is in pools, don't put them anywhere else.<br>
<br>
On 03/10/10 14:20, Glenn Satchell wrote:
<blockquote cite="mid:4CA87507.3070109@uniq.com.au" type="cite">On
10/03/10 20:16, Luka wrote:
<br>
<blockquote type="cite">I'm sorry for sending this message as a
new one and not as a reply, but
<br>
I haven't received your replies and had to find them in the
archives.
<br>
<br>
Glenn Satchell:
<br>
<br>
Possible workarounds include defining the option
tftp-server-name in the
<br>
pool, rather than the class. This may not be suitable if you
have many
<br>
pools.
<br>
<br>
Can you distinguish the two groups of machines any other way? Do
you
<br>
need two different tftp servers because the download file is
different?
<br>
---
<br>
<br>
Yes, there are many pools declared and I have tried to put the
tftp
<br>
option inside the pool with:
<br>
<br>
if( option vendor-class-identifier = "some-vendor" ) {
<br>
option tftp-server-name = "10.0.0.2";
<br>
}
<br>
<br>
but the clients still get the tftp from the a class.
<br>
<br>
</blockquote>
<br>
Hmm, what about using groups, something like this?
<br>
<br>
class "spa" {
<br>
match if (substring(hardware,1,3) = 00:01:02);
<br>
}
<br>
<br>
Subnets are declared as such:
<br>
<br>
# clients that need 10.0.0.1
<br>
group {
<br>
option tftp-server-name "10.0.0.1";
<br>
subnet 192.168.1.0 netmask 255.255.255.0 {
<br>
option routers 192.168.1.1;
<br>
option subnet-mask 255.255.255.0;
<br>
option broadcast-address 192.168.1.255;
<br>
pool {
<br>
allow members of "spa";
<br>
range 192.168.1.2 192.168.1.254;
<br>
}
<br>
}
<br>
subnet ... {
<br>
}
<br>
}
<br>
# clients that need 10.0.0.2
<br>
group {
<br>
option tftp-server-name "10.0.0.2";
<br>
subnet 192.168.2.0 netmask 255.255.255.0 {
<br>
option routers 192.168.2.1;
<br>
option subnet-mask 255.255.255.0;
<br>
option broadcast-address 192.168.2.255;
<br>
pool {
<br>
allow members of "spa";
<br>
range 192.168.2.2 192.168.2.254;
<br>
}
<br>
subnet ... {
<br>
}
<br>
}
<br>
<br>
# or without grouping - use the same class definition above, but
note
<br>
# there is no tftp-server defined in the class, only in the pool:
<br>
subnet 192.168.2.0 netmask 255.255.255.0 {
<br>
option routers 192.168.2.1;
<br>
option subnet-mask 255.255.255.0;
<br>
option broadcast-address 192.168.2.255;
<br>
pool {
<br>
allow members of "spa";
<br>
range 192.168.2.2 192.168.2.254;
<br>
option tftp-server-name "10.0.0.2";
<br>
}
<br>
}
<br>
<br>
regards,
<br>
-glenn
<br>
_______________________________________________
<br>
dhcp-users mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:dhcp-users@lists.isc.org">dhcp-users@lists.isc.org</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/dhcp-users">https://lists.isc.org/mailman/listinfo/dhcp-users</a>
<br>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Best regards
Sten Carlsen
No improvements come from shouting:
"MALE BOVINE MANURE!!!"
</pre>
</body>
</html>