References: <320af239b12d3dc44e23399129493513@www.isc.org> Content-Transfer-Encoding: binary Content-Disposition: inline X-Mailer: MIME-tools 5.508 (Entity 5.508) MIME-Version: 1.0 X-RT-Interface: Web In-Reply-To: <320af239b12d3dc44e23399129493513@www.isc.org> X-RT-Original-Encoding: utf-8 Message-ID: Content-Type: text/plain; charset="utf-8" RT-Send-CC: Content-Length: 832 Hello Radek: This issue was corrected in ISC DHCP 4.4.1 under rt46719. ISC DHCP 4.3.* is EOL at this point. I have attached a patch that should work 4.3.6 but keep in mind that it does not represent an official, tested patch. Our official response for your issue is to suggest you upgrade 4.4.1. Upgrading from 4.3.5 to 4.4.1 should be painless, they are architecturally compatible. Speaking of EOL, 4.4.1 is the last feature release of ISC DHCP as we are putting our focus on new DHCP product: https://www.isc.org/kea While we do plan on doing some maintenance releases for ISC DHCP, the next one (4.4.2) has not yet been scheduled. It might be a good time for you to look into migrating to Kea. Thank you for your inquiry, I help this addresses the issue for you. Sincerely, Thomas Markwalder ISC Software Engineering