Report information
The Basics
Id:
47062
Status:
resolved
Worked:
3 hours (180 minutes)
Users:
tmark: 3 hours (180 minutes)
Priority:
Medium/Medium
Queue:

BugTracker
Version Fixed:
4.4.0 v4_3 4.1-ESV-R16
Version Found:
(no value)
Versions Affected:
(no value)
Versions Planned:
4.4.2 4.1-ESV-R16
Priority:
P2 Normal
Severity:
S2 Normal
CVSS Score:
(no value)
CVE ID:
(no value)
Component:
(no value)
Area:
feature

Dates
Created:Thu, 25 Jan 2018 17:23:27 -0500
Updated:Thu, 20 Dec 2018 16:02:43 -0500
Closed:Mon, 17 Dec 2018 16:03:58 -0500



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.

From: "Peter Lewis" <plewis@grailbio.com>
To: dhcp-bugs@isc.org
Date: Thu, 25 Jan 2018 14:23:16 -0800
Subject: option configfile validation error
validation comand:
dhcpd -t -cf /etc/dhcp/dhcpd.conf

error:
/etc/dhcp/dhcpd.conf line 3: unknown option dhcp.configfile
    option configfile "pxelinux.cfg/config1"
               ^

Config file:
host test1 {
    option configfile "pxelinux.cfg/config1";
    hardware ethernet 00:00:00:00:00:01;
    fixed-address 10.10.10.10;
    option host-name "test1";
}
host test2 {
    option configfile "pxelinux.cfg/config2";
    hardware ethernet 00:00:00:00:00:02;
    fixed-address 10.10.10.11;
    option host-name "test2";
}

The "option configfile" has been working well to give out DHCP option 209 to our pxe clients for auto deployments, however, when it is in our config file the validation fails.  Rendering our auto-configuration scripts useless.


Hello Peter: Could you please identify what version of "dhcpd" this was working under and what you are using now? Examining our code it appears to me the ISC DHCP has never supported option 209, though its specification exists in our. It is currently compiled out as you can see in the excerpt from common/tables.c below: : #if 0 /* PXELINUX options: defined by RFC 5071 */ { "pxelinux-magic", "BBBB", &dhcp_universe, 208, 1 }, { "loader-configfile", "t", &dhcp_universe, 209, 1 }, { "loader-pathprefix", "t", &dhcp_universe, 210, 1 }, { "loader-reboottime", "L", &dhcp_universe, 211, 1 }, #endif : As near as I can determine we have never shipped a version with this compiled in or with the option name as "configfile". Most likely you were running a patched or packaged version, not produced by ISC. If you're willing to build from our source and require only that the option be parsed and sent back by the server, you could change the "#if 0" to "#if 1" in the file above and rebuild. If you decide to go this route I would encourage you to use the option labels as they are above: "loader_configfile" rather than "configfile". In the event we begin shipping with these compiled in, you'll be compatible with our source. In the meantime, I will look into whether or not we should compile these options in by default. RFC 5071 was finalized a long time ago (2007) and I need to dig into why these options were not included by default at that time. It may be simple oversight but DHCP protocol evolution sometimes holds obscurities and it seldom pays to make assumptions. Regards, Thomas Markwalder ISC Software Engineering