<p dir="ltr">Thank you so much Glenn.</p>
<p dir="ltr">I will give you a feedback in a while. </p>
<p dir="ltr">With regards,<br>
Eugène NG. </p>
<div class="gmail_quote">Le 19 juil. 2014 08:07, "Glenn Satchell" <<a href="mailto:glenn.satchell@uniq.com.au">glenn.satchell@uniq.com.au</a>> a écrit :<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Eugene<br>
<br>
You are correct. The dynamic range is not used for hosts assigned an<br>
address via a fixed-address statement. But different people are offering<br>
ideas for you.<br>
<br>
The "range dynamic-bootp" assigns bootp leases to clients. The difference<br>
between bootp and dhcp is defined in several RFCs, but for our purpose we<br>
can think of dhcp as an enhanced bootp. One of the noticeable differences<br>
is that a bootp lease does not expire, so it is easy to run out of IPs if<br>
you have too many clients, even over a long timne. Eg the PC you got rid<br>
of two years ago is still holding one of your IPs. The isc-dhcp server<br>
handles both types of leases in the same way, with a flag to distinguish<br>
bootp from dhcp. It uses the same leases file. "range dynamic-bootp" was<br>
an example in the example dhcpd.conf distributed by RedHat, so that's<br>
probably where it came from.<br>
<br>
I see that you are running dhcpd version 3.0.5. this is a very old<br>
version, released in 2006. This was the default version with RedHat 5. If<br>
you upgrade to RedHat 6.x you get version 4.1_something. There have been<br>
many versions and fixes in the last 8 years. The next step before looking<br>
at problems with your setup would be to upgrade to a current version and<br>
see if you still see the problem. This is probably going to be the easiest<br>
path. Your current dhcpd.conf looks like it would work without change.<br>
<br>
This is from the Release Notes (RELNOTES) in a newer version:<br>
<br>
Changes since 3.0.5<br>
<br>
- Assorted fixes for broken network devices: Packet length is now<br>
determined from the IP header length field to finally calculate the<br>
UDP payload length, because some NIC drivers return more data than<br>
they actually received.<br>
<br>
regards,<br>
-glenn<br>
<br>
On Sat, July 19, 2014 12:07 am, Eugène Ngontang wrote:<br>
> But Maarten, the dynamic range is for host whose ip address is not<br>
> reserved. So if there nerver is a host requesting for a dynamic address,<br>
> will there be a dynamic lease too? where do bootp store its leases? Is it<br>
> in the same dhcpd.leases file?<br>
><br>
> Thanks.<br>
><br>
><br>
> 2014-07-18 15:48 GMT+02:00 Eugène Ngontang <<a href="mailto:sympavali@gmail.com">sympavali@gmail.com</a>>:<br>
><br>
>> Ok Maarten, I will look at this.<br>
>><br>
>> In fact I'm not the one who set the "range dynamic-bootp" clausure, I<br>
>> guess the clients are using dhcp and bootp is not really required.<br>
>><br>
>> But please, I know bootp is an old protocol, but I din't know the impact<br>
>> of using this clausure. I would like if possible to have a link where<br>
>> the<br>
>> difference between the two clausures is explained, and the impact of<br>
>> using<br>
>> "range dynamic-bootp" in lease offers.<br>
>><br>
>> I will try investigating this way. Thanks.<br>
>><br>
>> Regards,<br>
>> Eugène NG<br>
>><br>
>><br>
>> 2014-07-18 14:36 GMT+02:00 Maarten Carels <<a href="mailto:lists@carels.info">lists@carels.info</a>>:<br>
>><br>
>>> On 18 Jul 2014, at 14:22 , Eugène Ngontang <<a href="mailto:sympavali@gmail.com">sympavali@gmail.com</a>><br>
>>> wrote:<br>
>>><br>
>>> > @Maarten, that is what I didn't figure out.<br>
>>> ><br>
>>> > Nevertheless, I have a dynamic range, and fixed addresses.<br>
>>> ><br>
>>> > Please explain in more detail what you mean in your post about bootp.<br>
>>> Thank you my dear.<br>
>>><br>
>>> If all your clients are using dhcp, change the range statement to<br>
>>> range 1.1.1.50 1.1.1.100;<br>
>>><br>
>>> bootp is an old protocol that lacks the automatic lease expiration.<br>
>>><br>
>>> And look at the place where the server is logging, usually somewhere in<br>
>>> /var/log. If it thinks it can't give a lease, it will log why.<br>
>>><br>
>>> --maarten<br>
>>><br>
>>> _______________________________________________<br>
>>> dhcp-users mailing list<br>
>>> <a href="mailto:dhcp-users@lists.isc.org">dhcp-users@lists.isc.org</a><br>
>>> <a href="https://lists.isc.org/mailman/listinfo/dhcp-users" target="_blank">https://lists.isc.org/mailman/listinfo/dhcp-users</a><br>
>>><br>
>><br>
>><br>
>><br>
>> --<br>
>> <a href="mailto:ngonta_e@epitech.net">ngonta_e@epitech.net</a><br>
>> <a href="mailto:sympavali@gmail.com">sympavali@gmail.com</a><br>
>> ------------------------------------------------------------<br>
>> *Aux hommes il faut un chef, et au*<br>
>><br>
>> * chef il faut des hommes! L'habit ne fait pas le moine, mais lorsqu'on<br>
>> te<br>
>> voit on te juge!*<br>
>><br>
><br>
><br>
><br>
> --<br>
> <a href="mailto:ngonta_e@epitech.net">ngonta_e@epitech.net</a><br>
> <a href="mailto:sympavali@gmail.com">sympavali@gmail.com</a><br>
> ------------------------------------------------------------<br>
> *Aux hommes il faut un chef, et au*<br>
><br>
> * chef il faut des hommes!L'habit ne fait pas le moine, mais lorsqu'on te<br>
> voit on te juge!*<br>
> _______________________________________________<br>
> dhcp-users mailing list<br>
> <a href="mailto:dhcp-users@lists.isc.org">dhcp-users@lists.isc.org</a><br>
> <a href="https://lists.isc.org/mailman/listinfo/dhcp-users" target="_blank">https://lists.isc.org/mailman/listinfo/dhcp-users</a><br>
<br>
<br>
_______________________________________________<br>
dhcp-users mailing list<br>
<a href="mailto:dhcp-users@lists.isc.org">dhcp-users@lists.isc.org</a><br>
<a href="https://lists.isc.org/mailman/listinfo/dhcp-users" target="_blank">https://lists.isc.org/mailman/listinfo/dhcp-users</a><br>
</blockquote></div>