Be very careful about what filename you specify in dhcpd.conf if you get an error like this:

NBP filesize is 0 Bytes PXE-E23: Client received TFTP error from server.

If you specify "BOOTx64.efi" then the file had better not be called "BOOTx64.EFI" as it is case sensitive.  It's really a case of the file technically not existing.

You can verify this by checking your tftp logs:

routerOS in.tftpd[169277]: RRQ from 192.168.1.193 filename /BOOTx64.efi

Then check the actual name of the file:
BOOTx64.EFI  efi  EFI  grub.cfg  images  ldlinux.c32  libutil.c32  menu.c32  pxelinux.0  pxelinux.cfg  syslinux.efi

Whoops .EFI != .efi so let's fix it and then we boot OK:

mv BOOTx64.EFI BOOTx64.efi
 

pxe, bootx, efi, grub, booting, bytes, tftp, dhcp, nbp, filesize, filename, specify, dhcpd, conf, server, quot, existing, verify, logs, routeros, tftpd, rrq, cfg, images, ldlinux, libutil, pxelinux, syslinux, whoops, ok, mv,

Latest Articles