[prev in list] [next in list] [prev in thread] [next in thread]
List: dhcp-hackers
Subject: Re: Possible regression in 3.1.0?
From: "David W. Hankins" <David_Hankins () isc ! org>
Date: 2007-08-10 16:02:18
Message-ID: 20070810160218.GB31592 () isc ! org
[Download RAW message or body]
On Thu, Aug 09, 2007 at 05:08:25PM -0700, Matt Cowger wrote:
> option space pxelinux;
> option pxelinux.magic code 208 = string;
> option pxelinux.configfile code 209 = text;
> option pxelinux.pathprefix code 210 = text;
> option pxelinux.reboottime code 211 = unsigned integer 32;
>
> site-option-space "pxelinux";
What's happening here is options less than 224 aren't being pulled
out of the named site-local option space, they're being tried in
the dhcp option space.
From RELNOTES:
Changes since 3.0 (New Features)
- RFC3942 compliance, site-local option spaces start at 224 now, not 128.
We're sort of inbetween RFC's. RFC3942 says that 224+ qualify as
site-local, and draft-ietf-dhc-pxelinux hasn't become an RFC yet.
You'll want to redefine your 208-211 options as regular DHCP options,
rather than site local ones, in 3.1.0. Those definitions will
supersede anything we configure in a public version:
#if 0
/* PXELINUX options: not defined by RFC yet */
{ "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
(I have a suspicion "BBBB" will become an "X" to match usual use)
--
Ash bugud-gul durbatuluk agh burzum-ishi krimpatul.
Why settle for the lesser evil? https://secure.isc.org/store/t-shirt/
--
David W. Hankins "If you don't do it right the first time,
Software Engineer you'll just have to do it again."
Internet Systems Consortium, Inc. -- Jack T. Hankins
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic