• I have been all the way through the troubleshooting wiki to no avail.

    I am able to tftp via windows and linux to get undionly.kpxe

    Here is from the packet capture I took:
    alt text

    Any thoughts?

  • Moderator

    @Wayne-Workman That’s it. Thanks heaps for finding this! I thought I’d searched for \003 but obviously I didn’t - not properly at least.

    You recommended to use undionly.kkpxe as the “quick fix”.

    That’s not the whole truth I’m afraid! As it does not load a binary from the TFTP you need to use other methods like USB booting (rom-o-matic.eu, settings in the wiki but output format iso/usb). Or you could burn iPXE into the NIC ROM (haven’t done this myself yet so I cannot give any instructions). Why I did recommend undionly.kkpxe is because there is a known issue with a particular realtek NIC. As the OP didn’t let us know any machine or NIC details I am not sure if this is the same one. But I guess this is a very rare issue. So possibly it’e exactly the same NIC.

  • @Sebastian-Roth I searched for \003 and found this: https://forums.fogproject.org/topic/5984/file-not-found

    You recommended to use undionly.kkpxe as the “quick fix”.

  • Moderator

    @Chris-Kuhn Definitely the machine / NIC model would be valuable information. Looking at this again and again I am almost sure that I have seen this very strange behavior reported by another user here in the forums some month ago already. But whatever search query I try I just cannot find it anymore. If I remember correctly the client sending two requests is quite normal. You will see this first aborted try in the server logs as well. This is because first wants to see if it can get the file in one go. The server reports back the (t)size. While the client now sees that this is definitely too much to be transfered in one big blob it aborts the transfer and sends a new request to receive the file in blocks of 1456 bytes.

    The only problem is that on the second request it asks for a different filename \003 (instead of undionly.kpxe which does not make any sense! Maybe one of the other FOGers does remember this and can find it in the forums. I am sure I’ve seen this before. If I remember correctly there was no easy solution to this. You could add a PCI network card to boot from or use USB NIC. Or boot this PC from a iPXE USB stick.

  • Moderator

    Lets collect some background information here.

    What version of fog (from the cloud on the management web gui)?
    What is the target computer you are trying to pxe boot?
    Is the fog server and target computer on the same subnet? I’m finding it interesting the pxe boot server and target device have the same 4th octet yet the 3rd octet is different. Makes me suspect there is a subnet difference.
    Do you see any errors on the linux server side as reported by tftp?
    Is the target computer in uefi mode or bios?