From dmrz@illinois.edu Tue Dec 22 21:37:17 2015 MIME-Version: 1.0 In-Reply-To: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.0 X-RT-Interface: API References: <56784745.8040408@illinois.edu> Message-ID: <5679C289.2090607@illinois.edu> content-type: text/plain; charset="utf-8"; format="flowed" X-RT-Original-Encoding: utf-8 Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) by bugs.isc.org (Postfix) with ESMTP id C9C1971B586 for ; Tue, 22 Dec 2015 21:37:17 +0000 (UTC) Received: from golbez.ci.uiuc.edu (golbez.ci.uiuc.edu [IPv6:2620:0:e00:400e:92b1:1cff:fe7f:20dc]) by mx.ams1.isc.org (Postfix) with ESMTP id C86A51FCABE for ; Tue, 22 Dec 2015 21:37:15 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) by golbez.ci.uiuc.edu (Postfix) with ESMTP id 2B39B22092B for ; Tue, 22 Dec 2015 15:37:14 -0600 (CST) Delivered-To: dhcp-bugs@bugs.isc.org User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 Subject: Re: [ISC-Bugs #41358] dhcpd inappropriately frees lease Return-Path: X-Original-To: dhcp-bugs@bugs.isc.org Date: Tue, 22 Dec 2015 15:37:13 -0600 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mx.ams1.isc.org To: dhcp-bugs@isc.org Content-Transfer-Encoding: 7bit From: "David Zych" RT-Message-ID: Content-Length: 772 On 12/21/2015 04:39 PM, Michael McNally via RT wrote: > On Mon Dec 21 18:39:07 2015, dmrz@illinois.edu wrote: >> When a client using option 61 client identifier moves to a new network >> and obtains a lease, its lease for an IP on the old network is >> inappropriately freed by dhcpd. > > What we told them was that we believe the behavior > of the server is incorrect in this case and we'll > take a look at fixing it, but the schedule for the > maintenance releases already in progress is already > set (and nearing its end) so unless this is causing > a crisis for operators it will probably take a little > while before we can schedule work on it. Not a crisis; I will happily look forward to seeing it fixed in a future release. Thanks, and happy holidays! David