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