• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

PXE Boot - NBP file downloaded successfullly

Scheduled Pinned Locked Moved Solved
FOG Problems
2
6
4.5k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • N
    noobFogger
    last edited by Dec 30, 2021, 6:33 PM

    Hello,

    i have a problem with the pxe boot.

    I installed the FOG Server 1.5.9 on an ubuntu desktop 20.04 LTS. The Ubuntu desktop is an hyper-v VM.

    The Fogserver installation is completed and fog management gui is working.

    i tried different dhcp settings, but i think this settings are the right one:
    66 = [ip of the fogserver]
    67 = ipxe.efi

    i choosed ipxe.efi, because my clients run with UEFI and not with BIOS - is that correct or can i try other boot files?

    i recorded an video what happens, when i try to start an pxe boot with one of my clients

    Video:
    https://drive.google.com/file/d/14Qfa1foJE9ek5HaQMIw5HwpElR-vHwAs/view?usp=sharing

    what does it mean, i hope you can help me
    where is my mistake

    G 1 Reply Last reply Dec 30, 2021, 6:36 PM Reply Quote 0
    • G
      george1421 Moderator @noobFogger
      last edited by Jan 3, 2022, 11:36 AM

      @noobfogger Well this is a bit different conditions than your original post. iPXE is being loaded now but when iPXE starts it issues a second dhcp query to pick up its IP address and loads dhcp option 66 once again to find the FOG server. If it fails to get dhcp option 66 it will prompt for the FOG server IP address.

      This is still telling me there is a second dhcp server on this subnet. There is a way to find out. Take a third computer and load wirehark on it. Use this exact capture filter port 67 or port 68 Start wireshark and then pxe boot until you get the failure. Stop wireshark and then inspect the captured packets.

      In the top section you should see a DISCOVER packet sent from the pxe booting computer. Then you should see one or more OFFER packets. These OFFER packets will be from each dhcp server that hears a DISCOVER packet. In your case you should only hear an OFFER from the FOG server’s IP address. I’m suspecting you will hear a second OFFER. The response sequence is DISCOVER, OFFER, REQUEST, ACK/NACK. If the target computer gets to the prompting for FOG server IP address question you should see two complete sequences of the DORA process. If you are getting the question that second sequence is failing. If you can’t figure out the pcap, upload it to a file share site and share it as you have the videos and I will take a look at it for you. But it should be obvious if you have a second OFFER in response to a DISCOVER something is not as we expect it to be.

      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

      N 1 Reply Last reply Jan 3, 2022, 7:06 PM Reply Quote 1
      • G
        george1421 Moderator @noobFogger
        last edited by Dec 30, 2021, 6:36 PM

        @noobfogger Make sure you have secure boot disabled in the firmware. You have the dhcp settings configured correctly for uefi boot. It appears its downloading the ipxe.efi file but its not able to run it because of secure boot (guess). If it wasn’t getting the file you would see other error messages.

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

        N 2 Replies Last reply Dec 30, 2021, 7:19 PM Reply Quote 1
        • N
          noobFogger @george1421
          last edited by Dec 30, 2021, 7:19 PM

          @george1421 thanks for your very fast reply, i will test it the next days and will give you a update

          1 Reply Last reply Reply Quote 0
          • N
            noobFogger @george1421
            last edited by noobFogger Jan 3, 2022, 5:18 AM Jan 3, 2022, 10:25 AM

            @george1421 i tried to boot with disabled secure boot but it still dont work

            I have to enter an tftp server, but the ip address of the fogserver dont work

            Error message
            https://drive.google.com/file/d/1spnuHIB-mqK4bQrlzOBLCvPjVBvtXSFo/view?usp=drivesdk

            The client and the fogserver are in the same subnet.

            I tried it with different pcs and with one VM and everywhere the same message.

            I checked with systemctl status isc-dhcp-server.service the status of the dhcp on the fogserver and there is no secound dhcp running - the only dhcp in my network is an windows server with the correct 66 and 67 informatiions

            G 1 Reply Last reply Jan 3, 2022, 11:36 AM Reply Quote 0
            • G
              george1421 Moderator @noobFogger
              last edited by Jan 3, 2022, 11:36 AM

              @noobfogger Well this is a bit different conditions than your original post. iPXE is being loaded now but when iPXE starts it issues a second dhcp query to pick up its IP address and loads dhcp option 66 once again to find the FOG server. If it fails to get dhcp option 66 it will prompt for the FOG server IP address.

              This is still telling me there is a second dhcp server on this subnet. There is a way to find out. Take a third computer and load wirehark on it. Use this exact capture filter port 67 or port 68 Start wireshark and then pxe boot until you get the failure. Stop wireshark and then inspect the captured packets.

              In the top section you should see a DISCOVER packet sent from the pxe booting computer. Then you should see one or more OFFER packets. These OFFER packets will be from each dhcp server that hears a DISCOVER packet. In your case you should only hear an OFFER from the FOG server’s IP address. I’m suspecting you will hear a second OFFER. The response sequence is DISCOVER, OFFER, REQUEST, ACK/NACK. If the target computer gets to the prompting for FOG server IP address question you should see two complete sequences of the DORA process. If you are getting the question that second sequence is failing. If you can’t figure out the pcap, upload it to a file share site and share it as you have the videos and I will take a look at it for you. But it should be obvious if you have a second OFFER in response to a DISCOVER something is not as we expect it to be.

              Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

              N 1 Reply Last reply Jan 3, 2022, 7:06 PM Reply Quote 1
              • N
                noobFogger @george1421
                last edited by Jan 3, 2022, 7:06 PM

                @george1421 I found a device that was running a second DHCP … thanks for your help, the capture and deployment works now

                1 Reply Last reply Reply Quote 1
                • 1 / 1
                1 / 1
                • First post
                  5/6
                  Last post

                275

                Online

                12.0k

                Users

                17.3k

                Topics

                155.2k

                Posts
                Copyright © 2012-2024 FOG Project