Syslinux - Oct 2008 - PXE over HTTP instead of TFTP - flip flopping OS boots

Is there a way to boot PXELINUX 100% over HTTP instead of TFTP?  I can
pull over pxelinux.0 via HTTP (DHCP config) but all the config files
are pulled over via TFTP.

DHCPD config file example:

filename "pxelinux.0" ; # boots via TFTP
filename "http://10.1.1.10/pxelinux.0"  # boots via HTTP

My goal is to alternate booting between Linux and Memtest for some
hardware stress testing.  On the webserver I want to generate the
config file and send it back on the fly via HTTP to decide which OS to
boot.  I can't do this via TFTP.

Any thoughts?

Thanks,

John

John Studarus wrote:
> Is there a way to boot PXELINUX 100% over HTTP instead of TFTP?  I can
> pull over pxelinux.0 via HTTP (DHCP config) but all the config files
> are pulled over via TFTP.
> 
> DHCPD config file example:
> 
> filename "pxelinux.0" ; # boots via TFTP
> filename "http://10.1.1.10/pxelinux.0"  # boots via HTTP
> 
> My goal is to alternate booting between Linux and Memtest for some
> hardware stress testing.  On the webserver I want to generate the
> config file and send it back on the fly via HTTP to decide which OS to
> boot.  I can't do this via TFTP.
> 
> Any thoughts?
> 
Yes, use DHCP option 209 to set a different filename prefix (and make it 
a URL prefix), or use DHCP option 210 to set a different configuration 
file name.  The former is recommended.

To boot 100% over HTTP -- that is, no TFTP server at all -- you have to 
flash gPXE into your boot ROM.

	-hpa