[syslinux] Chainloading pxe boot loaders and dhcp root-path option

Arends, R.R. r.r.arends at hro.nl
Mon May 16 04:37:05 PDT 2011

Oke i debugged some more and can confirm that after the pxechain there isn't a new dhcp request. 

What i'm trying to achief is to mainly use gpxelinux with a menu as our network boot environment and have a menu entry there to point to Windows Deployment Service, so our windows admins can use that as well. 

So our next-server is set to the main server which hosts a tftpd where we have the gpxelinux.0 nbp. 
then we try to pxechain by this:
pxechain.com 145.x.x.2::boot\x86\wdsnbp.com

To the Windows machine where the Windows Deployment Service (tftpd+more) is running. 

But then wdsnbp.com tries to load more stuff from the initial next-server (dhcp option 66?) first tftpd. 

I already tried setting option 66/next-server by gpxecmd.c32... But doesn't work. What i'm i missing. Could it be a problem with the cached dhcp packet? Should pxechain.com reset option 66 and 67?



>>> On 16-5-2011 at 11:02, in message <4DD1042E0200001000012E5F at idas01.hro.nl>,
"Arends, R.R." <r.r.arends at hro.nl> wrote:
> I'm trying to do the same by means of pxechaining to windows deployment 
> service, but it also seems to 'forget' the extra dhcp options i set from 
> withing gpxe. I will do some debugging today aswel, so far it didn't look 
> like the wds does another dhcp request. 
> Can it be that somehow setting dhcpoptions from gpxelinux with gpxecmd.c32 
> then doing a pxechain.com forgets those options again?
> /reni
>>>> On 15-5-2011 at 11:35, in message <20110515093528.GG2001 at gpm.stappers.nl>,
> Geert Stappers <stappers at stappers.nl> wrote:
>> On Sun, May 15, 2011 at 03:27:34AM -0400, Matt Fioravante wrote:
>>> On Sun, May 15, 2011 at 2:54 AM, Geert Stappers wrote:
>>> > AIUI is the scripting of iPXE wanted, http://ipxe.org/scripting 
>>> > Setting root-path is not enumrated at http://ipxe.org/cmd/set 
>>> > However root-path is seen in the screenshot at http://ipxe.org/cmd/config 
>>> I've tried playing around with gpxe, and just now (I hadn't heard of it
>>> before) ipxe. No matter how I try to change the root path, freebsd only gets
>>> a root path if it was originally set in the dhcp server options.
>>> I think its doing a dhcp request after it boots to get this information. I
>>> can't verify that completely because I don't have a box I can stick in
>>> between to snoop packets, but there doesn't seem to be any other explanation
>>> as to why its ignoring my changes to the root-path option in g/ipxe.
>> Would packet sniffing on the DHCP server(s) a possiblity?
>>> I think I'm pretty much screwed, unless I use some rediculus hack like
>>> changing the mac address to some fixed value and having the dhcp server give
>>> a special dhcp-root-path option for that machine.
>> Groeten Stappers
> _______________________________________________
> Syslinux mailing list
> Submissions to Syslinux at zytor.com 
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux 
> Please do not send private replies to mailing list traffic.

More information about the Syslinux mailing list