pihole 6 dnsmasq pxe enable-tftp possible?

Schnabulator · February 18, 2025, 9:27pm

Hello,
today I updated to pihole 6. Previously i used this config to get a simple PXE boot service running for my pis.
'''
enable-tftp
tftp-root=/tftpboot
pxe-service=0,"Raspberry Pi Boot"
'''
How can i create a similar config with pihole 6?

Greetings and thank you in advance

yubiuser · February 18, 2025, 9:28pm

Go to Settings > All Settings > Misc > and enter it into misc.dnsmasq_lines

Schnabulator · February 18, 2025, 9:28pm

Found it thank you guys
Should FTL load additional dnsmasq configuration files from /etc/dnsmasq.d/?
etc_dnsmasq_d = true

yubiuser · February 18, 2025, 9:34pm

This is an other possibility if you want to put your code as a dnsmasq config file and load it on Pi-hole startup.

Both ways should work

Schnabulator · February 18, 2025, 10:10pm

good thing is i can see the rainbow splash. Sadly nothing more happens.
Pi does not boot anymore

setting/misc.dnsmasq_lines

enable-tftp
tftp-root=/tftpboot
# pxe rpi
pxe-service=0,"Raspberry Pi Boot"

The directory is mounted to /tftpboot

Volume=/srv/tftpboot:/tftpboot

container quadlet /etc/containers/systemd/pihole.container

[Unit]
Description=pihole container
Wants=network-online.target
After=network-online.target nss-lookup.target

[Container]
Image=docker.io/pihole/pihole:latest
ContainerName=pihole
HostName=pihole.ohs.lan
IP=192.168.2.254
Network=macvlan.network

# extra caps
AddCapability=NET_ADMIN CAP_NET_RAW NET_RAW

# Enable auto-update container
AutoUpdate=registry

Volume=/srv/container/pihole/etc-pihole:/etc/pihole
Volume=/srv/container/pihole/etc-dnsmasq.d:/etc/dnsmasq.d
Volume=/srv/tftpboot:/tftpboot

Environment=TZ=Europe/Berlin
Environment=WEBPASSWORD=piholepw

[Service]
Restart=always
TimeoutStartSec=900

[Install]
WantedBy=default.target

nothing special was configured in previous release i think.

Greetings

PromoFaux · February 18, 2025, 11:55pm

This is no longer a valid environment variable, though probably not directly related to your issue.

https://docs.pi-hole.net/docker/upgrading/v5-v6/

Schnabulator · February 19, 2025, 5:43am

Yes, the variable will be removed, thank you.
I have seen that there is a migration directory.

etc-pihole/migration_backup_v6

Unfortunately, I have later this day time to compare the configs.
Do you know if there was changes in pihole6 - dnsmasq related to pxe?

Thank you in advance.

DL6ER · February 19, 2025, 7:31am

From the dnsmasq CHANGELOG:

  57         Add --dhcp-option-pxe config. This acts almost exactly like
  58         --dhcp-option except that the defined option is only sent when
  59         replying to PXE clients. More importantly, these options are sent
  60         in reply PXE clients when dnsmasq in acting in PXE proxy mode. In
  61         PXE proxy mode, the set of options sent is defined by the PXE standard
  62         and the normal set of options is not sent. This config allows arbitrary
  63         options in PXE-proxy replies. A typical use-case is to send option
  64         175 to iPXE. Thanks to Jason Berry for finding the requirement for
  65         this.
  66
  67         Support PXE proxy-DHCP and DHCP-relay at the same time.
  68         When using PXE proxy-DHCP, dnsmasq supplies PXE information to
  69         the client, which also talks to another "normal" DHCP server
  70         for address allocation and similar. The normal DHCP server may
  71         be on the local network, but it may also be remote, and accessed via
  72         a DHCP relay. This change allows dnsmasq to act as both a
  73         PXE proxy-DHCP server AND a DHCP relay for the same network.

That's it.

Schnabulator · February 19, 2025, 8:36pm

@DL6ER i dont know how to set dhcp-option-pxe and tried various things.
So far I had no luck to get pxe running with v6. Pis stuck always @ rainbow splash.

The bootfiles have the correct permissions (chmod -R 755 /srv/tftpboot)

As a workaround the container was downgraded, and pxe worked again like expected

image=docker.io/pihole/pihole:2024.07.0

container quadlet /etc/containers/systemd/pihole.container

[Unit]
Description=pihole container
Wants=network-online.target
After=network-online.target nss-lookup.target

[Container]
#Image=docker.io/pihole/pihole:latest
Image=docker.io/pihole/pihole:2024.07.0

ContainerName=pihole
HostName=pihole.ohs.lan
IP=192.168.2.254
Network=macvlan.network

AddCapability=CAP_NET_ADMIN CAP_NET_RAW CAP_NET_BIND_SERVICE CAP_CHOWN
AutoUpdate=registry

Volume=/srv/container/pihole/etc-pihole:/etc/pihole
Volume=/srv/container/pihole/etc-dnsmasq.d:/etc/dnsmasq.d
Volume=/srv/tftpboot:/tftpboot

Environment=TZ=Europe/Berlin
Environment=WEBPASSWORD=piholepw

[Service]
Restart=always
TimeoutStartSec=900

[Install]
WantedBy=default.target

Thanks @ all so far

DL6ER · February 19, 2025, 8:59pm

Do you have any related logs from /var/log/pihole/pihole.log ?
It'd also be worth using some tool like tcpdump to record a pcap from the working and the non-working containers so we can do an in-depth debugging looking at the differences between the two.

nero355 · February 19, 2025, 10:27pm

When passing some DHCP Options like 43 for example you need to encode the stuff you are sending to the Client in a certain format : Maybe you need to do this too from now on ?!

/Very wild guess...

Schnabulator · March 2, 2025, 10:42am

sorry for the delay. Here are the tcpdumps and log details for latest and 2024.07.0.

tcpdump with pihole6 (latest)

