Report information
The Basics
Id:
48691
Status:
open
Priority:
Low/Low
Queue:

People
Owner:
Nobody in particular
Cc:

BugTracker
Version Fixed:
(no value)
Version Found:
4.4.1
Versions Affected:
(no value)
Versions Planned:
4.4.2
Priority:
(no value)
Severity:
(no value)
CVSS Score:
(no value)
CVE ID:
(no value)
Component:
(no value)
Area:
feature

Dates
Created:Thu, 20 Dec 2018 09:39:54 -0500
Updated:Thu, 27 Dec 2018 04:30:01 -0500
Closed:Not set



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: Server parser should emit either or warning, if not an error when classes are defined within a scope
Date: Thu, 20 Dec 2018 14:39:54 +0000
From: tmark@isc.org
To: dhcp-public@isc.org
Users have reported issues with getting the wrong option values when they have defined classes within subnet scopes. See support issue 13886 and this thread: https://lists.isc.org/pipermail/dhcp-users/2018-December/021500.html I replicated the issue reported in the thread with the attached config file. The server should emit at least a warning, if not an error when classes are defined within a scope.
Subject: 13886-subnetclasses.conf

Message body not shown because it is not plain text.

Suggestion (from one administrator who was accidentally 'bitten' by this): "Glad to see that you guys were able to replicate this in lab. Yes, That will be very helpful and safe bet if the config checker -t flag can catch this and throw non zero return code as we rely on -t flag before pushing configs to our dhcp servers. "