PiHole V6 2025.02.6 TFTP Error

[TheGCat]

Hello,

in the new version the TFTP Server is nonfunctional:

The V5 section on the image is working. When I stop the old V5 Version and start the new V6, he can't access this file for example.

I have of course enabled the TFTP Server in DNSMASQ:

enable-tftp
tftp-root=/tftpboot

# PXEClient Codes
dhcp-vendorclass=x86-BIOS,PXEClient:Arch:00000   # BIOS/Legacy Modus
dhcp-vendorclass=x86-UEFI32,PXEClient:Arch:00006 # x86 32-Bit EFI
dhcp-vendorclass=x86-UEFI,PXEClient:Arch:00007   # x86_64 64-Bit EFI
dhcp-vendorclass=x86-UEFI64,PXEClient:Arch:00009 # x86_64 64-Bit EFI veraltet!
dhcp-vendorclass=ARM-UEFI32,PXEClient:Arch:00010 # ARM 32-Bit EFI
dhcp-vendorclass=ARM-UEFI64,PXEClient:Arch:00011 # ARM 64-Bit EFI

dhcp-match=set:iPXE,175 # iPXE sends a 175 option.

# Die erste Zeile ist stets die Firmware!
# Die zweite Zeile ist der eigentliche Bootloader!

# BIOS/Legacy Modus
dhcp-boot=tag:!iPXE,tag:x86-BIOS,undionly.kpxe,0.0.0.0,0.0.0.0
dhcp-boot=tag:x86-BIOS,tag:iPXE,pxelinux.kpxe,0.0.0.0,0.0.0.0

# x86_64 64-Bit EFI
# Standard für die meisten UEFI Rechner
dhcp-boot=tag:!iPXE,tag:x86-UEFI,iPXE64.efi,0.0.0.0,0.0.0.0
dhcp-boot=tag:x86-UEFI,tag:iPXE,pxeEFI64.ipxe,0.0.0.0,0.0.0.0

# x86_64 64-Bit EFI Veraltet! Manche VMs benötigen diesen Eintrag noch!
dhcp-boot=tag:!iPXE,tag:x86-UEFI64,iPXE64.efi,0.0.0.0,0.0.0.0
dhcp-boot=tag:x86-UEFI64,tag:iPXE,pxeEFI64.ipxe,0.0.0.0,0.0.0.0

In the pihole.log i can find: "unsupported request from 192.168.1.1" = That is the TFTP Request from my image in V6.

In the V5 Version the line reports: dnsmasq-tftp[235]: sent /tftpboot/iPXE64.efi to 192.168.1.1

What's wrong?

Any ideas?

[Bucking_Horn]

Those options are not offered or advertised by Pi-hole or pihole-FTL, but by dnsmasq.

They only would have been used in v5 if you had manually applied a custom dnsmasq configuration.

Did you enable custom dnsmasq configurations in Pi-hole v6 yet?

If not, have a read of Custom dnsmasq configs not loading.

[TheGCat]

Hi, of course I enabled it.

He loads the file: "iPXE64.efi" during the PXE start, but can't load the iPXE scriptfile. It is 1:1 the same script. V5 is working: V6 not.

[Bucking_Horn]

Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:

pihole -d

or if you run your Pi-hole as a Docker container:

docker exec -it <pihole-container-name-or-id> pihole -d

where you substitute <pihole-container-name-or-id> as required.

[TheGCat]

https://tricorder.pi-hole.net/ll31y7PE/

THX.

[Bucking_Horn]

Pi-hole v5 ran with sudo powers, Pi-hole v6 doesn't anymore.

pihole-FTL may lack permissions to access your boot files.

Please check permissions on your boot files, and either grant access to the pihole user, or put your files in a path where pihole is allowed to read from.

[Bucking_Horn]

This seems to be a bug in upstream dnsmasq, where a fix is currently discussed at [Dnsmasq-discuss] [PATCH] TFTP off-by-2 bugfix - CRASH.

[TheGCat]

Thank you for your answer. But I switched to Adguard, because this was not the only issue I had with the new release. Sorry, but I don't want to be an Beta Tester!