sudo tcpdump -i eth0 port bootpc
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
11:27:46.885850 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from e4:5f:01:54:40:25 (oui Unknown), length 322
11:27:49.890929 IP pi.hole.bootps > 192.168.2.37.bootpc: BOOTP/DHCP, Reply, length 363
11:27:49.891529 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from e4:5f:01:54:40:25 (oui Unknown), length 309
11:27:49.893675 IP pi.hole.bootps > 192.168.2.37.bootpc: BOOTP/DHCP, Reply, length 307
11:27:54.966017 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from e4:5f:01:54:40:25 (oui Unknown), length 322
11:27:54.966833 IP pi.hole.bootps > 192.168.2.37.bootpc: BOOTP/DHCP, Reply, length 363
11:27:54.967431 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from e4:5f:01:54:40:25 (oui Unknown), length 309
11:27:54.969490 IP pi.hole.bootps > 192.168.2.37.bootpc: BOOTP/DHCP, Reply, length 307
11:28:00.099091 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from e4:5f:01:54:40:25 (oui Unknown), length 322
11:28:00.099847 IP pi.hole.bootps > 192.168.2.37.bootpc: BOOTP/DHCP, Reply, length 363
11:28:00.100453 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from e4:5f:01:54:40:25 (oui Unknown), length 309
11:28:00.102236 IP pi.hole.bootps > 192.168.2.37.bootpc: BOOTP/DHCP, Reply, length 307
11:28:05.232091 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from e4:5f:01:54:40:25 (oui Unknown), length 322
11:28:05.232852 IP pi.hole.bootps > 192.168.2.37.bootpc: BOOTP/DHCP, Reply, length 363
11:28:05.233489 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from e4:5f:01:54:40:25 (oui Unknown), length 309
11:28:05.235570 IP pi.hole.bootps > 192.168.2.37.bootpc: BOOTP/DHCP, Reply, length 307
11:28:10.365131 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from e4:5f:01:54:40:25 (oui Unknown), length 322
11:28:10.365485 IP pi.hole.bootps > 192.168.2.37.bootpc: BOOTP/DHCP, Reply, length 363
11:28:10.366072 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from e4:5f:01:54:40:25 (oui Unknown), length 309
11:28:10.367759 IP pi.hole.bootps > 192.168.2.37.bootpc: BOOTP/DHCP, Reply, length 307
11:28:15.431410 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from e4:5f:01:54:40:25 (oui Unknown), length 322
11:28:15.431848 IP pi.hole.bootps > 192.168.2.37.bootpc: BOOTP/DHCP, Reply, length 363
11:28:15.432434 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from e4:5f:01:54:40:25 (oui Unknown), length 309
11:28:15.435042 IP pi.hole.bootps > 192.168.2.37.bootpc: BOOTP/DHCP, Reply, length 307
11:28:20.498854 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from e4:5f:01:54:40:25 (oui Unknown), length 322
11:28:20.499427 IP pi.hole.bootps > 192.168.2.37.bootpc: BOOTP/DHCP, Reply, length 363
11:28:20.500074 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from e4:5f:01:54:40:25 (oui Unknown), length 309
11:28:20.502231 IP pi.hole.bootps > 192.168.2.37.bootpc: BOOTP/DHCP, Reply, length 307
11:28:25.564715 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from e4:5f:01:54:40:25 (oui Unknown), length 322
11:28:25.565151 IP pi.hole.bootps > 192.168.2.37.bootpc: BOOTP/DHCP, Reply, length 363
11:28:25.565783 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from e4:5f:01:54:40:25 (oui Unknown), length 309
11:28:25.567311 IP pi.hole.bootps > 192.168.2.37.bootpc: BOOTP/DHCP, Reply, length 307
11:28:30.631334 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from e4:5f:01:54:40:25 (oui Unknown), length 322
11:28:30.632022 IP pi.hole.bootps > 192.168.2.37.bootpc: BOOTP/DHCP, Reply, length 363
11:28:30.632663 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from e4:5f:01:54:40:25 (oui Unknown), length 309
11:28:30.634492 IP pi.hole.bootps > 192.168.2.37.bootpc: BOOTP/DHCP, Reply, length 307

log details with pihole 6 (latest)

