What version of FOG?
The 500 error is from apache, you might want to inspect the apache error logs in /var/logs.
If you had ubuntu installed, I might think that ubuntu has applied a patch and secured the database, but you are using fedora so that’s probably not the issue. But again, check the apache error logs first.
@InfoOverload said in iPXE/tftp error - Extra chars in the RRQ:
working through some of the troubleshooting/ I decided to look at the dhcpd.conf a little closer
This is what I had - “broken”
Great you figured this out! Not something I’d know from the top of my head and believe me I have done very extensive debugging and use of the Linux DHCP server.
The difference between option bootfile-name and filename as far as I understand it, is that the later actually puts the filename into the answer body vs. the other one adds it as a option later in the DHCP packet. Take a look at the DHCP packets in wireshark and you’ll understand what I mean.
Why some NICs handle the DHCP option properly while other do not - I don’t know. It would be interesting to see if the DHCP server actually sends those malformed names or if it’s the NICs miss-reading it. I suppose it’s some kind of missing “end of string” character that makes some NICs read beyond the actual filename in the DHCP option… just guessing here.
Upload a PCAP and we can figure this out. :-)