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

    PXE-E53: No boot filename recieved

    Scheduled Pinned Locked Moved Solved
    Windows Problems
    3
    12
    819
    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.
    • S
      Sebastian Roth Moderator
      last edited by

      @weidongyan Please run sudo systemctl status dnsmasq and post output here. As well I may ask you to post the full content of your dnsmasq configuration file.

      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

      W 2 Replies Last reply Reply Quote 0
      • W
        weidongyan @Sebastian Roth
        last edited by

        @Sebastian-Roth Status of dnsmasq:

        ● dnsmasq.service - LSB: DHCP and DNS server
           Loaded: loaded (/etc/init.d/dnsmasq; generated)
           Active: active (exited) since Tue 2019-07-30 16:02:47 EDT; 9min ago
             Docs: man:systemd-sysv-generator(8)
          Process: 4654 ExecStop=/etc/init.d/dnsmasq stop (code=exited, status=0/SUCCESS
          Process: 4655 ExecStart=/etc/init.d/dnsmasq start (code=exited, status=0/SUCCE
        
        Jul 30 16:02:47 genesicadmin-PowerEdge-840 systemd[1]: Starting LSB: DHCP and DN
        Jul 30 16:02:47 genesicadmin-PowerEdge-840 systemd[1]: Started LSB: DHCP and DNS
        

        The content of the configuration:

        # 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,,<192.168.88.40>
        
        # 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,,<192.168.88.40>
        dhcp-boot=net:UEFI,ipxe.efi,,<192.168.88.40>
        dhcp-boot=net:UEFI64,ipxe.efi,,<192.168.88.40>
        
        # 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=<192.168.88.40>,proxy
        
        1 Reply Last reply Reply Quote 0
        • W
          weidongyan @Sebastian Roth
          last edited by

          @Sebastian-Roth I was having trouble with starting dnsmasq service, saying bad dhcp-range which pointed to the end of the configuration was something wrong. I tried to reinstall dnsmasq service and now it is working now. I am not sure if there is some connection between these two problem.

          1 Reply Last reply Reply Quote 0
          • S
            Sebastian Roth Moderator
            last edited by

            @weidongyan said in PXE-E53: No boot filename recieved:

            dhcp-range=<192.168.88.40>,proxy

            Please check your config again. All the places where you have <192.168.88.40> should actually be 192.168.88.40 without the tag characters!!

            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

            george1421G W 2 Replies Last reply Reply Quote 1
            • george1421G
              george1421 Moderator @Sebastian Roth
              last edited by

              @Sebastian-Roth said in PXE-E53: No boot filename recieved:

              Please check your config again. All the places where you have <192.168.88.40> should actually be 192.168.88.40 without the tag characters!!

              +1 That’s exactly the problem.

              There is another tutorial on how to install dnsmasq service here: https://forums.fogproject.org/topic/12796/installing-dnsmasq-on-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!

              W 2 Replies Last reply Reply Quote 0
              • W
                weidongyan @george1421
                last edited by

                @george1421 Hi, George. Unfortunately, I still got the same problem here with that issue fixed. My configuration is like this

                # 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,,192.168.88.40
                
                # 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,,192.168.88.40
                dhcp-boot=net:UEFI,ipxe.efi,,192.168.88.40
                dhcp-boot=net:UEFI64,ipxe.efi,,192.168.88.40
                
                # 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=192.168.88.40,proxy
                
                george1421G 1 Reply Last reply Reply Quote 0
                • W
                  weidongyan @george1421
                  last edited by

                  @george1421 Hi George, it worked!!! After I made update for dnsmasq. I was thinking about that dnsmasq did not use the configuration that I created to run. So I was updating it and it worked. Thank you.

                  1 Reply Last reply Reply Quote 1
                  • george1421G
                    george1421 Moderator @weidongyan
                    last edited by

                    @weidongyan And you have confirmed that dnsmasq is running on the fog server ps aux|grep dnsmasq AND the pxe booting client are on the same subnet?

                    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!

                    W 1 Reply Last reply Reply Quote 0
                    • W
                      weidongyan @Sebastian Roth
                      last edited by

                      @Sebastian-Roth Thank you Sebastian. I got it worked. Thank you so much for your patient help. I really appreciate.

                      1 Reply Last reply Reply Quote 0
                      • W
                        weidongyan @george1421
                        last edited by

                        @george1421 I got some tricky ways to find if dnsmasq is using the configuration that we created. In the directory /etc/dnsmasq.d/, we created the configuration file, but if there is no other file called README, I think dnsmasq did not use the configuration file. But after I updated dnsmasq, there is a new file called README. And it works!!! I am not sure if my thoughts was right. But it got working in my case.

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

                        326

                        Online

                        12.0k

                        Users

                        17.3k

                        Topics

                        155.2k

                        Posts
                        Copyright © 2012-2024 FOG Project