cat pihole.log | grep 192.168.2.37
Mar  2 11:27:49 dnsmasq-dhcp[51]: DHCPOFFER(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 11:27:49 dnsmasq-dhcp[51]: DHCPREQUEST(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 11:27:49 dnsmasq-dhcp[51]: DHCPACK(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 11:27:49 dnsmasq-tftp[51]: file /tftpboot/75a721db/start4.elf not found for 192.168.2.37
Mar  2 11:27:49 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:27:49 dnsmasq-tftp[51]: file /tftpboot/config.txt not found for 192.168.2.37
Mar  2 11:27:49 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:27:49 dnsmasq-tftp[51]: file /tftpboot/recover4.elf not found for 192.168.2.37
Mar  2 11:27:49 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:27:49 dnsmasq-tftp[51]: file /tftpboot/start4.elf not found for 192.168.2.37
Mar  2 11:27:49 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:27:49 dnsmasq[301]: config 192.168.2.37 is NXDOMAIN
Mar  2 11:27:54 dnsmasq-dhcp[51]: DHCPOFFER(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 11:27:54 dnsmasq-dhcp[51]: DHCPREQUEST(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 11:27:54 dnsmasq-dhcp[51]: DHCPACK(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 11:27:54 dnsmasq-tftp[51]: file /tftpboot/75a721db/start4.elf not found for 192.168.2.37
Mar  2 11:27:54 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:27:54 dnsmasq-tftp[51]: file /tftpboot/config.txt not found for 192.168.2.37
Mar  2 11:27:54 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:27:54 dnsmasq-tftp[51]: file /tftpboot/recover4.elf not found for 192.168.2.37
Mar  2 11:27:54 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:27:54 dnsmasq-tftp[51]: file /tftpboot/start4.elf not found for 192.168.2.37
Mar  2 11:27:55 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:00 dnsmasq-dhcp[51]: DHCPOFFER(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 11:28:00 dnsmasq-dhcp[51]: DHCPREQUEST(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 11:28:00 dnsmasq-dhcp[51]: DHCPACK(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 11:28:00 dnsmasq-tftp[51]: file /tftpboot/75a721db/start4.elf not found for 192.168.2.37
Mar  2 11:28:00 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:00 dnsmasq-tftp[51]: file /tftpboot/config.txt not found for 192.168.2.37
Mar  2 11:28:00 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:00 dnsmasq-tftp[51]: file /tftpboot/recover4.elf not found for 192.168.2.37
Mar  2 11:28:00 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:00 dnsmasq-tftp[51]: file /tftpboot/start4.elf not found for 192.168.2.37
Mar  2 11:28:00 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:05 dnsmasq-dhcp[51]: DHCPOFFER(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 11:28:05 dnsmasq-dhcp[51]: DHCPREQUEST(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 11:28:05 dnsmasq-dhcp[51]: DHCPACK(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 11:28:05 dnsmasq-tftp[51]: file /tftpboot/75a721db/start4.elf not found for 192.168.2.37
Mar  2 11:28:05 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:05 dnsmasq-tftp[51]: file /tftpboot/config.txt not found for 192.168.2.37
Mar  2 11:28:05 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:05 dnsmasq-tftp[51]: file /tftpboot/recover4.elf not found for 192.168.2.37
Mar  2 11:28:05 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:05 dnsmasq-tftp[51]: file /tftpboot/start4.elf not found for 192.168.2.37
Mar  2 11:28:05 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:10 dnsmasq-dhcp[51]: DHCPOFFER(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 11:28:10 dnsmasq-dhcp[51]: DHCPREQUEST(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 11:28:10 dnsmasq-dhcp[51]: DHCPACK(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 11:28:10 dnsmasq-tftp[51]: file /tftpboot/75a721db/start4.elf not found for 192.168.2.37
Mar  2 11:28:10 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:10 dnsmasq-tftp[51]: file /tftpboot/config.txt not found for 192.168.2.37
Mar  2 11:28:10 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:10 dnsmasq-tftp[51]: file /tftpboot/recover4.elf not found for 192.168.2.37
Mar  2 11:28:10 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:10 dnsmasq-tftp[51]: file /tftpboot/start4.elf not found for 192.168.2.37
Mar  2 11:28:10 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:15 dnsmasq-dhcp[51]: DHCPOFFER(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 11:28:15 dnsmasq-dhcp[51]: DHCPREQUEST(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 11:28:15 dnsmasq-dhcp[51]: DHCPACK(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 11:28:15 dnsmasq-tftp[51]: file /tftpboot/75a721db/start4.elf not found for 192.168.2.37
Mar  2 11:28:15 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:15 dnsmasq-tftp[51]: file /tftpboot/config.txt not found for 192.168.2.37
Mar  2 11:28:15 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:15 dnsmasq-tftp[51]: file /tftpboot/recover4.elf not found for 192.168.2.37
Mar  2 11:28:15 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:15 dnsmasq-tftp[51]: file /tftpboot/start4.elf not found for 192.168.2.37
Mar  2 11:28:15 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:20 dnsmasq-dhcp[51]: DHCPOFFER(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 11:28:20 dnsmasq-dhcp[51]: DHCPREQUEST(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 11:28:20 dnsmasq-dhcp[51]: DHCPACK(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 11:28:20 dnsmasq-tftp[51]: file /tftpboot/75a721db/start4.elf not found for 192.168.2.37
Mar  2 11:28:20 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:20 dnsmasq-tftp[51]: file /tftpboot/config.txt not found for 192.168.2.37
Mar  2 11:28:20 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:20 dnsmasq-tftp[51]: file /tftpboot/recover4.elf not found for 192.168.2.37
Mar  2 11:28:20 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:20 dnsmasq-tftp[51]: file /tftpboot/start4.elf not found for 192.168.2.37
Mar  2 11:28:20 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:25 dnsmasq-dhcp[51]: DHCPOFFER(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 11:28:25 dnsmasq-dhcp[51]: DHCPREQUEST(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 11:28:25 dnsmasq-dhcp[51]: DHCPACK(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 11:28:25 dnsmasq-tftp[51]: file /tftpboot/75a721db/start4.elf not found for 192.168.2.37
Mar  2 11:28:25 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:25 dnsmasq-tftp[51]: file /tftpboot/config.txt not found for 192.168.2.37
Mar  2 11:28:25 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:25 dnsmasq-tftp[51]: file /tftpboot/recover4.elf not found for 192.168.2.37
Mar  2 11:28:25 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:25 dnsmasq-tftp[51]: file /tftpboot/start4.elf not found for 192.168.2.37
Mar  2 11:28:25 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:30 dnsmasq-dhcp[51]: DHCPOFFER(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 11:28:30 dnsmasq-dhcp[51]: DHCPREQUEST(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 11:28:30 dnsmasq-dhcp[51]: DHCPACK(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 11:28:30 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:30 dnsmasq-tftp[51]: error 0 Early terminate received from 192.168.2.37
Mar  2 11:28:30 dnsmasq-tftp[51]: sent /tftpboot/75a721db/start.elf to 192.168.2.37
Mar  2 11:28:30 dnsmasq-tftp[51]: sent /tftpboot/75a721db/config.txt to 192.168.2.37
Mar  2 11:28:30 dnsmasq-tftp[51]: file /tftpboot/75a721db/pieeprom.sig not found for 192.168.2.37
Mar  2 11:28:30 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:30 dnsmasq-tftp[51]: file /tftpboot/75a721db/recovery.elf not found for 192.168.2.37
Mar  2 11:28:30 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:32 dnsmasq-tftp[51]: sent /tftpboot/75a721db/start.elf to 192.168.2.37
Mar  2 11:28:32 dnsmasq-tftp[51]: sent /tftpboot/75a721db/fixup.dat to 192.168.2.37
Mar  2 11:28:33 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:33 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:33 dnsmasq-tftp[51]: error 0 Early terminate received from 192.168.2.37
Mar  2 11:28:33 dnsmasq-tftp[51]: failed sending /tftpboot/75a721db/config.txt to 192.168.2.37
Mar  2 11:28:33 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:33 dnsmasq-tftp[51]: file /tftpboot/75a721db/recovery.elf not found for 192.168.2.37
Mar  2 11:28:33 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:33 dnsmasq-tftp[51]: file /tftpboot/75a721db/bootcfg.txt not found for 192.168.2.37
Mar  2 11:28:34 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:34 dnsmasq-tftp[51]: file /tftpboot/75a721db/recovery8-32.img not found for 192.168.2.37
Mar  2 11:28:34 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:34 dnsmasq-tftp[51]: file /tftpboot/75a721db/recovery7.img not found for 192.168.2.37
Mar  2 11:28:34 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:34 dnsmasq-tftp[51]: file /tftpboot/75a721db/kernel8.img not found for 192.168.2.37
Mar  2 11:28:34 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:34 dnsmasq-tftp[51]: file /tftpboot/75a721db/kernel7l.img not found for 192.168.2.37
Mar  2 11:28:34 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:34 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:34 dnsmasq-tftp[51]: error 0 Early terminate received from 192.168.2.37
Mar  2 11:28:34 dnsmasq-tftp[51]: failed sending /tftpboot/75a721db/kernel.img to 192.168.2.37
Mar  2 11:28:34 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:34 dnsmasq-tftp[51]: error 0 Early terminate received from 192.168.2.37
Mar  2 11:28:34 dnsmasq-tftp[51]: failed sending /tftpboot/75a721db/bcm2711-rpi-4-b.dtb to 192.168.2.37
Mar  2 11:28:34 dnsmasq-tftp[51]: sent /tftpboot/75a721db/bcm2711-rpi-4-b.dtb to 192.168.2.37
Mar  2 11:28:34 dnsmasq-tftp[51]: error 0 Early terminate received from 192.168.2.37
Mar  2 11:28:34 dnsmasq-tftp[51]: failed sending /tftpboot/75a721db/overlays/overlay_map.dtb to 192.168.2.37
Mar  2 11:28:34 dnsmasq-tftp[51]: sent /tftpboot/75a721db/overlays/overlay_map.dtb to 192.168.2.37
Mar  2 11:28:34 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:34 dnsmasq-tftp[51]: error 0 Early terminate received from 192.168.2.37
Mar  2 11:28:34 dnsmasq-tftp[51]: failed sending /tftpboot/75a721db/config.txt to 192.168.2.37
Mar  2 11:28:34 dnsmasq-tftp[51]: unsupported request from 192.168.2.37
Mar  2 11:28:34 dnsmasq-tftp[51]: file /tftpboot/75a721db/armstub8-32-gic.bin not found for 192.168.2.37

tcpdump with pihole 2024.07.0

sudo tcpdump -i eth0 port bootpc
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
10:59:59.922891 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from e4:5f:01:54:40:25 (oui Unknown), length 322
10:59:59.923772 IP pi.hole.bootps > 192.168.2.37.bootpc: BOOTP/DHCP, Reply, length 350
10:59:59.924403 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from e4:5f:01:54:40:25 (oui Unknown), length 309
10:59:59.927156 IP pi.hole.bootps > 192.168.2.37.bootpc: BOOTP/DHCP, Reply, length 301
11:00:25.974255 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from e4:5f:01:54:40:25 (oui Unknown), length 548
11:00:25.974945 IP pi.hole.bootps > 192.168.2.37.bootpc: BOOTP/DHCP, Reply, length 301
11:00:25.980916 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from e4:5f:01:54:40:25 (oui Unknown), length 548
11:00:25.983753 IP pi.hole.bootps > 192.168.2.37.bootpc: BOOTP/DHCP, Reply, length 301
11:00:39.089406 IP COM-MID1.ohs.lan.bootpc > pi.hole.bootps: BOOTP/DHCP, Request from 80:c7:55:ba:b7:c5 (oui Unknown), length 328
11:00:39.092157 IP pi.hole.bootps > COM-MID1.ohs.lan.bootpc: BOOTP/DHCP, Reply, length 301

log details with pihole 2024.07.0

Mar  2 10:59:59 dnsmasq-dhcp[263]: DHCPOFFER(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 10:59:59 dnsmasq-dhcp[263]: DHCPREQUEST(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 10:59:59 dnsmasq-dhcp[263]: DHCPACK(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 10:59:59 dnsmasq-tftp[263]: file /tftpboot/75a721db/start4.elf not found for 192.168.2.37
Mar  2 10:59:59 dnsmasq-tftp[263]: error 0 Early terminate received from 192.168.2.37
Mar  2 10:59:59 dnsmasq-tftp[263]: sent /tftpboot/75a721db/start.elf to 192.168.2.37
Mar  2 10:59:59 dnsmasq-tftp[263]: sent /tftpboot/75a721db/config.txt to 192.168.2.37
Mar  2 10:59:59 dnsmasq-tftp[263]: file /tftpboot/75a721db/pieeprom.sig not found for 192.168.2.37
Mar  2 10:59:59 dnsmasq-tftp[263]: file /tftpboot/75a721db/recover4.elf not found for 192.168.2.37
Mar  2 10:59:59 dnsmasq-tftp[263]: file /tftpboot/75a721db/recovery.elf not found for 192.168.2.37
Mar  2 10:59:59 dnsmasq-tftp[263]: file /tftpboot/75a721db/start4.elf not found for 192.168.2.37
Mar  2 11:00:01 dnsmasq-tftp[263]: sent /tftpboot/75a721db/start.elf to 192.168.2.37
Mar  2 11:00:01 dnsmasq-tftp[263]: sent /tftpboot/75a721db/fixup.dat to 192.168.2.37
Mar  2 11:00:02 dnsmasq-tftp[263]: file /tftpboot/75a721db/recovery.elf not found for 192.168.2.37
Mar  2 11:00:02 dnsmasq-tftp[263]: error 0 Early terminate received from 192.168.2.37
Mar  2 11:00:02 dnsmasq-tftp[263]: failed sending /tftpboot/75a721db/config.txt to 192.168.2.37
Mar  2 11:00:02 dnsmasq-tftp[263]: sent /tftpboot/75a721db/config.txt to 192.168.2.37
Mar  2 11:00:02 dnsmasq-tftp[263]: error 0 Early terminate received from 192.168.2.37
Mar  2 11:00:02 dnsmasq-tftp[263]: sent /tftpboot/75a721db/distroconfig.txt to 192.168.2.37
Mar  2 11:00:02 dnsmasq-tftp[263]: sent /tftpboot/75a721db/distroconfig.txt to 192.168.2.37
Mar  2 11:00:02 dnsmasq-tftp[263]: file /tftpboot/75a721db/dt-blob.bin not found for 192.168.2.37
Mar  2 11:00:02 dnsmasq-tftp[263]: file /tftpboot/75a721db/recovery.elf not found for 192.168.2.37
Mar  2 11:00:02 dnsmasq-tftp[263]: error 0 Early terminate received from 192.168.2.37
Mar  2 11:00:02 dnsmasq-tftp[263]: failed sending /tftpboot/75a721db/config.txt to 192.168.2.37
Mar  2 11:00:02 dnsmasq-tftp[263]: sent /tftpboot/75a721db/config.txt to 192.168.2.37
Mar  2 11:00:02 dnsmasq-tftp[263]: error 0 Early terminate received from 192.168.2.37
Mar  2 11:00:02 dnsmasq-tftp[263]: sent /tftpboot/75a721db/distroconfig.txt to 192.168.2.37
Mar  2 11:00:02 dnsmasq-tftp[263]: sent /tftpboot/75a721db/distroconfig.txt to 192.168.2.37
Mar  2 11:00:03 dnsmasq-tftp[263]: file /tftpboot/75a721db/bootcfg.txt not found for 192.168.2.37
Mar  2 11:00:03 dnsmasq-tftp[263]: error 0 Early terminate received from 192.168.2.37
Mar  2 11:00:03 dnsmasq-tftp[263]: failed sending /tftpboot/75a721db/kernel.img to 192.168.2.37
Mar  2 11:00:03 dnsmasq-tftp[263]: error 0 Early terminate received from 192.168.2.37
Mar  2 11:00:03 dnsmasq-tftp[263]: failed sending /tftpboot/75a721db/kernel.img to 192.168.2.37
Mar  2 11:00:03 dnsmasq-tftp[263]: error 0 Early terminate received from 192.168.2.37
Mar  2 11:00:03 dnsmasq-tftp[263]: failed sending /tftpboot/75a721db/bcm2711-rpi-4-b.dtb to 192.168.2.37
Mar  2 11:00:03 dnsmasq-tftp[263]: sent /tftpboot/75a721db/bcm2711-rpi-4-b.dtb to 192.168.2.37
Mar  2 11:00:03 dnsmasq-tftp[263]: error 0 Early terminate received from 192.168.2.37
Mar  2 11:00:03 dnsmasq-tftp[263]: failed sending /tftpboot/75a721db/overlays/overlay_map.dtb to 192.168.2.37
Mar  2 11:00:03 dnsmasq-tftp[263]: sent /tftpboot/75a721db/overlays/overlay_map.dtb to 192.168.2.37
Mar  2 11:00:03 dnsmasq-tftp[263]: error 0 Early terminate received from 192.168.2.37
Mar  2 11:00:03 dnsmasq-tftp[263]: failed sending /tftpboot/75a721db/config.txt to 192.168.2.37
Mar  2 11:00:03 dnsmasq-tftp[263]: sent /tftpboot/75a721db/config.txt to 192.168.2.37
Mar  2 11:00:03 dnsmasq-tftp[263]: error 0 Early terminate received from 192.168.2.37
Mar  2 11:00:03 dnsmasq-tftp[263]: sent /tftpboot/75a721db/distroconfig.txt to 192.168.2.37
Mar  2 11:00:03 dnsmasq-tftp[263]: sent /tftpboot/75a721db/distroconfig.txt to 192.168.2.37
Mar  2 11:00:03 dnsmasq-tftp[263]: error 0 Early terminate received from 192.168.2.37
Mar  2 11:00:03 dnsmasq-tftp[263]: failed sending /tftpboot/75a721db/overlays/vc4-kms-v3d-pi4.dtbo to 192.168.2.37
Mar  2 11:00:03 dnsmasq-tftp[263]: sent /tftpboot/75a721db/overlays/vc4-kms-v3d-pi4.dtbo to 192.168.2.37
Mar  2 11:00:03 dnsmasq-tftp[263]: error 0 Early terminate received from 192.168.2.37
Mar  2 11:00:03 dnsmasq-tftp[263]: sent /tftpboot/75a721db/cmdline.txt to 192.168.2.37
Mar  2 11:00:03 dnsmasq-tftp[263]: sent /tftpboot/75a721db/cmdline.txt to 192.168.2.37
Mar  2 11:00:04 dnsmasq-tftp[263]: file /tftpboot/75a721db/armstub8-gic.bin not found for 192.168.2.37
Mar  2 11:00:04 dnsmasq-tftp[263]: error 0 Early terminate received from 192.168.2.37
Mar  2 11:00:04 dnsmasq-tftp[263]: failed sending /tftpboot/75a721db/kernel.img to 192.168.2.37
Mar  2 11:00:06 dnsmasq-tftp[263]: sent /tftpboot/75a721db/kernel.img to 192.168.2.37
Mar  2 11:00:25 dnsmasq-dhcp[263]: DHCPOFFER(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 11:00:25 dnsmasq-dhcp[263]: DHCPREQUEST(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 11:00:25 dnsmasq-dhcp[263]: DHCPACK(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 11:00:39 dnsmasq[263]: query[A] time1.google.com from 192.168.2.37
...

I dont know how to fix Early terminate and unsupported requests with latest.
Also i don't know if it matters but after the client got the bootfiles via tftp, he should get the rest of the filesystem via nfs share from the host machine.

Greetings

Bucking_Horn · March 2, 2025, 11:14am

You may be affected by the same issue as in PiHole V6 2025.02.6 TFTP Error - #9 by Bucking_Horn.

Schnabulator · March 2, 2025, 12:14pm

@Bucking_Horn Maybe you are right.
In the container terminal for user root it is possible to cat files.
I have trouble to check if user pihole is able to cat files.

/tftpboot/rpi4-libreelec # cat cmdline.txt
boot=NFS=192.168.2.200:/srv/tftpboot/rpi4-libreelec disk=NFS=192.168.2.200:/srv/tftpstorage/@UID@ ip=dhcp
/tftpboot/rpi4-libreelec # su pihole
This account is not available

Here are the bootfiles in the container.

ls -la /tftpboot/rpi4-libreelec

´´´
drwxr-xr-x 3 root root 4096 Nov 16 16:44 .
drwxr-xr-x 10 root root 4096 Feb 19 19:13 ..
-rwxr-xr-x 1 root root 138252288 Aug 18 2024 SYSTEM
-rwxr-xr-x 1 root root 48 Aug 18 2024 SYSTEM.md5
-rwxr-xr-x 1 root root 32443 Aug 18 2024 bcm2710-rpi-2-b.dtb
-rwxr-xr-x 1 root root 35270 Aug 18 2024 bcm2710-rpi-3-b-plus.dtb
-rwxr-xr-x 1 root root 34635 Aug 18 2024 bcm2710-rpi-3-b.dtb
-rwxr-xr-x 1 root root 32222 Aug 18 2024 bcm2710-rpi-cm3.dtb
-rwxr-xr-x 1 root root 33612 Aug 18 2024 bcm2710-rpi-zero-2-w.dtb
-rwxr-xr-x 1 root root 33612 Aug 18 2024 bcm2710-rpi-zero-2.dtb
-rwxr-xr-x 1 root root 56056 Aug 18 2024 bcm2711-rpi-4-b.dtb
-rwxr-xr-x 1 root root 56060 Aug 18 2024 bcm2711-rpi-400.dtb
-rwxr-xr-x 1 root root 38349 Aug 18 2024 bcm2711-rpi-cm4-io.dtb
-rwxr-xr-x 1 root root 56540 Aug 18 2024 bcm2711-rpi-cm4.dtb
-rwxr-xr-x 1 root root 53343 Aug 18 2024 bcm2711-rpi-cm4s.dtb
-rwxr-xr-x 1 root root 80153 Aug 18 2024 bcm2712-rpi-5-b.dtb
-rwxr-xr-x 1 root root 80587 Aug 18 2024 bcm2712-rpi-cm5-cm4io.dtb
-rwxr-xr-x 1 root root 80579 Aug 18 2024 bcm2712-rpi-cm5-cm5io.dtb
-rwxr-xr-x 1 root root 80628 Aug 18 2024 bcm2712-rpi-cm5l-cm4io.dtb
-rwxr-xr-x 1 root root 80620 Aug 18 2024 bcm2712-rpi-cm5l-cm5io.dtb
-rwxr-xr-x 1 root root 80137 Aug 18 2024 bcm2712d0-rpi-5-b.dtb
-rwxr-xr-x 1 root root 106 Mar 2 11:23 cmdline.txt
....
´´´

after chowning the files to uid1000 (my user @ host / user pihole @ podman container) i see no different behaviour.

ls -la /tftpboot/rpi4-libreelec

´´´
/ # ls -la /tftpboot/rpi4-libreelec
total 150080
drwxr-xr-x 3 pihole pihole 4096 Nov 16 16:44 .
drwxr-xr-x 10 pihole pihole 4096 Feb 19 19:13 ..
-rwxr-xr-x 1 pihole pihole 138252288 Aug 18 2024 SYSTEM
-rwxr-xr-x 1 pihole pihole 48 Aug 18 2024 SYSTEM.md5
-rwxr-xr-x 1 pihole pihole 32443 Aug 18 2024 bcm2710-rpi-2-b.dtb
-rwxr-xr-x 1 pihole pihole 35270 Aug 18 2024 bcm2710-rpi-3-b-plus.dtb
-rwxr-xr-x 1 pihole pihole 34635 Aug 18 2024 bcm2710-rpi-3-b.dtb
-rwxr-xr-x 1 pihole pihole 32222 Aug 18 2024 bcm2710-rpi-cm3.dtb
-rwxr-xr-x 1 pihole pihole 33612 Aug 18 2024 bcm2710-rpi-zero-2-w.dtb
-rwxr-xr-x 1 pihole pihole 33612 Aug 18 2024 bcm2710-rpi-zero-2.dtb
-rwxr-xr-x 1 pihole pihole 56056 Aug 18 2024 bcm2711-rpi-4-b.dtb
-rwxr-xr-x 1 pihole pihole 56060 Aug 18 2024 bcm2711-rpi-400.dtb
-rwxr-xr-x 1 pihole pihole 38349 Aug 18 2024 bcm2711-rpi-cm4-io.dtb
-rwxr-xr-x 1 pihole pihole 56540 Aug 18 2024 bcm2711-rpi-cm4.dtb
-rwxr-xr-x 1 pihole pihole 53343 Aug 18 2024 bcm2711-rpi-cm4s.dtb
-rwxr-xr-x 1 pihole pihole 80153 Aug 18 2024 bcm2712-rpi-5-b.dtb
-rwxr-xr-x 1 pihole pihole 80587 Aug 18 2024 bcm2712-rpi-cm5-cm4io.dtb
-rwxr-xr-x 1 pihole pihole 80579 Aug 18 2024 bcm2712-rpi-cm5-cm5io.dtb
-rwxr-xr-x 1 pihole pihole 80628 Aug 18 2024 bcm2712-rpi-cm5l-cm4io.dtb
-rwxr-xr-x 1 pihole pihole 80620 Aug 18 2024 bcm2712-rpi-cm5l-cm5io.dtb
-rwxr-xr-x 1 pihole pihole 80137 Aug 18 2024 bcm2712d0-rpi-5-b.dtb
-rwxr-xr-x 1 pihole pihole 106 Mar 2 11:23 cmdline.txt
-rwxr-xr-x 1 pihole pihole 86 Aug 18 2024 cmdline.txt.bak
-rwxr-xr-x 1 pihole pihole 1533 Aug 18 2024 config.txt
-rwxr-xr-x 1 pihole pihole 360 Aug 18 2024 distroconfig-composite.txt
-rwxr-xr-x 1 pihole pihole 333 Aug 18 2024 distroconfig.txt
-rwxr-xr-x 1 pihole pihole 8451 Aug 18 2024 fixup.dat
-rwxr-xr-x 1 pihole pihole 1773 Aug 18 2024 hat_map.dtb
-rwxr-xr-x 1 pihole pihole 11370848 Aug 18 2024 kernel.img
-rwxr-xr-x 1 pihole pihole 48 Aug 18 2024 kernel.img.md5
drwxr-xr-x 2 pihole pihole 16384 Aug 18 2024 overlays
-rwxr-xr-x 1 pihole pihole 3006152 Aug 18 2024 start.elf

´´´

do you think there could be a problem?

tcpdump with uid1000 and pihole (latest)

12:54:44.628427 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from e4:5f:01:54:40:25 (oui Unknown), length 322
12:54:44.628683 IP pi.hole.bootps > 192.168.2.37.bootpc: BOOTP/DHCP, Reply, length 350
12:54:44.629318 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from e4:5f:01:54:40:25 (oui Unknown), length 309
12:54:44.630538 IP pi.hole.bootps > 192.168.2.37.bootpc: BOOTP/DHCP, Reply, length 307
12:54:49.691817 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from e4:5f:01:54:40:25 (oui Unknown), length 322
12:54:49.692199 IP pi.hole.bootps > 192.168.2.37.bootpc: BOOTP/DHCP, Reply, length 350
12:54:49.692779 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from e4:5f:01:54:40:25 (oui Unknown), length 309
12:54:49.695929 IP pi.hole.bootps > 192.168.2.37.bootpc: BOOTP/DHCP, Reply, length 307

log details with uid1000 and pihole (latest)

Mar  2 12:54:44 dnsmasq-dhcp[53]: DHCPOFFER(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 12:54:44 dnsmasq-dhcp[53]: DHCPREQUEST(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 12:54:44 dnsmasq-dhcp[53]: DHCPACK(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 12:54:44 dnsmasq-tftp[53]: file /tftpboot/75a721db/start4.elf not found for 192.168.2.37
Mar  2 12:54:44 dnsmasq-tftp[53]: unsupported request from 192.168.2.37
Mar  2 12:54:44 dnsmasq-tftp[53]: file /tftpboot/config.txt not found for 192.168.2.37
Mar  2 12:54:44 dnsmasq-tftp[53]: unsupported request from 192.168.2.37
Mar  2 12:54:44 dnsmasq-tftp[53]: file /tftpboot/recover4.elf not found for 192.168.2.37
Mar  2 12:54:44 dnsmasq-tftp[53]: unsupported request from 192.168.2.37
Mar  2 12:54:44 dnsmasq-tftp[53]: file /tftpboot/start4.elf not found for 192.168.2.37
Mar  2 12:54:44 dnsmasq-tftp[53]: unsupported request from 192.168.2.37
Mar  2 12:54:44 dnsmasq[184]: config 192.168.2.37 is NXDOMAIN
Mar  2 12:54:49 dnsmasq-dhcp[53]: DHCPOFFER(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 12:54:49 dnsmasq-dhcp[53]: DHCPREQUEST(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 12:54:49 dnsmasq-dhcp[53]: DHCPACK(eth0) 192.168.2.37 e4:5f:01:54:40:25 
Mar  2 12:54:49 dnsmasq-tftp[53]: unsupported request from 192.168.2.37
Mar  2 12:54:49 dnsmasq-tftp[53]: error 0 Early terminate received from 192.168.2.37
Mar  2 12:54:49 dnsmasq-tftp[53]: sent /tftpboot/75a721db/start.elf to 192.168.2.37
Mar  2 12:54:49 dnsmasq-tftp[53]: sent /tftpboot/75a721db/config.txt to 192.168.2.37
Mar  2 12:54:49 dnsmasq-tftp[53]: file /tftpboot/75a721db/pieeprom.sig not found for 192.168.2.37
Mar  2 12:54:49 dnsmasq-tftp[53]: unsupported request from 192.168.2.37
Mar  2 12:54:49 dnsmasq-tftp[53]: file /tftpboot/75a721db/recovery.elf not found for 192.168.2.37
Mar  2 12:54:49 dnsmasq-tftp[53]: unsupported request from 192.168.2.37
Mar  2 12:54:51 dnsmasq-tftp[53]: sent /tftpboot/75a721db/start.elf to 192.168.2.37
Mar  2 12:54:51 dnsmasq-tftp[53]: sent /tftpboot/75a721db/fixup.dat to 192.168.2.37
Mar  2 12:54:52 dnsmasq-tftp[53]: file /tftpboot/75a721db/recovery.elf not found for 192.168.2.37
Mar  2 12:54:52 dnsmasq-tftp[53]: unsupported request from 192.168.2.37
Mar  2 12:54:52 dnsmasq-tftp[53]: file /tftpboot/75a721db/dt-blob.bin not found for 192.168.2.37
Mar  2 12:54:52 dnsmasq-tftp[53]: unsupported request from 192.168.2.37
Mar  2 12:54:52 dnsmasq-tftp[53]: unsupported request from 192.168.2.37
Mar  2 12:54:52 dnsmasq-tftp[53]: error 0 Early terminate received from 192.168.2.37
Mar  2 12:54:52 dnsmasq-tftp[53]: failed sending /tftpboot/75a721db/config.txt to 192.168.2.37
Mar  2 12:54:52 dnsmasq-tftp[53]: unsupported request from 192.168.2.37
Mar  2 12:54:53 dnsmasq-tftp[53]: file /tftpboot/75a721db/recovery8.img not found for 192.168.2.37
Mar  2 12:54:53 dnsmasq-tftp[53]: unsupported request from 192.168.2.37
Mar  2 12:54:53 dnsmasq-tftp[53]: file /tftpboot/75a721db/recovery7l.img not found for 192.168.2.37
Mar  2 12:54:53 dnsmasq-tftp[53]: unsupported request from 192.168.2.37
Mar  2 12:54:53 dnsmasq-tftp[53]: file /tftpboot/75a721db/recovery.img not found for 192.168.2.37
Mar  2 12:54:53 dnsmasq-tftp[53]: unsupported request from 192.168.2.37
Mar  2 12:54:53 dnsmasq-tftp[53]: file /tftpboot/75a721db/kernel8-32.img not found for 192.168.2.37
Mar  2 12:54:53 dnsmasq-tftp[53]: unsupported request from 192.168.2.37
Mar  2 12:54:53 dnsmasq-tftp[53]: file /tftpboot/75a721db/kernel7.img not found for 192.168.2.37
Mar  2 12:54:53 dnsmasq-tftp[53]: unsupported request from 192.168.2.37
Mar  2 12:54:53 dnsmasq-tftp[53]: error 0 Early terminate received from 192.168.2.37
Mar  2 12:54:53 dnsmasq-tftp[53]: failed sending /tftpboot/75a721db/bcm2711-rpi-4-b.dtb to 192.168.2.37
Mar  2 12:54:53 dnsmasq-tftp[53]: sent /tftpboot/75a721db/bcm2711-rpi-4-b.dtb to 192.168.2.37
Mar  2 12:54:53 dnsmasq-tftp[53]: error 0 Early terminate received from 192.168.2.37
Mar  2 12:54:53 dnsmasq-tftp[53]: failed sending /tftpboot/75a721db/overlays/overlay_map.dtb to 192.168.2.37
Mar  2 12:54:53 dnsmasq-tftp[53]: sent /tftpboot/75a721db/overlays/overlay_map.dtb to 192.168.2.37
Mar  2 12:54:53 dnsmasq-tftp[53]: unsupported request from 192.168.2.37
Mar  2 12:54:53 dnsmasq-tftp[53]: error 0 Early terminate received from 192.168.2.37
Mar  2 12:54:53 dnsmasq-tftp[53]: failed sending /tftpboot/75a721db/config.txt to 192.168.2.37
Mar  2 12:54:53 dnsmasq-tftp[53]: unsupported request from 192.168.2.37
Mar  2 12:54:53 dnsmasq-tftp[53]: file /tftpboot/75a721db/armstub8-32-gic.bin not found for 192.168.2.37

thank you for supporting

[Edit]

user pihole can access files
tested with sudo -u pihole cat cmdline.txt

Schnabulator · March 2, 2025, 6:09pm

As a workaround i set up another dnsmasq container for tftp&pxe.
DHCP BOOTP&PXE metrics shows 0 even if some client boots from the new tftp container.

TFTP dnsmasq 2.90

[Unit]
Description=tftp container
Wants=network-online.target
After=network-online.target nss-lookup.target

[Container]
Image=docker.io/dockurr/dnsmasq
ContainerName=tftp
HostName=tftp.ohs.lan
IP=192.168.2.248
Network=macvlan.network
AddCapability=CAP_NET_ADMIN CAP_NET_RAW
AutoUpdate=registry

Volume=/srv/container/tftp/dnsmasq.conf:/etc/dnsmasq.conf
Volume=/srv/container/tftp/etc-dnsmasq.d:/etc/dnsmasq.d
Volume=/srv/tftpboot:/tftpboot

Environment=TZ=Europe/Berlin

[Service]
Restart=always
TimeoutStartSec=900

[Install]
WantedBy=default.target

TFTP dnsmasq.conf

port=0
dhcp-range=192.168.2.0,proxy,255.255.255.0
enable-tftp
tftp-root=/tftpboot
pxe-service=0,"Raspberry Pi Boot"

Greetings

DL6ER · March 3, 2025, 11:23am

More info on this here:

github.com/pi-hole/FTL

dnsmasq tftp's 'get' function reports "operation not supported"

opened 02:16AM - 26 Feb 25 UTC

antbricks

dnsmasq bug

### Versions - Pi-hole: v6.0.4 - AdminLTE: v6.0.1 - FTL: v6.0.2 ### Platfor…m - OS and version: Debian - Platform: Raspberry Pi 3b+ ### Expected behavior dnsmasq's tftp function can serve a file ### Actual behavior / bug After upgrade, dnsmasq's tftp server reports error on 'get' requests. This worked before the upgrade to 6.0.4, and I used it in some home automation scripts for several years. kevin@pihole:~ $ atftp localhost tftp> get entry_file tftp: error received from server \<unsupported request from ::1\> tftp: aborting tftp> ### Steps to reproduce created /etc/dnsmasq.d/07-tftp.conf with the following contents: enable-tftp tftp-root=/srv/tftp tftp-no-blocksize #(this option made no difference, but I tried it just in case) in /etc/dnsmasq.conf, uncomment the line: conf-dir=/etc/dnsmasq.d run 'sudo service restart pihole-FTL' execute a tftp transfer of a file ("entry_file" in this example) (I installed atftp locally to rule out external network variables, but the resulting failure is identical externally) antbricks@pihole:~ $ atftp localhost tftp> get entry_file tftp: error received from server \<unsupported request from ::1\> tftp: aborting tftp> ## Debug Token - URL: ### Screenshots _If applicable, add screenshots to help explain your problem._ ### Additional context This used to work reliably. I can run pihole -d if that helps, just let me know.

You could try

sudo pihole checkout ftl update/dnsmasq

to see if this restores normal operation for you. After the next release (probably v6.0.4), you should go back to master using

sudo pihole checkout ftl master