[Dnsmasq-discuss] using gPXE in chainloader mode

[Carlos Carvalho]

rance at frontiernet.net (rance at frontiernet.net) wrote on 23 December 2007 01:19:
 >I'm not sure if its a bug in dnsmasq or not, as I don't know the RFCs  
 >well enough to make a judgement.  But the gPXE people seemed convinced  
 >that dnsmasq was somehow "wrong" in this.

As Simon said, dnsmasq is just trying to cope with buggy clients. Your
machines cannot handle a terminating null in the filename but my
machines (pxe rom in Asus motherboards) don't work without it...

You can try to pass options 66 and 67 as dhcp-option directives
instead of dhcp-boot; these don't include a null byte at the end of
filenames. Besides, this way you can put the directives in a
dhcp-optsfile which is re-read with a HUP, instead of having to
restart dnsmasq. You need version test25 for this.