UEFI PXE Boot how to do it?



  • Hi,

    i really would also like to have the ability to boot into fog menu with UEFI enabled, for this i read that articel:
    https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy

    Since we have a Server 2012 i did the changes from the wiki article:

    alt text

    alt text

    alt text

    alt text

    This is all i did, i was wondering that Option 66 should not be filled with the fog’s server ip?
    I tried UEFI PXE booting but it doesn’t work, anyone booting via UEFI or have any ideas?

    Is ipxe.efi available in fog by default?

    @Tom-Elliott @george1421 @Wayne-Workman

    Regards X23


  • Moderator

    @x23piracy said in [SOLVED] UEFI PXE Boot how to do it?:

    Is there an overview about the efi files, what they support and so on?

    Yes:
    https://wiki.fogproject.org/wiki/index.php?title=Filename_Information


  • Moderator

    @x23piracy Ah, I see, I thought you were trying to boot UEFI, my bad.



  • @Quazz i removed all the filters except for 7 and 9 and legacy is working again i think the mistake was to add 0 for the filter because 0 is legacy and i override undi…with ipxe.efi

    Regards X23


  • Moderator

    @x23piracy snponly is similar to undionly in that they try to use the included drivers on the NIC itself (as far as I know), but this generally doesn’t work as well for UEFI boot as it does legacy.

    ipxe (whether .efi or .kpxe) include all of the NIC drivers available and should thus be able to boot just about anything, but in practice that’s not necessarily the case. They’re about 8 times bigger in filesize, though.

    Then you have some vendor specific files like the realtek and intel ones. You also have backdated ones (7156) because of changes to IPXE and incompatibility with certain hardware.

    tl;dr It’s more of a try some and see if it works



  • @Quazz said in [SOLVED] UEFI PXE Boot how to do it?:

    @x23piracy Looks like the NIC on that one doesn’t support the size of the bootfile.

    Try snponly.efi , it’s smaller.

    Is there an overview about the efi files, what they support and so on?
    I really know nothing about it :D

    Regards X23


  • Moderator

    @x23piracy Looks like the NIC on that one doesn’t support the size of the bootfile.

    Try snponly.efi , it’s smaller.



  • Hi,

    i cheered too soon, when i now try to boot legacy i get:

    alt text

    When i disable the DHCP filter rule for UEFI legacy is working again.

    Is this may caused because i created a filter rule from 00000 up to 00009?

    Regards X23



  • @Wayne-Workman @george1421 hey no beef :D i already had bios booting enabled 66 & 67 since i only tried 00007 with uefi boot while having not filled the filter option 66 i am sure wayne is may right, have to remove the 66 to test this.

    Regards X23


  • Moderator

    @george1421 said in UEFI PXE Boot how to do it?:

    If the wiki would have had that this mentioned this thread would not exist

    It does, at the very top:

    “The below method assumes that your normal Scope options 066 and 067 are already setup for BIOS based network booting.”


  • Moderator

    @Wayne-Workman said in UEFI PXE Boot how to do it?:

    @george1421 said in UEFI PXE Boot how to do it?:

    I agree if the wiki is not clear we should revise it to include a mention of be sure to set the dhcp option 66.

    It’s not necessary if the Windows DHCP server’s defaults are already configured for BIOS systems.

    Well if someone was setting up a dhcp server from scratch then the dhcp option 66 might not be set. I think its not a bad idea to at least mention “Hey don’t forget to set dhcp option 66 to point to the ip address of your fog server”. If the wiki would have had that this mentioned this thread would not exist. Not throwing shade your way, as they young kids say. It is what it is.


  • Moderator

    @x23piracy said in UEFI PXE Boot how to do it?:

    Got it booting over PXE :) i just created all the entrys from 0 to 9 and it works.

    This means your device you were booting wasn’t the type 00007, but was some other UEFI architecture.


  • Moderator

    @george1421 said in UEFI PXE Boot how to do it?:

    I agree if the wiki is not clear we should revise it to include a mention of be sure to set the dhcp option 66.

    It’s not necessary if the Windows DHCP server’s defaults are already configured for BIOS systems.


  • Moderator

    @george1421 said in UEFI PXE Boot how to do it?:

    The instructions above are only for the dynamic part of dhcp option 67.

    This setup assumes you have option 066 and 067 defaulted for BIOS. The filter would only change option 067, because option 066 is already set and correct.

    These filters are only changing what is given for 067. The other settings for everything else are still given as normal, like option 066.

    This is how I’ve setup many 2012 DHCP servers.



  • Got it booting over PXE :) i just created all the entrys from 0 to 9 and it works.
    UEFI PXE booting takes more time while getting devices ready screen stucks 10-15 seconds before proceed to menu but it works :D great.

    @george1421 you are absolutely right, getting things work is not understanding what things are doing, i am willing to learn more about UEFI booting.

    Regards X23


  • Moderator

    @x23piracy Yes you will (might) need the others depending on the hardware you are tying to boot. The pcap will tell you what the client is saying. I still think its worth the time for you to learn this part to debug pxe booting. But I also understand that it will take a little time to setup.

    I agree if the wiki is not clear we should revise it to include a mention of be sure to set the dhcp option 66.

    We are here is you need help.



  • @george1421 said in UEFI PXE Boot how to do it?:

    The instructions above are only for the dynamic part of dhcp option 67. You still must supply dhcp option 66 which should be the ip address of your FOG server.

    Hi George thank you for the answer, well if 66 is still needed then this is missing in the wiki article and should be added:

    alt text

    Before i will do all the work i will also add all the other efi options, 00006, 00008 and so on…

    Regards X23


  • Moderator

    The instructions above are only for the dynamic part of dhcp option 67. You still must supply dhcp option 66 which should be the ip address of your FOG server.

    If you have everything setup and if its still not working then I suggest a test.

    Place the fog server, dhcp server and test target computer in the same subnet. This is only for a test. We need to capture the network packets of the dhcp booting process. This will tell us 1) the filters you created are working as intended, 2) what is really going down your network wire.

    Please do the following once all three are on the same subnet (broadcast domain):

    1. Install tcpdump on your FOG server
    2. Install wireshark on a windows computer (you will only use this to review the pcap file created via tcpdump)
    3. Start tcpdump with this command on your fog server tcpdump -w output.pcap port 67 or port 68 or port 69 or port 4011
    4. Now pxe boot your target computer until it errors.
    5. Press Control-C to stop the tcpdump program
    6. Transfer the pcap file to your windows computer to review with wireshark (winscp or pscp will do this from the windows side).
    7. Upload the pcap to the forum so we can review it with you.

    Just be aware there are several different types of uefi systems you may have to create different filters than just arch 0007. The pcap will tell the truth of what is needed.


Log in to reply
 

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.