URL Redirection

[abdullah-erturk]

In previous versions, compiling the ipxe project with these codes worked flawlessly. And these codes worked perfectly simultaneously with a central DHCP server and TinyPXE's ProxyDHCP.

Currently, the ipxe-legacy.pxe file compiled in mbr mode cannot download the autoexec.ipxe file from my server.

My DHCP policies (which I believe are fine, as they worked in older ipxe versions)

This problem only occurs when requests are sent in mbr mode. EFI mode works without issues.

autoexec.ipxe file contents:
#!ipxe
dhcp ||
sleep 3
set menu-url http://${66}/autoexec.ipxe
initrd ${menu-url} && goto success || goto failure
sleep 2
goto command

:failure
echo Failure!
sleep 5

:command
chain ${menu-url} ||
shell

My compilation code:
make -j$(nproc) bin/ipxe-legacy.pxe EMBED=autoexec.ipxe

Where am I going wrong?

[NiKiZe]

As described in https://github.com/ipxe/ipxe/blob/master/CONTRIBUTING.md#bug-reports please use discussions for questions.
If an actual bug can be confirmed, and described, then we can move that to an issue to solve.
(If issues are created that is not clear bugs, they are moved, and if possible given a reply, but it needs to be moved first, a move is in no way a close or shutting it down)

So what you call MBR is pcbios mode.
The embedded script have set menu-url http://${66}/autoexec.ipxe
From the output we see http:///autoexec.ipxe

So there is no value for ${66}
Since you have both a DHCP and proxyDHCP and your main DHCP does provide option 66 when it matches PXE Legacy policy, what is that policy filter? and same for iPXE? And which values does your proxyDHCP have?

Getting the settings for the DHCP itself isn't really helpful since we don't know specifics of every server, so the best way is also to get a packet dump, use tcpdump or wireshark for that, hopefully you can see the options that the client might have and figure out why 66 is empty. But also, add a shell to your embedded script and run config, and check all nodes on the nic. iPXE does try to be smart and uses cached dhcp packets in some cases.

[NiKiZe]

Another thing, if this is not just random between which packets comes in first or similar, and it always works in some older version let us know which version that is, and then use git bisect to narrow down which git commit that introduced the difference.