They should, how does your PXE configuration look like? Note that, for PXE, it should contain pxe-service=... or pxe-prompt=... config lines. If you merely offer TFTP and use dhcp-boot to instruct the clients to download and execute a file, this is not really PXE but just "guided booting". Such a setup wouldn't be counted as PXE.
Easiest would be defining log-dhcp (if you haven't already) and then check /var/log/pihole/pihole.log.
enable-tftp
tftp-root=/media/pi/rootfs/netboot
pxe-prompt="Press Esc To Cancel Network Boot", 2
pxe-service=x86PC,"PXELINUX (BIOS)",bios/pxelinux
pxe-service=x86-64_EFI,"PXELINUX (EFI)",efi64/ipxe.efi
pxe-service=BC_EFI, "Boot UEFI PXE-BC", efi64/ipxe.efi
pxe-service=X86-64_EFI, "Boot UEFI PXE-64", efi64/ipxe.efi
the client received the ipxe script but the number did not increase
Dec 5 21:05:04 dnsmasq-dhcp[52]: 272308015 PXE(eth0) 192.168.1.100
Oh, yes, I think you just have found a bug in dnsmasq not counting certain PXE boots here. We'll report this upstream to get it fixed!
thank you for understanding, I know I don't word things the best way sometimes
also sorry for not being patient earlier in this thread
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
The bugfix has been accepted upstream and is available in the bleeding-edge branch update/dnsmasq. Eventually, it will enter the development branch.