I've also running DHCP and TFTP on different machines. My DHCP is an Raspberry B1 and all the other services like TFTP, NFS and so on are running on an X86-PC.
The relevant part of my dnsmasq-config is:
Code: Select all
dhcp-option-force=net:rpi-boot,43,"Raspberry Pi Boot"
# following not needed, RPi always requests 'bootcode.bin'
is the tag, to give the options below only to the raspberrys with the corresponding MAC-addresses. 192.168.0.100
is my TFTP.
But the internal boot-ROM of an RPi3 seems to be very tricky?
1. NetBooting any X86-machine works at 100% with my setup. Of course they refer not to 'bootcode.bin', they use 'pxelinux.0' or such.
2. NetBooting a RPi2 with an nearly empty SD-card (only bootcode.bin from NEXT-branch on it) works at 100% with my setup.
3. NetBooting a RPi3 with an nearly empty SD-card (only bootcode.bin from NEXT-branch on it) works at 100% with my setup.
4. NetBooting a RPi3 without SD-card (by using the internal boot-ROM) works at ~50% with my setup.
I cannot determine before if it works or not in this last case. Sometimes no DHCPDISCOVER is seen, sometimes I see this, but nothing is pulled via TFTP, sometime it works. I've also tried several switches, but no relation here ... But I think, there is no chance, to reflash the boot-ROM with better firmware at home? (These last sentences only refer to point 4.)