thanks for fast reply. You scared the hell out of me. I have 1k users in this config and every record have same pattern, all of this lines are in shared netowrk<br><br>#######################################################################################<br>
host m69 { hardware ethernet 00:0a:73:f9:e6:3a; fixed-address 172.16.10.69; filename "<a href="http://file.cm">file.cm</a>";}<br>class "M069" { match if binary-to-ascii(16, 8, ":", option agent.remote-id) = "0:a:73:f9:e6:3a"; spawn with option agent.remote-id; lease limit 1;}<br>
pool { allow members of "M069"; range 172.16.20.69; }<br><br>host m70 { hardware ethernet 00:0a:73:f9:e6:31; fixed-address 172.16.10.70; filename "<a href="http://file.cm">file.cm</a>";}<br>class "M070" { match if binary-to-ascii(16, 8, ":", option agent.remote-id) = "0:a:73:f9:e6:31"; spawn with option agent.remote-id; lease limit 1;}<br>
pool { allow members of "M070"; range 172.16.20.70; }<br><br>host m71 { hardware ethernet 00:0a:73:f9:e6:32; fixed-address 172.16.10.71; filename "<a href="http://file.cm">file.cm</a>";}<br>class "M071" { match if binary-to-ascii(16, 8, ":", option agent.remote-id) = "0:a:73:f9:e6:32"; spawn with option agent.remote-id; lease limit 1;}<br>
pool { allow members of "M071"; range 172.16.20.71; }<br><br>host m72... etc<br>##########################################################################################<br>and it would be very diffucult to rewrite it. In this pattern every modem should have only one CPE device connected, so pool provides only one ip address. As you can see the class and poll fields aren't between host braces, they're independent of each other. <br>
So what should i do now, should i rewrite entire config file ?<br><br>kind regards,<br>Jan<br><br><div class="gmail_quote">2012/9/13 Simon Hobson <span dir="ltr"><<a href="mailto:dhcp1@thehobsons.co.uk" target="_blank">dhcp1@thehobsons.co.uk</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Jan nowak top-posted:<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Sep 13 07:32:35 debian dhcpd: ICMP Echo reply while lease 172.16.20.203 valid.<br>
Sep 13 07:32:35 debian dhcpd: ICMP Echo reply while lease 172.16.20.203 valid.<br>
Sep 13 07:32:35 debian dhcpd: ICMP Echo reply while lease 172.16.20.203 valid.<br>
Sep 13 07:32:35 debian dhcpd: ICMP Echo reply while lease 172.16.20.203 valid.<br>
Sep 13 07:32:37 debian dhcpd: Reclaiming abandoned lease 172.16.20.203.<br>
Sep 13 07:32:37 debian dhcpd: Reclaiming abandoned lease 172.16.20.203.<br>
Sep 13 07:32:37 debian dhcpd: Reclaiming abandoned lease 172.16.20.203.<br>
Sep 13 07:32:37 debian dhcpd: Reclaiming abandoned lease 172.16.20.203.<br>
</blockquote>
<br></div>
Not seen that first message before, but basically it means the server has pinged the address and got a reply - when it shouldn't have. So it's marked the lease as abandoned - abandoned leases are only used as last resort if nothing else is available.<br>
<br>
But this is a different address to the one of interest ...<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Sep 13 07:32:41 debian dhcpd: data: "leased-address" configuration directive: there is no lease associated with this client.<br>
</blockquote>
<br></div>
That would be correct - the lease has been abandoned and there's nothing leased to the client.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Sep 13 07:32:58 debian dhcpd: DHCPDISCOVER from 00:14:5e:7f:35:3c via eth0: network xxx: no free leases<br>
</blockquote>
<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Sep 13 07:32:58 debian dhcpd: DHCPDISCOVER from 00:14:5e:7f:35:3c via eth0: network xxx: no free leases<br>
</blockquote>
<br></div>
This is what you expect to see when using restricted lease ranges and old leases are still active. There isn't anything for the server to assign to the client. Again, this isn't the client (MAC) in the config snippet.<br>
<br>
It's not that helpful to see this unrelated log extract. If it's a network with too much DHCP traffic to extract only the relevant entries, then you probably need to either temporarily disable DHCP service for all but one client, or setup a test environment with only the one client.<div class="im">
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
shared-network xxx{<br>
<br>
subnet 172.16.0.0 netmask 255.255.0.0 {<br>
next-server 192.168.0.1;<br>
option domain-name-servers 217.30.129.149, 217.30.137.200;<br>
option routers 172.16.0.1;<br>
option subnet-mask 255.255.0.0;<br>
option broadcast-address 172.16.255.255;<br>
}<br>
</blockquote>
<br></div>
Could I suggest better formatting would be a good idea ? Something like this would make the nesting more readily viewable :<div class="im"><br>
<br>
shared-network xxx{<br>
<br>
subnet 172.16.0.0 netmask 255.255.0.0 {<br>
next-server 192.168.0.1;<br>
option domain-name-servers 217.30.129.149, 217.30.137.200;<br>
option routers 172.16.0.1;<br>
option subnet-mask 255.255.0.0;<br>
option broadcast-address 172.16.255.255;<br>
}<br>
<br></div>
subnet ...<br>
<br>
This is especially true when we get to your host statements.<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
##############################<u></u>###########<br>
host m69 { hardware ethernet 00:0a:73:f9:e6:3a; fixed-address 172.16.10.69; filename "<<a href="http://plik.cm" target="_blank">http://plik.cm</a>><a href="http://plik.cm" target="_blank">plik.cm</a>";}<div class="im">
<br>
class "M069" { match if binary-to-ascii(16, 8, ":", option agent.remote-id) = "0:a:73:f9:e6:3a"; spawn with option agent.remote-id; lease limit 1;}<br>
pool { allow members of "M069"; range 172.16.20.69; }<br>
##############################<u></u>################<br>
}<br>
</div></blockquote>
<br>
Not only is this hard to read, it's mixing scopes as well.<div class="im"><br>
<br>
host m69 {<br>
hardware ethernet 00:0a:73:f9:e6:3a;<br>
fixed-address 172.16.10.69;<br>
filename "<a href="http://plik.cm" target="_blank">plik.cm</a>";}<br>
class "M069" {<br>
match if binary-to-ascii(16, 8, ":", option agent.remote-id) = "0:a:73:f9:e6:3a";<br>
spawn with option agent.remote-id; lease limit 1;<br>
}<br>
pool {<br>
allow members of "M069";<br>
range 172.16.20.69;<br>
}<br>
}<br>
<br></div>
So what *exactly* are you trying to achieve with this ?<br>
You've correctly put the host statement in the global scope, but then you've defined a class and pool within it.<br>
I'm not sure about the class (do these need to be in the global scope ?), but the pool really belongs within the subnet.<br>
<br>
And there should be no need to have both the class/pool AND a fixed address - either one or the other. So either :<div class="im"><br>
<br>
host m69 {<br>
hardware ethernet 00:0a:73:f9:e6:3a;<br>
fixed-address 172.16.10.69;<br>
filename "<a href="http://plik.cm" target="_blank">plik.cm</a>";}<br>
}<br>
<br></div>
or :<br>
<br>
class "M069" {<div class="im"><br>
match if option agent.remote-id) = 0:a:73:f9:e6:3a;<br></div><div class="im">
spawn with option agent.remote-id; lease limit 1;<br>
}<br></div>
and<div class="im"><br>
subnet 172.16.0.0 netmask 255.255.0.0 {<br>
next-server 192.168.0.1;<br>
option domain-name-servers 217.30.129.149, 217.30.137.200;<br>
option routers 172.16.0.1;<br>
option subnet-mask 255.255.0.0;<br>
option broadcast-address 172.16.255.255;<br></div><div class="im">
pool {<br>
allow members of "M069";<br>
range 172.16.20.69;<br>
}<br>
}<br>
<br></div>
Ahh, now I've split that up, it becomes clearer. 172.16.10.69 is for the device with MAC address 00:0a:73:f9:e6:3a and 172.16.20.69 is for the downstream device.<br>
As you've defined it, I don't think the class would be matched because the definition (and pool statement) are within a host statement that will not apply to the downstream client.<br>
By definition, the downstream client will not be the host with MAC address 0:a:73:f9:e6:3a, so the host statement will not be matches, and nothing inside it will be acted upon.<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
Simon Hobson<br>
<br>
Visit <a href="http://www.magpiesnestpublishing.co.uk/" target="_blank">http://www.<u></u>magpiesnestpublishing.co.uk/</a> for books by acclaimed<br>
author Gladys Hobson. Novels - poetry - short stories - ideal as<br>
Christmas stocking fillers. Some available as e-books.</font></span><div class="HOEnZb"><div class="h5"><br>
______________________________<u></u>_________________<br>
dhcp-users mailing list<br>
<a href="mailto:dhcp-users@lists.isc.org" target="_blank">dhcp-users@lists.isc.org</a><br>
<a href="https://lists.isc.org/mailman/listinfo/dhcp-users" target="_blank">https://lists.isc.org/mailman/<u></u>listinfo/dhcp-users</a><br>
</div></div></blockquote></div><br>