search for: rfc3942

I have 2 groups of machines, and within each group the pxelinux menu configuration is standard. It would be great to have 2 configuration files rather than one for each machine. I found the pxelinux magic option configfile (209) in http://syslinux.zytor.com/wiki/index.php/PXELINUX and it suggests for ISC dhcpd: site-option-space "pxelinux"; option pxelinux.magic

...ote: > Just an FYI, we're getting the odd report from pxelinux users on > 3.1.0 - using a 'site option space' for pxelinux options in 3.0.x and > upgrading to 3.1.x is breaking. The server only grabs options >> = 224 out of the site local space, rather than the old 128...rfc3942 > compliance. The workaround is to just define the pxelinux options > in the dhcp space ("option pxelinux-thing code foo = bar;" rather > than "option pxelinux.thingy code foo = bar;"). > > We're in a tough spot inbetween RFC's. I think the good news is...

On 2014/3/7 ?? 05:23, Gene Cumm wrote: > On Thu, Mar 6, 2014 at 10:55 AM, Bryan Romine <bromine1027 at gmail.com> wrote: >> Sorry for the confusion, I am actually using 6.02. It turns out that I was >> trying to use the 32-bit efi binary to load 64-bit kernels. I switched to >> using "syslinux64.efi" but it hangs during boot, just before loading the >>

...Mar 7 19:16:03 dhcpd: Client 0:c:29:6e:ac:93 requests 1:2:3:4:5:6:c:d:f:11:12:16:17:1c:28:29:2a:2b:32:33:36:3a:3b:3c:42:43:61:80:81:82:83:84:85:86:87 - PXEClient:Arch:00007:UNDI:003000 - no dhcp-client-id Mar 7 19:16:03 dhcpd: WARNING: site-local option codes less than 224 have been deprecated by RFC3942. You have options listed in site local space pxelinux that number as low as 208. Please investigate if these should be declared as regular options rather than site-local options, or migrated up past 224. Mar 7 19:16:03 dhcpd: DHCPDISCOVER from 00:0c:29:6e:ac:93 via eth1 Mar 7 19:16:04 dhcpd: DH...