Skip Menu |
Report information
The Basics
Id: 45780
Status: resolved
Priority: 30/30
Queue: dhcp-public

People
Bug Information
Version Fixed: 4.4.0
Version Found: (no value)
Versions Affected: (no value)
Versions Planned: 4.4.0
Priority: (no value)
Severity: (no value)
CVSS Score: (no value)
CVE ID: (no value)
Component: (no value)
Area: (no value)

Dates
Created:Tue, 15 Aug 2017 08:46:04 -0400
Updated:Tue, 10 Oct 2017 15:29:04 -0400
Closed:Tue, 10 Oct 2017 15:29:04 -0400



This bug tracker is no longer active.

Please go to our Gitlab to submit issues (both feature requests and bug reports) for active projects maintained by Internet Systems Consortium (ISC).

Due to security and confidentiality requirements, full access is limited to the primary maintainers.

To: dhcp-bugs@isc.org
Date: Tue, 15 Aug 2017 08:45:50 -0400
Subject: Fwd: DHCPv6 PD oddity with client changing prefix size.
From: "Tim DeNike" <tim@denike.us>
Download (untitled) / with headers
text/plain 1.8KiB
Running 4.3.5 in an ISP environment.  Delivering prefixes via DHCPv6-PD.

By default we give users a /64 but will allow them to request a /60 or /56.

Everything works fine with the /64s and /60s EXCEPT if a user changes prefix lengths.

IE:  User plugs in and enables DHCPv6, they get a /64.  They decide they want a /60 so change their prefix hint to /60 release/renew, they get the same /64 back again.

The only way to get them to acquire a /60 is to either manually remove the /64 lease from the leases file or wait out until the default-lease-time has expired.

Apparently when the client releases the prefix, it is still held for them so they can get it back.  No problem with that functionality.  Makes sense.  But if the client releases and requests a prefix that doesn't have a length that matches the previous lease then they should be allocated a prefix from the pool that does match based on the rules of "prefix-length-mode".

We do have "prefix-length-mode exact;" set.

Seems like a simple oversight/unintended side effect.

Hello Tim:

I retested your scenario with 4.3.6 which we released on 7/31.  While it does contain a correction for one issue with prefix delegation it does not address your scenario which I tested as:

1. Configured a server to have two PD pools in the same subnet, one /64 and the other /60,  prefix-length-mode = exact
2. Solicits from the same client with prefix length hints of /64 and /60 , are offered leases of /64 and /60, respectively
(confirming hints are being honored as expected)
3. Client solicits a /64, and accepts the offered /64 PD lease
4. Client releases /64 PD lease
5. Client solicits a /60
6. Server offers prior /64 PD lease

(Note prefix value for all solicits was "::")

If you would be so kind as to open a bug for this, we should be able to work it into 4.4.0 which is slated for January '18.
Hello Tim: You'll be pleased to hear that we've addressed your issue in our next release of ISC DHCP, 4.4.0, which is due out first quarter 2018. As you reported, the server would return a client's previously released prefix lease even when the client subsequently provided a prefix length hint that did not match that lease. Now the server will only return the previous lease if it exactly matches the hint or the prefix-length-mode is set to "ignore". Otherwise, it will attempt to allocate a new prefix based on the hint and the prefix-length-mode. We like to recognize contributors by citing them in our release notes. If you wish to be thanked in this manner please respond with how you want to be identified. Most often it is by name and/or organization. Thanks for taking the time to report this issue. Regards, Thomas Markwalder ISC Software Engineering
Date: Wed, 6 Sep 2017 11:33:22 -0400
To: dhcp-public@isc.org
Subject: Re: [ISC-Bugs #45780] Fwd: DHCPv6 PD oddity with client changing prefix size.
From: "Tim DeNike" <tim@denike.us>
Sure thing. Tim DeNike - Lightspeed Communications Thanks! Sent from my iPhone > On Sep 6, 2017, at 10:54 AM, Thomas Markwalder via RT <dhcp-public@isc.org> wrote: > > Hello Tim: > > You'll be pleased to hear that we've addressed your issue in our next release of ISC DHCP, 4.4.0, which is due out first quarter 2018. > > As you reported, the server would return a client's previously released prefix lease even when the client subsequently provided a prefix length hint that did not match that lease. Now the server will only return the previous lease if it exactly matches the hint or the prefix-length-mode is set to "ignore". Otherwise, it will attempt to allocate a new prefix based on the hint and the prefix-length-mode. > > We like to recognize contributors by citing them in our release notes. If you wish to be thanked in this manner please respond with how you want to be identified. Most often it is by name and/or organization. > > Thanks for taking the time to report this issue. > > Regards, > > Thomas Markwalder > ISC Software Engineering > >