[syslinux] ISOLinux, menu.c32 and PXE handoff?

Sergey Vlasov vsu at altlinux.ru
Wed Jul 23 07:07:32 PDT 2008


On Tue, Jul 22, 2008 at 07:08:12PM +0400, Sergey Vlasov wrote:
> -----------------------------------------------------------------------
> #!gpxe
> set filename tftp://10.0.0.1/boot/pxelinux.0
> kernel tftp://10.0.0.1/boot/pxelinux.0
> boot
> -----------------------------------------------------------------------
[...]
> This would work if the problematic DHCP server does not send the
> boot filename at all.  If the server sends the boot filename, that
> filename would still be used instead of the name specified in the
> script - in this case you can try
> 
> set net0.dhcp/filename tftp://10.0.0.1/boot/pxelinux.0
> 
> The above command will override the filename in the DHCP response,
> but it would work only for booting from the first network card -
> boot attempts from subsequent interfaces will fail.

There is yet another way to handle a DHCP server sending the boot
filename, which does not break with multiple network cards - you can
set a PXELINUX-specific DHCP option:

-----------------------------------------------------------------------
#!gpxe
set 210:string tftp://10.0.0.1/boot/
kernel tftp://10.0.0.1/boot/pxelinux.0
boot
-----------------------------------------------------------------------

Option 210 is "Path Prefix Option", described in RFC 5071
(doc/rfc5071.txt in syslinux sources).  This option overrides the
guessing of prefix from boot filename in pxelinux.

This gpxe script will also work only if the DHCP server does not
send the option 210 itself (if it does, the only solution is to set
net0.dhcp/210:string instead, which hardcodes the net0 interface).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://www.zytor.com/pipermail/syslinux/attachments/20080723/a423c0c8/attachment.sig>


More information about the Syslinux mailing list