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

    FOG .33b PXE Boot woes

    Scheduled Pinned Locked Moved
    FOG Problems
    7
    53
    22.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.
    • Jaymes DriverJ
      Jaymes Driver Developer
      last edited by

      Alright here is a working ltsp.conf for ipxe, delete those symlinks, make sure pxelinux.0 does not exist rename it, also rename or delete your pxelinux.cfg. Make sure your undionly.kpxe is in the root of your tftpboot folder.

      Edit your ltsp.conf to look like the following

      [code]

      Don’t function as a DNS server:

      port=0

      Log lots of extra information about DHCP transactions.

      log-dhcp

      Dnsmasq can also function as a TFTP server. You may uninstall

      tftpd-hpa if you like, and uncomment the next line:

      enable-tftp

      Set the root directory for files available via FTP.

      tftp-root=/tftpboot

      The boot filename, Server name, Server Ip Address

      dhcp-boot=undionly.kpxe,x.x.x.x

      rootpath option, for NFS

      #dhcp-option=17,/images

      kill multicast

      #dhcp-option=vendor:PXEClient,6,2b

      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

      PXE menu. The first part is the text displayed to the user. The second is the timeout, in seconds.

      #pxe-prompt=“Press F8 for boot menu”, 3

      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 from network”, pxelinux

      A boot service type of 0 is special, and will abort the

      net boot procedure and continue booting from local media.

      #pxe-service=X86PC, “Boot from local hard disk”, 0

      If an integer boot service type, rather than a basename is given, then the

      PXE client will search for a suitable boot service for that type on the

      network. This search may be done by multicast or broadcast, or direct to a

      server if its IP address is provided.

      pxe-service=x86PC, “Install windows from RIS server”, 1

      This range(s) is for the public interface, where dnsmasq functions

      as a proxy DHCP server providing boot information but no IP leases.

      Any ip in the subnet will do, so you may just put your server NIC ip here.

      Since dnsmasq is not providing true DHCP services, you do not want it

      handing out IP addresses. Just put your servers IP address for the interface

      that is connected to the network on which the FOG clients exist.

      If this setting is incorrect, the dnsmasq may not start, rendering

      your proxyDHCP ineffective.

      dhcp-range=10.0.0.10,proxy

      This range(s) is for the private network on 2-NIC servers,

      where dnsmasq functions as a normal DHCP server, providing IP leases.

      dhcp-range=192.168.0.20,192.168.0.250,8h

      For static client IPs, and only for the private subnets,

      you may put entries like this:

      dhcp-host=00:20:e0:3b:13:af,10.160.31.111,client111,infinite

      [/code]

      Save and restart dnsmasq.

      WARNING TO USERS: My comments are written completely devoid of emotion, do not mistake my concise to the point manner as a personal insult or attack.

      1 Reply Last reply Reply Quote 0
      • P
        Paul Freeman
        last edited by

        Awesome! After making the changes the machines are now able to boot to iPXE. HOWEVER, now it is saying it cannot find /default.ipxe. FOG is set as the owner for everything in the /tftpboot folder so i cant imagine its a permissions problem. Perhaps is there another config elsewhere that needs to be changed?

        [ATTACH=full]665[/ATTACH]

        [url=“/_imported_xf_attachments/0/665_IMG_20140414_120339.jpg?:”]IMG_20140414_120339.jpg[/url]

        1 Reply Last reply Reply Quote 0
        • Tom ElliottT
          Tom Elliott
          last edited by

          Make sure the /tftpboot/default.ipxe file actually exists.

          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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

          Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

          Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

          1 Reply Last reply Reply Quote 0
          • P
            Paul Freeman
            last edited by

            File exists and FOG has permission to use it. The contents are pointing to the IP of the Server. It was set to Net0 so i changed that to net1 as I am using eth1 for the connections but that had no effect.

            This is what my default.ipxe file looks like.
            [CODE]#!ipxe
            chain http://192.168.1.99/fog/service/ipxe/boot.php?mac=${net1/mac}[/CODE]

            1 Reply Last reply Reply Quote 0
            • Tom ElliottT
              Tom Elliott
              last edited by

              net net0/mac is for the client’s network interface, not the FOG Server’s network interface.

              Are you sure 192.168.1.99 is being hosted properly then?

              Can you tftp the default.ipxe file:
              [code]tftp -i 192.168.1.99 get default.ipxe[/code]

              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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

              Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

              Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

              1 Reply Last reply Reply Quote 0
              • P
                Paul Freeman
                last edited by

                I was able to download default.ipxe with that command successfully. I am thinking I will start over on my FOG config using what I have learned with this thread and see where that gets me.

                1 Reply Last reply Reply Quote 0
                • Tom ElliottT
                  Tom Elliott
                  last edited by

                  Okay, I hope all goes well.

                  I don’t know why it’s not pulling the default file, but before you start all over, maybe try restarting the tftpd-hpa service.

                  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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                  Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                  Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                  1 Reply Last reply Reply Quote 0
                  • P
                    Paul Freeman
                    last edited by

                    I had rebooted the server machine completely with the same result. Though when i try to restart the tftpd-hpa service it hangs and does not seem to want to start it again. And after a reboot when trying to restart the service the machine hangs at shutdown. Sounds like I may have other issues anyway. Would sorta make sense, i have been all over the place trying to get this thing to work.

                    1 Reply Last reply Reply Quote 0
                    • Jaymes DriverJ
                      Jaymes Driver Developer
                      last edited by

                      [quote=“Paul Freeman, post: 25459, member: 23545”]I had rebooted the server machine completely with the same result. Though when i try to restart the tftpd-hpa service it hangs and does not seem to want to start it again. And after a reboot when trying to restart the service the machine hangs at shutdown. Sounds like I may have other issues anyway. Would sorta make sense, i have been all over the place trying to get this thing to work.[/quote]

                      I would definitely start fresh. I can confirm these settings work for a linksys router. But if you are in a production environment, adjustments will need to be made. This is the most basic setting a ltsp.conf can have to boot.

                      I updated the wiki.

                      In order to use boot commands you will need to symlink undionly.kpxe to undionly.0

                      [code]
                      cd /tftpboot
                      sudo ln -s undionly.kpxe undionly.0
                      [/code]

                      Then edit your ltsp.conf edit these two lines
                      [code]
                      #pxe-prompt=“Press F8 for boot menu”, 3
                      to
                      pxe-prompt=“Press F8 for boot menu”, 3

                      You may change the number value after we get it working. 0 will instantly boot your first command.

                      #pxe-service=X86PC, “Boot from network”, pxelinux
                      to
                      pxe-service=X86PC, “Boot from network”, undionly.0
                      [/code]

                      WARNING TO USERS: My comments are written completely devoid of emotion, do not mistake my concise to the point manner as a personal insult or attack.

                      1 Reply Last reply Reply Quote 0
                      • P
                        Paul Freeman
                        last edited by

                        Hello again all.

                        I would like to thank you all for your hard work and dedication to the FOG project and all the support you offer everyone and to myself.

                        After seeing that .33 was in RC status I decided to wait for the full release. Now I have a fresh install of 1.01 on linux Mint 16 running in production using Cisco router DHCP on 1 NIC.

                        I have followed the instructions via the WIKI for using DNSMASQ and after completion I was able to get a PC to start to load into iPXE. It had stopped at trying to load /default.ipxe and I was not sure why, so I rebooted the server and now the machines will no longer boot to iPXE. It now stops again at [I]PXE-E32: TFTP open timeout[/I]. I have verified that both TFTPD-HPA and DNSMASQ services are running.

                        I do not understand why it would stop working after a reboot when nothing else has changed.

                        1 Reply Last reply Reply Quote 0
                        • Jaymes DriverJ
                          Jaymes Driver Developer
                          last edited by

                          [quote=“Paul Freeman, post: 28676, member: 23545”]Hello again all.

                          I would like to thank you all for your hard work and dedication to the FOG project and all the support you offer everyone and to myself.

                          After seeing that .33 was in RC status I decided to wait for the full release. Now I have a fresh install of 1.01 on linux Mint 16 running in production using Cisco router DHCP on 1 NIC.

                          I have followed the instructions via the WIKI for using DNSMASQ and after completion I was able to get a PC to start to load into iPXE. It had stopped at trying to load /default.ipxe and I was not sure why, so I rebooted the server and now the machines will no longer boot to iPXE. It now stops again at [I]PXE-E32: TFTP open timeout[/I]. I have verified that both TFTPD-HPA and DNSMASQ services are running.

                          I do not understand why it would stop working after a reboot when nothing else has changed.[/quote]

                          What happens if you restart the services even though they are running?

                          WARNING TO USERS: My comments are written completely devoid of emotion, do not mistake my concise to the point manner as a personal insult or attack.

                          1 Reply Last reply Reply Quote 0
                          • P
                            Paul Freeman
                            last edited by

                            Restarted the service and now it will boot back into iPXE. Now it stops at [I]/default.ipxe… No such file or directory ([url]http://ipxe.org/2d12603b[/url]) [/I]This reads to me like a permissions issue since the file is in the /tftpboot directory.

                            1 Reply Last reply Reply Quote 0
                            • P
                              Paul Freeman
                              last edited by

                              Changed ownership of /tftpboot to fog user and group and restarted the services and no change.

                              1 Reply Last reply Reply Quote 0
                              • JunkhackerJ
                                Junkhacker Developer
                                last edited by

                                can you retrieve undionly.kpxe by tftp from another computer from command line?

                                signature:
                                Junkhacker
                                We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

                                1 Reply Last reply Reply Quote 0
                                • P
                                  Paul Freeman
                                  last edited by

                                  Yes, I am able to retrieve undionly.kpxe and default.ipxe via TFTP.

                                  1 Reply Last reply Reply Quote 0
                                  • JunkhackerJ
                                    Junkhacker Developer
                                    last edited by

                                    can you verify that both the undionly.kpxe and default.ipxe are in the same directory and their permissions are 644

                                    signature:
                                    Junkhacker
                                    We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

                                    1 Reply Last reply Reply Quote 0
                                    • P
                                      Paul Freeman
                                      last edited by

                                      Both files are in the /tftpboot folder and are set to 644. Still throwing the same error. I currently have fog as the owner of the /tftpboot directory, should i change this back to root?

                                      1 Reply Last reply Reply Quote 0
                                      • JunkhackerJ
                                        Junkhacker Developer
                                        last edited by

                                        so long as the file can be read anonymously, ownership doesn’t matter

                                        signature:
                                        Junkhacker
                                        We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

                                        1 Reply Last reply Reply Quote 0
                                        • P
                                          Paul Freeman
                                          last edited by

                                          Good point. Is there another config file somewhere that deals with the path to the default.ipxe? I assume it just looks for it in the /tftpboot directory but perhaps this isnt the case?

                                          1 Reply Last reply Reply Quote 0
                                          • JunkhackerJ
                                            Junkhacker Developer
                                            last edited by

                                            the undionly.kpxe file automatically searches for default.ipxe in the same directory as itself.
                                            changing that setting requires recompiling undionly.kpxe

                                            signature:
                                            Junkhacker
                                            We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

                                            1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 2 / 3
                                            • First post
                                              Last post

                                            153

                                            Online

                                            12.0k

                                            Users

                                            17.3k

                                            Topics

                                            155.2k

                                            Posts
                                            Copyright © 2012-2024 FOG Project