Report information
The Basics
Id:
41473
Status:
resolved
Estimated:
12 hours (720 minutes)
Worked:
6.67 hours (400 minutes)
Users:
tmark: 6.67 hours (400 minutes)
Left:
12 hours (720 minutes)
Priority:
Low/Low
Queue:

BugTracker
Version Fixed:
4.4.0 4.3.6 4.1-ESV-R15
Version Found:
(no value)
Versions Affected:
(no value)
Versions Planned:
4.4.0 4.3.6 4.1.-ESV-R15
Priority:
P2 Normal
Severity:
S2 Normal
CVSS Score:
(no value)
CVE ID:
(no value)
Component:
DHCP Client
Area:
bug

Dates
Created:Thu, 14 Jan 2016 01:06:30 -0500
Updated:Tue, 12 Dec 2017 07:38:34 -0500
Closed:Wed, 03 May 2017 10:28:59 -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.

Subject: DHCP - DHCP Client is not behaving as stated in MAN page for REQUIRE OPTION.
Date: Thu, 14 Jan 2016 06:06:27 +0000
To: dhcp-bugs@isc.org
From: "MRITUNJAY KUMAR DUBEY" <mritunjaykumar.dubey@nokia.com>
Bug Report from www.isc.org: Name: MRITUNJAY KUMAR DUBEY Email: mritunjaykumar.dubey@nokia.com Software Version: DHCP OS: Linux 3.XX Subject:DHCP Client is not behaving as stated in MAN page for REQUIRE OPTION. Bug Detail =========== Hi, Many thanks for the DHCP support. While using DHCP for IPV6, we have observed that DHCP client is accepting the offer even if required option present in configuration file is not present in the offer. As per MAN page, DHCP client should reject the offer and continue sending SOLICIT messages. Please help me to understand if this is expected behavior or not. If not, why. Thanks Mritunjay Kumar Dubey --- This email was received through isc.org Bug Submission Form All information within this email is considered confidential and for internal use only.
Subject: RE: [ISC-Bugs #41473] AutoReply: DHCP - DHCP Client is not behaving as stated in MAN page for REQUIRE OPTION.
Date: Wed, 27 Jan 2016 08:34:16 +0000
To: "dhcp-bugs@isc.org" <dhcp-bugs@isc.org>
From: "Dubey, Mritunjaykumar (Nokia - IN/Bangalore)" <mritunjaykumar.dubey@nokia.com>
Dear ISC Group, Is there any progress on this issue. Br, MKD [TRS-MBB] [+918884102323] -----Original Message----- From: EXT DHCP Bugs via RT [mailto:dhcp-bugs@isc.org] Sent: Thursday, January 14, 2016 11:37 AM To: Dubey, Mritunjaykumar (Nokia - IN/Bangalore) <mritunjaykumar.dubey@nokia.com> Subject: [ISC-Bugs #41473] AutoReply: DHCP - DHCP Client is not behaving as stated in MAN page for REQUIRE OPTION. Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "DHCP - DHCP Client is not behaving as stated in MAN page for REQUIRE OPTION.", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [ISC-Bugs #41473]. Please include the string: [ISC-Bugs #41473] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, dhcp-bugs@isc.org ------------------------------------------------------------------------- Bug Report from www.isc.org: Name: MRITUNJAY KUMAR DUBEY Email: mritunjaykumar.dubey@nokia.com Software Version: DHCP OS: Linux 3.XX Subject:DHCP Client is not behaving as stated in MAN page for REQUIRE OPTION. Bug Detail =========== Hi, Many thanks for the DHCP support. While using DHCP for IPV6, we have observed that DHCP client is accepting the offer even if required option present in configuration file is not present in the offer. As per MAN page, DHCP client should reject the offer and continue sending SOLICIT messages. Please help me to understand if this is expected behavior or not. If not, why. Thanks Mritunjay Kumar Dubey --- This email was received through isc.org Bug Submission Form All information within this email is considered confidential and for internal use only.
Hello Mritunjay: You'll be pleased to know that we are addressing this issue in our upcoming maintenance releases, 4.3.6 and 4.1-ESV-R15 due out July '17, and our feature release of 4.4.0 (release date is TBD). For the maintenance releases, the new behavior must be enabled at compile time by a new flag in includes/site.h, ENFORCE_DHCPV6_CLIENT_REQUIRE. Beginning with 4.4.0, the behavior will be included by default. This is mitigate any disruption users might see with the maintenance releases. We like to recognize our contributors by citing them in our release notes. If you would like to be so noted, please respond with how you would like to be identified. Most often it is by name and organization. I'd like to thank you for taking the time and interest to report this issue to us and encourage you to continue submitting feedback in the future. Regards, Thomas Markwalder ISC Software Engineering
Subject: RE: [ISC-Bugs #41473] DHCP - DHCP Client is not behaving as stated in MAN page for REQUIRE OPTION.
Date: Wed, 3 May 2017 04:06:23 +0000
To: "dhcp-review@isc.org" <dhcp-review@isc.org>
From: "Dubey, Mritunjaykumar (Nokia - IN/Bangalore)" <mritunjaykumar.dubey@nokia.com>
Hi, Many thanks for looking into the issue. >>please respond with how you would like to be identified Mritunjaykumar Dubey at Nokia Br, MKD -----Original Message----- From: Thomas Markwalder via RT [mailto:dhcp-review@isc.org] Sent: Tuesday, May 02, 2017 7:46 PM To: Dubey, Mritunjaykumar (Nokia - IN/Bangalore) <mritunjaykumar.dubey@nokia.com> Subject: [ISC-Bugs #41473] DHCP - DHCP Client is not behaving as stated in MAN page for REQUIRE OPTION. Hello Mritunjay: You'll be pleased to know that we are addressing this issue in our upcoming maintenance releases, 4.3.6 and 4.1-ESV-R15 due out July '17, and our feature release of 4.4.0 (release date is TBD). For the maintenance releases, the new behavior must be enabled at compile time by a new flag in includes/site.h, ENFORCE_DHCPV6_CLIENT_REQUIRE. Beginning with 4.4.0, the behavior will be included by default. This is mitigate any disruption users might see with the maintenance releases. We like to recognize our contributors by citing them in our release notes. If you would like to be so noted, please respond with how you would like to be identified. Most often it is by name and organization. I'd like to thank you for taking the time and interest to report this issue to us and encourage you to continue submitting feedback in the future. Regards, Thomas Markwalder ISC Software Engineering