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

2 Error in iPXE (time out and sand device)

Scheduled Pinned Locked Moved Unsolved
FOG Problems
2
28
5.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.
  • F
    FrancoDin
    last edited by FrancoDin Oct 29, 2018, 7:48 AM Oct 29, 2018, 1:36 PM

    Hello, I cant figure out how to solve this, I spend a while now. The server ip is 10.0.0.72, maybe the error is because its says that the DHCP IP is .72?, I dont knwo to much about networking, if so how to change it?

    Some times i get this error:
    0_1540819908685_Sin nombre.png
    And some times this one
    0_1540820139562_sad.png

    1 Reply Last reply Reply Quote 0
    • G
      george1421 Moderator
      last edited by george1421 Oct 29, 2018, 8:27 AM Oct 29, 2018, 2:26 PM

      My initial reaction is that you have 2 dhcp servers running that is confusing the pxe booting client.

      So lets get some background data here.

      1. What device is your dhcp server for the 10.0.x.x subnet? (that’s a pretty big subnet mask for a single subnet (!!) )

      2. What device is 10.0.0.3 (I’m suspecting a soho/home router)

      3. Your fog server is at 10.0.0.72?

      FWIW: Each error message picture indicates a different error. But combined they give us a better picture of the problem.

      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!

      F 1 Reply Last reply Oct 29, 2018, 2:34 PM Reply Quote 0
      • F
        FrancoDin @george1421
        last edited by FrancoDin Oct 29, 2018, 8:34 AM Oct 29, 2018, 2:34 PM

        @george1421
        Thank you for answering.
        1-Its a PC whit Linux Mint 17.3 64 bits Cinammon
        2- Router Mikrotik
        3- Yes, that is the IP where the server is

        G 1 Reply Last reply Oct 29, 2018, 2:54 PM Reply Quote 0
        • G
          george1421 Moderator @FrancoDin
          last edited by Oct 29, 2018, 2:54 PM

          @FrancoDin said in 2 Error in iPXE (time out and sand device):

          1-Its a PC whit Linux Mint 17.3 64 bits Cinammon
          2- Router Mikrotik

          So do you have FOG configured as a dhcp server AND your router (mikrotik) is also configured for DHCP?

          If that is the case then I can see why its not working.

          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!

          F 1 Reply Last reply Oct 29, 2018, 2:57 PM Reply Quote 0
          • F
            FrancoDin @george1421
            last edited by Oct 29, 2018, 2:57 PM

            @george1421

            I should stop the DHCP in the server? so it works?

            G 1 Reply Last reply Oct 29, 2018, 3:04 PM Reply Quote 0
            • G
              george1421 Moderator @FrancoDin
              last edited by Oct 29, 2018, 3:04 PM

              @FrancoDin The best path to take is disable dhcp server on your FOG server.

              I’m a RHEL guy so I’m guessing at these commands.

              # stop the isc-dhcp server
              sudo service isc-dhcp-server stop 
              # Uninstall isc-dhcp server
              sudo apt-get remove isc-dhcp-server
              

              The next step is to update your router to add the boot file settings into your router. From the second error message it appears the router is selecting itself as the boot server.

              What you need to do is update dhcp option 66 {next-server} on your router to point to your FOG server’s IP address and then update dhcp option 67 {boot-file} to undionly.kpxe for bios based systems or ipxe.efi for uefi based systems.

              If your router doesn’t support netbooting / pxe booting then we can move on to plan B. Either plan required that you stop and uninistall the isc-dhcp server from your fog server.

              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!

              F 1 Reply Last reply Oct 30, 2018, 1:02 PM Reply Quote 0
              • F
                FrancoDin @george1421
                last edited by FrancoDin Oct 30, 2018, 7:05 AM Oct 30, 2018, 1:02 PM

                @george1421 I cant access to the router, so lest go whit plan B

                (I will try dnsmasq in the server)

                G 1 Reply Last reply Oct 30, 2018, 1:12 PM Reply Quote 0
                • G
                  george1421 Moderator @FrancoDin
                  last edited by george1421 Oct 30, 2018, 7:15 AM Oct 30, 2018, 1:12 PM

                  @FrancoDin Ok then for plan b.

                  I want you to install the DNSMASQ service on your FOG server.
                  sudo apt-get install dnsmasq

                  We will use dnsmasq to “override” what your dhcp server is telling the clients to boot from.

                  Once dnsmasq is installed inspect /etc/dnsmasq.d directory. There shouldn’t be any files in that directory. We need to create a new one called ltsp.conf.

                  Paste the following into that file

                  # Don't function as a DNS server:
                  port=0
                  
                  # Log lots of extra information about DHCP transactions.
                  log-dhcp
                  
                  # Set the root directory for files available via FTP.
                  tftp-root=/tftpboot
                  
                  # The boot filename, Server name, Server Ip Address
                  dhcp-boot=undionly.kpxe,,<fog_server_IP>
                  
                  # Disable re-use of the DHCP servername and filename fields as extra
                  # option space. That's to avoid confusing some old or broken DHCP clients.
                  dhcp-no-override
                  
                  # inspect the vendor class string and match the text to set the tag
                  dhcp-vendorclass=BIOS,PXEClient:Arch:00000
                  dhcp-vendorclass=UEFI32,PXEClient:Arch:00006
                  dhcp-vendorclass=UEFI,PXEClient:Arch:00007
                  dhcp-vendorclass=UEFI64,PXEClient:Arch:00009
                  
                  # Set the boot file name based on the matching tag from the vendor class (above)
                  dhcp-boot=net:UEFI32,i386-efi/ipxe.efi,,<fog_server_IP>
                  dhcp-boot=net:UEFI,ipxe.efi,,<fog_server_IP>
                  dhcp-boot=net:UEFI64,ipxe.efi,,<fog_server_IP>
                  
                  # PXE menu.  The first part is the text displayed to the user.  The second is the timeout, in seconds.
                  pxe-prompt="Booting FOG Client", 1
                  
                  # The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,
                  # Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI
                  # This option is first and will be the default if there is no input from the user.
                  pxe-service=X86PC, "Boot to FOG", undionly.kpxe
                  pxe-service=X86-64_EFI, "Boot to FOG UEFI", ipxe.efi
                  pxe-service=BC_EFI, "Boot to FOG UEFI PXE-BC", ipxe.efi
                  
                  dhcp-range=<fog_server_ip>,proxy
                  

                  Don’t forget to replace <fog_server_ip> in the above text with the IP address of your fog server. The tag appears many times.

                  Then issue the following commands to:

                  # enable dnsmasq to start every time
                  sudo systemctl enable dnsmasq
                  # restart the dnsmasq service to pick up the new config files
                  sudo systemctl restart dnsmasq
                  

                  Make sure before you install dnsmaq you already disabled and remove isc-dhcp server from the previous post. Both services use the same network ports.

                  pxe boot your target computer and see if you can get to the FOG iPXE menu.

                  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!

                  F 1 Reply Last reply Oct 30, 2018, 1:56 PM Reply Quote 0
                  • F
                    FrancoDin @george1421
                    last edited by Oct 30, 2018, 1:56 PM

                    @george1421

                    I did as you say, reinstall complety fog, and remove dhcp from the server
                    0_1540907625405_errordeboot.png

                    G 1 Reply Last reply Oct 30, 2018, 1:58 PM Reply Quote 0
                    • G
                      george1421 Moderator @FrancoDin
                      last edited by george1421 Oct 30, 2018, 8:00 AM Oct 30, 2018, 1:58 PM

                      @FrancoDin Can you confirm that dnsmasq is running in memory.

                      sudo ps aux|grep dnsmasq

                      I’m also not seeing it pick up a dhcp address. Is the target computer on the same subnet as your dhcp server? Your Mikrotik is your normal dhcp server right?

                      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!

                      F 1 Reply Last reply Oct 30, 2018, 2:05 PM Reply Quote 0
                      • F
                        FrancoDin @george1421
                        last edited by Oct 30, 2018, 2:05 PM

                        @george1421

                        0_1540908314508_ram.png

                        The target computer is in the same subnet as the dhcp server, and yes the mikrotik is the normal dhcp server.

                        G 2 Replies Last reply Oct 30, 2018, 2:07 PM Reply Quote 0
                        • G
                          george1421 Moderator @FrancoDin
                          last edited by Oct 30, 2018, 2:07 PM

                          @FrancoDin well from the screen shot I don’t see dnsmasq running.

                          sudo systemctl start dnsmasq

                          then make sure it starts every reboot
                          sudo systemctl enable dnsmasq

                          Also lets capture the version of dnsmasq to make sure its 2.76 or newer
                          sudo dnsmasq -v

                          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!

                          1 Reply Last reply Reply Quote 0
                          • G
                            george1421 Moderator @FrancoDin
                            last edited by george1421 Oct 30, 2018, 8:11 AM Oct 30, 2018, 2:09 PM

                            @FrancoDin I also see from the screen shot you are editing the /etc/dnsmasq.conf file. This file should not be adjusted. It should have a reference to load any files in the /etc/dnsmasq.d directory. The dnsmasq.d directory is where the ltsp.conf file goes.

                            Also, is your FOG server running on virtual box? If so, you need to ensure you are using a bridged network adapter for both the fog server and pxe booting client. Using a nat network adapter will cause you pains trying to get things to pxe boot.

                            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!

                            F 1 Reply Last reply Oct 30, 2018, 2:20 PM Reply Quote 0
                            • F
                              FrancoDin @george1421
                              last edited by FrancoDin Oct 30, 2018, 8:26 AM Oct 30, 2018, 2:20 PM

                              @george1421

                              0_1540909005732_jobdns.png

                              So its fail at running, and the version of dnsmasq is 2.75
                              I am editing that file whit nano, because I am using Putty, and I cant coppy paste files in the ubuntu server at the moment. The fog isent runing in virtual box.

                              I just realized the error is in spanish, sorry my bad, that red line says:
                              Rank of dhcp not valid, in line 26 of lstp.conf
                              Fail at the start

                              0_1540909587748_dpfconfig.png

                              G 1 Reply Last reply Oct 30, 2018, 2:36 PM Reply Quote 0
                              • G
                                george1421 Moderator @FrancoDin
                                last edited by Oct 30, 2018, 2:36 PM

                                @FrancoDin well I can see from your screen shot that you have extra text in the config file. <10.0.0.2> should be 10.0.0.2 (assuming that 10.0.0.2 is your FOG server’s IP)

                                PS: Look at the FOG Forum chat bubble for additional hits

                                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!

                                F 1 Reply Last reply Oct 30, 2018, 2:53 PM Reply Quote 0
                                • F
                                  FrancoDin @george1421
                                  last edited by Oct 30, 2018, 2:53 PM

                                  @george1421

                                  Now it works, but when I go to the PC and boot:

                                  Auto-Select:
                                  Boot to FOG

                                  BOOT Server ip:10.0.0.2
                                  TFTP.
                                  PXE-T01: File not Found
                                  Pxe-E3B: TFTP Error - File not found
                                  PXE-M0F: Exiting intel PXE ROm.
                                  Fatal: Could not read from the boot medium

                                  Also I see that maybe there is a problem in the IP, because there is another device whit the ip 10.0.0.2 so I will fix that tomorrow and tell you what happen

                                  G 1 Reply Last reply Oct 30, 2018, 6:55 PM Reply Quote 1
                                  • G
                                    george1421 Moderator @FrancoDin
                                    last edited by Oct 30, 2018, 6:55 PM

                                    @FrancoDin said in 2 Error in iPXE (time out and sand device):

                                    BOOT Server ip:10.0.0.2

                                    fwiw: In a previous post you had the fog server at 10.0.0.27

                                    Also the fog server must have a static IP address or one created via dhcp reservation. FOG does not fog support servers that are configured to use dhcp. Your fog deployment will break if the IP address of your fog server changes after FOG is installed.

                                    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!

                                    F 1 Reply Last reply Oct 31, 2018, 12:35 PM Reply Quote 0
                                    • F
                                      FrancoDin @george1421
                                      last edited by Oct 31, 2018, 12:35 PM

                                      @george1421

                                      Yhep, that broke the fog.
                                      But I managed it, to update the dnsmasq, after manually instaling 80 packes from https://www.debian.org/distrib/packages , that seems to work for the pxe boot error, but it direct me to my previous IP, so I will reinstall ubuntu server, and try all again, because I try to reinstall fog, but have a problem deleting it and when try to reinstall its gets an error instalin packges,(maybe I broke that aswell).

                                      G 1 Reply Last reply Oct 31, 2018, 12:46 PM Reply Quote 0
                                      • G
                                        george1421 Moderator @FrancoDin
                                        last edited by Oct 31, 2018, 12:46 PM

                                        @FrancoDin Well if you want to go through the process again, just make sure that the FOG server has a static IP address before you install FOG. Just install a normal FOG server without dhcp services.

                                        Then install dnsmasq and use the config file I provided. (hint: if you are using putty to connect to your fog server, you can use copy and paste to copy the text file into nano and ltsp.conf easily).

                                        Once dnsmasq is setup correctly using my config file it should work. If not then we will use the fog server and tcpdump to capture what is going wrong with the pxe booting process. We are far from just giving up. This WILL work.

                                        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!

                                        F 1 Reply Last reply Oct 31, 2018, 2:14 PM Reply Quote 0
                                        • F
                                          FrancoDin @george1421
                                          last edited by FrancoDin Oct 31, 2018, 8:24 AM Oct 31, 2018, 2:14 PM

                                          @george1421

                                          Thank you a Lot, all working now.
                                          Just one think, I follow this guide (https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images/9) to add Linux Mint, to the fog menu. But when I boot from there Its says “Connection time out”, its has anything to deal whit dnsmasq?

                                          Also, in the parameters:
                                          kernel tftp://${fog-ip}/mint/18.1/vmlinu
                                          Should go like this
                                          kernel tftp://${10.0.0.7}/mint/18.1/vmlinuz
                                          or
                                          kernel tftp://$10.0.0.7/mint/18.1/vmlinuz
                                          in the 3 different times its appears.

                                          G F 3 Replies Last reply Oct 31, 2018, 2:31 PM Reply Quote 0
                                          • 1
                                          • 2
                                          • 1 / 2
                                          1 / 2
                                          • First post
                                            16/28
                                            Last post

                                          204

                                          Online

                                          12.0k

                                          Users

                                          17.3k

                                          Topics

                                          155.2k

                                          Posts
                                          Copyright © 2012-2024 FOG Project