<div dir="ltr"> Hi,<div>Are you guys aware of memory leak issues with dhcptl_connect function in DHCP version</div><div><span style="font-size:12.8px">4.1-ESV-R7 or higher ?</span></div><div><span style="font-size:12.8px">Is there a bugdb that I can search for know issues?</span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">Thanks</span></div><div><span style="font-size:12.8px">Praveen</span></div><div><span style="font-size:12.8px"><br></span><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 3, 2015 at 12:23 PM, Thomas Markwalder <span dir="ltr"><<a href="mailto:tmark@isc.org" target="_blank">tmark@isc.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">ISC DHCP 4.1-ESV-R12 is now available for download.<br>
<br>
This is the release of ISC DHCP 4.1-ESV-R12, a maintenance<br>
release which contains a number of bug fixes.<br>
<br>
Field testing is an important part of our quality process.<br>
Please report bugs to <a href="mailto:dhcp-bugs@isc.org">dhcp-bugs@isc.org</a>.<br>
<br>
A list of the changes in this release has been appended to the end<br>
of this message. For a complete list of changes from any previous<br>
release, please consult the RELNOTES file within the source distribution.<br>
They can also be found at:<br>
<br>
<br>
<a href="https://kb.isc.org/article/AA-01293/82/DHCP-4.1-ESV-R12-Release-Notes.html" rel="noreferrer" target="_blank">https://kb.isc.org/article/AA-01293/82/DHCP-4.1-ESV-R12-Release-Notes.html</a><br>
<br>
Knowledge base articles about various features can be found starting from:<br>
<br>
<a href="https://kb.isc.org/category/201/0/10/Software-Products/DHCP/Features/" rel="noreferrer" target="_blank">https://kb.isc.org/category/201/0/10/Software-Products/DHCP/Features/</a><br>
<br>
Webinars can be found here:<br>
<br>
<a href="http://www.youtube.com/user/ISCdotorg" rel="noreferrer" target="_blank">http://www.youtube.com/user/ISCdotorg</a><br>
<br>
This release, and its OpenPGP-signatures are available now from:<br>
<br>
<a href="https://www.isc.org/downloads/DHCP/" rel="noreferrer" target="_blank">https://www.isc.org/downloads/DHCP/</a><br>
<br>
<a href="ftp://ftp.isc.org/isc/dhcp/4.1-ESV-R12/dhcp-4.1-ESV-R12.tar.gz" rel="noreferrer" target="_blank">ftp://ftp.isc.org/isc/dhcp/4.1-ESV-R12/dhcp-4.1-ESV-R12.tar.gz</a><br>
<br>
<a href="ftp://ftp.isc.org/isc/dhcp/4.1-ESV-R12/dhcp-4.1-ESV-R12.tar.gz.sha512.asc" rel="noreferrer" target="_blank">ftp://ftp.isc.org/isc/dhcp/4.1-ESV-R12/dhcp-4.1-ESV-R12.tar.gz.sha512.asc</a><br>
<br>
<a href="ftp://ftp.isc.org/isc/dhcp/4.1-ESV-R12/dhcp-4.1-ESV-R12.tar.gz.sha256.asc" rel="noreferrer" target="_blank">ftp://ftp.isc.org/isc/dhcp/4.1-ESV-R12/dhcp-4.1-ESV-R12.tar.gz.sha256.asc</a><br>
<a href="ftp://ftp.isc.org/isc/dhcp/4.1-ESV-R12/dhcp-4.1-ESV-R12.tar.gz.sha1.asc" rel="noreferrer" target="_blank">ftp://ftp.isc.org/isc/dhcp/4.1-ESV-R12/dhcp-4.1-ESV-R12.tar.gz.sha1.asc</a><br>
<br>
ISC's Release Signing Key can be obtained at:<br>
<br>
<a href="http://www.isc.org/about/openpgp/" rel="noreferrer" target="_blank">http://www.isc.org/about/openpgp/</a><br>
<br>
The following are changes that may be more interesting and require<br>
a bit more explanation.<br>
<br>
We have modified the PARANOIA patch to adjust the file permissions<br>
(owner and group) used for the lease file. In our testing this had<br>
no negative effects. However, given the range of OSes and security<br>
features, we are not able to test all possible combinations.<br>
<br>
The following is the list of all changes for this release.<br>
<br>
Changes since 4.1-ESV-R12b1<br>
<br>
- None<br>
<br>
Changes since 4.1-ESV-R11<br>
<br>
- The server now does a better check to see if it can allocate the memory<br>
for large blocks of v4 leases and should provide a slightly better error<br>
message. Note well: the server pre-allocates v4 addresses, if you use<br>
a large range, such as a /8, the server will attempt to use a large<br>
amount of memory and may not start if there either isn't enough memory<br>
or the size exceeds what the code supports.<br>
[ISC-Bugs #38637]<br>
<br>
- The server will now reject unicast Request, Renew, Decline, and Release<br>
messages from a client unless the server would have sent that client the<br>
dhcp6.unicast option. This behavior is in compliance with paragraph 1 in<br>
each of the sections 18.2,1, 18.2.3, 18.2.6, and 18.2.7 of RFC 3315. Prior<br>
to this, the server would simply accept the messages. Now, in order for<br>
the server to accept such a message, the server configuration must include<br>
the dhcp6.unicast option either globally or within the shared network to<br>
which the requested lease belongs. In other words, the server will map<br>
the first IA_XX address found within the client message to a<br>
shared-network<br>
and look for the presence of the unicast option there and then globally.<br>
[ISC-Bugs #21235]<br>
<br>
- Write out the DUID server id on startup in all cases, previously if it<br>
was read in from server-duid option in the config or lease files for<br>
DHCPv4 it would not be written to the new lease file.<br>
[ISC-Bugs #37791]<br>
<br>
- When parsing dates for leases convert dates past 2038 to "never".<br>
This avoids problems with integer overflows in the date and time<br>
handling code for people that decide to use very large lease times<br>
or add a lease entry with a date far in the future.<br>
[ISC-Bugs #33056]<br>
<br>
- Leave the siaddr field clear when sending a NACK as per RFC 2131<br>
table 3.<br>
[ISC-Bugs #38769]<br>
<br>
- Some compilers don't like the use of abs in minires/ns_verify.c,<br>
change it to labs to make them happy.<br>
[ISC-Bugs #39301]<br>
<br>
- In the client don't send expired addresses to the script as part of<br>
the binding process. Thanks to Sven Trenkel at Google for reporting<br>
the issue and suggesting the patch.<br>
[ISC-Bugs #38631]<br>
<br>
- While parsing IPv6 addresses treat "add" as part of the address instead<br>
of as a token.<br>
[ISC-Bugs #39529]<br>
<br>
- Delayed-ack now works properly with Failover. Prior to this, bind updates<br>
post startup were being queued but never delivered. Among other<br>
things, this<br>
was causing leases to not transition from expired or released to free.<br>
[ISC-Bugs #31474]<br>
<br>
- Clean up parsing of v6 lease files a bit to avoid infinite loops if the<br>
lease file is corrupt in certain ways.<br>
[ISC-Bugs #39760]<br>
<br>
- Corrected an issue in v6 lease file parsing. Prior to this, when<br>
encountering<br>
a lease with an address for which no configured pool exists, the<br>
server was<br>
declaring the lease file corrupt and incorrectly skipping over the<br>
subsequent<br>
entry in the file. The server will now emit a log message indicating that<br>
no pool was found for the address (or prefix) and correctly resume parsing<br>
with the next entry in the lease file. Our thanks to Michal Žejdl for<br>
reporting the issue.<br>
[ISC-Bugs #39314]<br>
<br>
- Enhance the PARANOIA patch to include fchown() the lease file to<br>
allow it to be manipulated after the server does a chown().<br>
Thanks to Jiri Popelka at Red Hat for the patch.<br>
[ISC-Bugs #36978]<br>
<br>
- Fixed a server crash that could occur when the server attempts to remove<br>
the billing class from the last lease billed to a dynamic class after said<br>
class has been deleted.<br>
[ISC-Bugs #39978]<br>
<br>
- Handle an out of memory condition in the client a bit better.<br>
Thanks to Frédéric Perrin from Brocade for finding the issue<br>
and suggesting a patch.<br>
[ISC-Bugs #39279]<br>
<br>
<br>
_______________________________________________<br>
dhcp-workers mailing list<br>
<a href="mailto:dhcp-workers@lists.isc.org">dhcp-workers@lists.isc.org</a><br>
<a href="https://lists.isc.org/mailman/listinfo/dhcp-workers" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/listinfo/dhcp-workers</a></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Regards,<br>Praveen</div>
</div></div></div>