PXE booting EFI client

[john doe]

Debians,

I'm trying to pxe boot a client with UEFI BIOS to no avail.

Everything works with legacy BIOS but if I use those two lines in my
dnsmasq.conf:

"dhcp-boot=bootnetx64.efi
pxe-service=X86-64_EFI, "Boot UEFI PXE-64", bootnetx64.efi"


the client gets an IP but no file are sent.

I'm at a lost on what to do to PXE boot a EFI client.

Does PXE booting of EFI clients require other ports than 69 UDP and 4011
UDP?

Any pointers is appreciated.

--
John Doe

[Sven Hoexter]

On Tue, Sep 06, 2022 at 07:21:59PM +0200, john doe wrote:
> Debians,
>
> I'm trying to pxe boot a client with UEFI BIOS to no avail.
>
> Everything works with legacy BIOS but if I use those two lines in my
> dnsmasq.conf:
>
> "dhcp-boot=bootnetx64.efi
> pxe-service=X86-64_EFI, "Boot UEFI PXE-64", bootnetx64.efi"

Maybe you've a host which sents as architecture "00007" instead of
"00009" via DHCP and this pxe-service is not matched at all. You
can figure that out if you look with wireshark at the DHCP traffic.
According to my notes the protocol option field is 93 you've to look at.
I ran into such an issue a few years back with HPE DL360G10 vs DL120G9.

Config setting to try out would be:
pxe-service=BC_EFI, "Boot UEFI PXE-64", bootnetx64.efi"

Sven

[john doe]

Thanks to the help of "Sven Hoexter <sv...@stormbind.net>' I got it
working by doing:
/etc/dnsmasq.conf:

pxe-service=BC_EFI, "Boot UEFI PXE-64",

/debian-installer/amd64/bootnetx64.efi

I emulate the 'dhcp-boot' option in a option file:
option:bootfile-name,/debian-installer/amd64/bootnetx64.efi

I also had to put the below file in the tftp root directory:
grubx64.efi

Sven's blog [1] has more info on all of this.


[1] https://sven.stormbind.net/blog/posts/deb_stretch_hpe_dl360/

--
John Doe