As it turns out, UEFI does support PXE menus, but the implementations are
rather buggy in that regard. VMware often does not render the menu on the
screen, but you can blindly select the menu entry using the arrow keys and boot
it with the return key. A recent Asus laptop renders the menu, but
Actually, I shouldn’t set the siaddr in the initial Offer. It’s fine for VMware
UEFI and BIOS, but the Asus UEFI will end up trying to download the boot file
from the Offer’s siaddr instead of the ACK’s siaddr if it’s present. So the
small additional modification below will also allow the TFTP
More wiresharking helped me figure this out. So when UEFI receives a DHCP Offer
or Proxy DHCP Offer with Vendor Class Identifier (option 60) set to PXEClient,
it sends a DHCP Request to the siaddr from the offer, but on port 4011. If the
server then sends a DHCP ACK back to port 4011,
Is there any sort of standards document that explains how this is
supposed to work in EFI?
Cheers,
Simon.
On 19/10/15 12:54, Michael Kuron wrote:
> I made some changes to dnsmasq (patch below) that remove the PXE menu system
> (the option 43 stuff) if there’s only one menu entry and put the
I made some changes to dnsmasq (patch below) that remove the PXE menu system
(the option 43 stuff) if there’s only one menu entry and put the boot file name
and server address directly into the file and siaddr fields. This works fine
for BIOS systems, but doesn’t work for UEFI either.
Next
The problem in known, but not the solution. I did start working on that
about six months ago, but got bogged down in creating a test system.
What would be really useful would be to find an implementation that
works with UEFI and proxy DHCP, and getting for packet captures to show
what should be
