Menu file loads fine via TFTP, but not via HTTP

Menu file loads fine via TFTP, but not via HTTP - Printable Version

+- iPXE discussion forum (https://forum.ipxe.org)
+-- Forum: iPXE user forums (/forumdisplay.php?fid=1)
+--- Forum: General (/forumdisplay.php?fid=2)
+--- Thread: Menu file loads fine via TFTP, but not via HTTP (/showthread.php?tid=7973)

Menu file loads fine via TFTP, but not via HTTP - mbirth - 2016-02-27 00:00

I've setup a dnsmasq similar to this.

This is my config:

Code:

dhcp-range=172.16.0.0,proxy

dhcp-match=ipxe,175   # iPXE sends a 175 option

pxe-service=net:!ipxe,x86PC,"iPXE Network boot",undionly.kpxe

dhcp-boot=net:ipxe,http://diskstation/ipxe/boot.ipxe

enable-tftp

tftp-root=/var/ftpd

For some reason, iPXE itself loads fine, but then fails with "Nothing to boot.". Entering the iPXE shell and typing "chain http://.../boot.ipxe" loads the menu just fine. It just doesn't work automatically. (From the dnsmasq log I can see that the URL is sent to iPXE.)

However, changing the dhcp-boot line to:

Code:

dhcp-boot=net:ipxe,menu.ipxe,172.16.254.10,172.16.254.10

So that the file is loaded via TFTP, works and the menu shows up directly on boot. But this is from a different server and I'd like the menu file to be on the HTTP server with the rest of the files.

dnsmasq is version 2.75.

Any ideas?

I probably could compile iPXE with the chain-command, but I'd love for it to work out-of-the-box with the http-URL delivered via DHCP.

RE: Menu file loads fine via TFTP, but not via HTTP - fdge - 2016-03-14 06:23

Try using the IP address of the server.