<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFCC" text="#000000">
You still have the mistake to have a fixed address in a range.
Declare subnet 1.1.1.0 with no range statement. There is a risk that
an unknown client will be given the 1.1.1.2 address when it is
defined as a range.<br>
<br>
On 25/11/11 16:17, Jan Markus wrote:
<blockquote cite="mid:4ECFB19D.8050402@seznam.cz" type="cite">Dne
11/24/2011 05:10 PM, Simon Hobson napsal(a):
<br>
<blockquote type="cite">Jan Markus wrote:
<br>
<br>
<blockquote type="cite">host customer101public {
<br>
hardware ethernet 00:11:22:33:44:55;
<br>
fixed-address 1.1.1.2;
<br>
}
<br>
<br>
shared-network vlan101 {
<br>
subnet 10.0.0.0 netmask 255.255.255.248 {
<br>
range 10.0.0.2 10.0.0.6;
<br>
option routers 10.0.0.1;
<br>
}
<br>
<br>
subnet 1.1.1.0 netmask 255.255.255.252 {
<br>
range 1.1.1.2;
<br>
option routers 1.1.1.1;
<br>
}
<br>
}
<br>
<br>
Everything works all right. Now the customer wants to purchase
a new server and he wants me to
<br>
remove public IP from his old server, until he will send me
MAC address of the new one. So I just
<br>
changed MAC in the "host" declaration, restarted DHCP daemon
(even removed leases file).
<br>
<br>
But the old server is still "getting" the public IP address,
or it is "keeping" it. How can I
<br>
specify in the dhcpd.conf, that this IP is no more for him, so
he will lease address from the
<br>
10.0.0.0/29 pool?
<br>
</blockquote>
<br>
Your config is wrong - you have made a VERY common mistake. You
should NEVER have an address which
<br>
is both in a pool and in a fixed address statement. Because the
address is included in a pool it can
<br>
be leased to any device - including the one you want to exclude.
<br>
<br>
First step would be to remove the range statement as it isn't
needed and is more likely to cause you
<br>
problems.
<br>
<br>
Doing that will be sufficient to prevent the server leasing that
address.
<br>
<br>
If you need to specifically prevent a device getting an address
from a pool, you can add "deny
<br>
booting" :
<br>
<br>
host old-customer101public {
<br>
hardware ethernet 00:11:22:33:44:55;
<br>
deny booting;
<br>
}
<br>
<br>
</blockquote>
<br>
Thank you very much! That was it. I have finaly changed
configuration to this:
<br>
<br>
host customer101public {
<br>
hardware ethernet 00:11:22:33:44:55;
<br>
fixed-address 1.1.1.2;
<br>
}
<br>
<br>
shared-network vlan101 {
<br>
subnet 10.0.0.0 netmask 255.255.255.248 {
<br>
option routers 10.0.0.1;
<br>
pool {
<br>
range 10.0.0.2 10.0.0.6;
<br>
deny known-clients;
<br>
}
<br>
}
<br>
<br>
subnet 1.1.1.0 netmask 255.255.255.252 {
<br>
option routers 1.1.1.1;
<br>
}
<br>
}
<br>
<br>
<br>
-Jan
<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>