[Dnsmasq-discuss] problem getting gpxe to work within dnsmasq

[Simon Kelley]

Rance Hall wrote:
> Heres my setup dnsmasq is my dhcp/dns/tftpserver all together.
> 
> I have a working pxe menu system I like, and it affords me the chance
> to boot dban, memtest, etc just from pxe.
> 
> I've really struggled getting gPXE to work the way I want it to since
> Simon was so nice to alter dnsmasq to that gpxe would work
> 
> the gpxe authors and Simon have apparently teamed up as there is some
> really good docs out there.
> 
> Here is what Im trying to accomplish:
> 
> 
> leave the currently setup pxe menus alone, except add an option from
> one of the menus to boot gpxe from pxe.
> 
> pxe supplies the gpxe kernel just like it would for any other product.
> 
> gpxe starts, gets a different bootfile name and starts the gPXe menu
> page where you can define the various iSCSI drives that are
> netbootable
> 
> problem:
> 
> here is the stock dnsmasq config file section
> 
> # Boot for Etherboot gPXE. The idea is to send two different
> # filenames, the first loads gPXE, and the second tells gPXE what to
> # load. The dhcp-match sets the gpxe tag for requests from gPXE.
> #dhcp-match=gpxe,175 # gPXE sends a 175 option.
> #dhcp-boot=net:#gpxe,undionly.kpxe
> 
> 
> I have the following configuration
> 
> dhcp-boot=pxelinux.0
> dhcp-match=gpxe,175 # gPXE sends a 175 option.
> dhcp-boot=net:#menu.gpxe
                 ^
This doesn't look right, should probably be

dhcp-boot=net:#gpxe,menu.gpxe


> 
> where menu.gpxe exists right next to the pxelinux.0 file in the fttp
> directory and the file is a gpxe script that tells it what to do next.
> 
> on my clients I get the following behavior...
> 
> 
> pxe boots as expected.
> 
> select gpxe from pxe menu
> 
> gpxe loads as expected
> 
> gpxe does NOT load the script and create the menu.
> 
> gpxe reloads itself ONCE
> 
> no filename or root path specified
> 
> BOOT FAILURE.
> 
>

Cheers,

Simon.