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

    Dell Inspiron 15 7559

    Scheduled Pinned Locked Moved Solved
    Hardware Compatibility
    uefi dnsmasq parallels inspiron 15 7559
    4
    29
    9.0k
    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.
    • george1421G
      george1421 Moderator @Merilious
      last edited by george1421

      @Merilious That is the version you need. Now post your ltsp.conf file and we can take a look at that.

      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
      • M
        Merilious @george1421
        last edited by

        @george1421

        Here’s what I’m currently trying out for my ltsp.conf.

        # 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

# 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
dhcp-match=set:ParallelsEFI,97,00:ef:e3:6d:16:10:6f:46:9d:87:12:5a:12:c2

# Set the boot file name based on the matching tag from the vendor class (above)
dhcp-boot=net:UEFI32,i386-efi/ipxe.efi,,10.200.10.20
dhcp-boot=net:UEFI,ipxe.efi,,10.200.10.20
dhcp-boot=net:UEFI64,ipxe.efi,,10.200.10.20
dhcp-boot=tag:UEFI,tag:ParallelsEFI,intel.efi,10.200.10.20,10.200.10.20

# The boot filename, Server name, Server Ip Address
dhcp-boot=undionly.kpxe,,10.200.10.20

# PXE menu.  The first part is the text displayed to the user.  The second is the timeout, in seconds.
pxe-prompt="Booting FOG!", 10

dhcp-range=10.200.10.20,proxy
        george1421G 1 Reply Last reply Reply Quote 0
        • george1421G
          george1421 Moderator @Merilious
          last edited by

          @Merilious That one looks good. There is the next step if that one doesn’t boot correctly. The dnsmaq configuration is built in layers, you start basic and then build up until it works in your environment. Right now you are on step 2 of 3.

          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!

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

            @george1421 So with 2.76 is your pxe booting for uefi working as you need it?

            Don’t follow this just yet, posting it cause I’m doing 4 things right now and don’t want to loose the link.
            ref: https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue

            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!

            M 1 Reply Last reply Reply Quote 0
            • M
              Merilious @george1421
              last edited by

              @george1421

              UEFI is not working. Only BIOS booting works as intended. When I look in the syslog it shows that there is communication, the client just doesn’t push to the FOG bootup.

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

                @Merilious is the uefi iPXE kernel making it to the target computer (i.e. are you seeing the iPXE banner)?

                If you are unsure where to turn next, then follow and do what the tutorial says in the previous post. What we need to do is capture the pxe bootup of one of these uefi systems. This works really well if the fog server and the pxe booting client is on the same subnet. Post the pcap here for review.

                I can boot and image a BIOS system no problem. It’s UEFI/EFI systems that don’t want to work

                for clarity a clear picture taken with a mobile phone helps understand what don’t work means. If we can see the error we may understand what’s wrong. The context of the error is almost as important as the error itself.

                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!

                M 1 Reply Last reply Reply Quote 0
                • M
                  Merilious @george1421
                  last edited by

                  @george1421 0_1492802598813_output.pcap

                  0_1492803378849_Screenshot_20170421-142729.png
                  1_1492803378849_Screenshot_20170421-143037.png

                  M george1421G 2 Replies Last reply Reply Quote 0
                  • M
                    Merilious @Merilious
                    last edited by

                    @Merilious

                    That 2nd snip took a little ingenuity to capture lol. Had to use the slow-mo video feature on the galaxy s7. Thanks for the help thus far. I feel like I’m on the right track, just need to fix a few nub errors I may have configured or not configured yet maybe.

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

                      @Merilious ok that tells me a bit more about the booting process. Everything looks good until it talks to the ProxyDHCP server (dnsmasq). So we need to move to step 3 for dnsmasq config.

                      after this section in your ltsp.conf

                      # PXE menu.  The first part is the text displayed to the user.  The second is the timeout, in seconds.
pxe-prompt="Booting FOG!", 10

                      Actually take the prompt timeout from 10 to 1. Its not needed since you can’t pick anything different in this configuration.

                      add in

                      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

                      I guessed at the context since I can’t find it quickly. I have the answer on my dev server at home, but well that’s at home and I’m not.

                      If that doesn’t work then move to step 4

                      pxe-service=X86PC, "Boot to FOG", undionly.kpxe,10.200.10.20
pxe-service=X86-64_EFI, "Boot to FOG UEFI", ipxe.efi,10.200.10.20
pxe-service=BC_EFI, "Boot to FOG UEFI PXE-BC", ipxe.efi,10.200.10.20

                      We don’t want to jump right to 4 because it may create other issues. So one step at a time. This should tell proxy dhcp to send the right file name per the client request.

                      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!

                      M 1 Reply Last reply Reply Quote 0
                      • M
                        Merilious @george1421
                        last edited by

                        @george1421

                        0_1492804610091_20170421_145140.jpg

                        Right after this it booted right to the FOG menu! Did a quick registration and verified FOG picked it up in the web portal. So awesome! If you don’t mind me asking, why did this work?

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

                          @Merilious Some environments require the pxe-service code and some do not. I don’t have a solid answer for you, but we start and step 1 and move to step 4 testing at each step. Your pcap file was flowing perfectly until it got to the proxydhcp dialog. dnsmasq didn’t supply what your PXE rom needed so it abort the pxe boot. This is all different pxe rom requirements. Once you are in iPXE then fog has a better chance of controlling the pxe booting process.

                          Ah ok, I just reread what iPXE posted, duplicate option 66… your dhcp server gave it one IP address for the boot server and dhcp proxy gave it another so it talked to the proxy to find out what to do. I need to look at your pcap file again a bit closer to see where your main dhcp server was sending the client. Do you have another imaging system in your environment?

                          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!

                          M 1 Reply Last reply Reply Quote 1
                          • M
                            Merilious @george1421
                            last edited by

                            @george1421

                            I have my Parallel VM’s. Just tested the EFI boot on it and it worked great. Exact same message about the duplicate DHCP. Unfortunately I’m out for the weekend as of this post so if you don’t hear anything from me until Monday… I REALLY appreciate the help. Any further information you need just ask and I’ll post first chance I get. When I saw the duplicate info notice I asked our network guy if the Next-Server entry happened to still linger but it was not.

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

                              @Merilious Great to see that you guys figured this out already. Well done George! Thanks for posting the PCAP and pictures as well. Looks like our iPXE script (see here) is not behaving the way we intended it to. I am not sure if this a general issue or just caused by the UEFI firmware you have.

                              Should be save to ignore in your case as far as I can see in the PCAP file there is no next-server/option 66 sent by your main DHCP server.

                              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 1 Reply Last reply Reply Quote 0
                              • george1421G
                                george1421 Moderator @Sebastian Roth
                                last edited by

                                @Sebastian-Roth said in Dell Inspiron 15 7559:

                                Looks like our iPXE script (see here) is not behaving the way we intended it to.

                                Well that may explain why I didn’t see the main dhcp server responding with next server. I was going to have the OP post his ltsp.conf again on monday to see if we had something in the wrong spot and/or capture another pcap file. We might want to do that just to be clear that dnsmasq isn’t doing something unexpected.

                                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 1
                                • M
                                  Merilious
                                  last edited by

                                  Alright I’m back (a day late). We’re trying to move fast with this so I’ve gone ahead and began building the FOG server on our production side. Again though, I’m stuck on breaking DNS once DNSMasq is installed. I don’t remember how I got around this before to do the DNSMasq build/upgrade to 2.76 unfortunately…

                                  You had mentioned disabling dnsmasq from taking over DNS through ltsp.conf. Here is my current running ltsp.conf:

                                   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

# 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
dhcp-match=set:ParallelsEFI,97,00:ef:e3:6d:16:10:6f:46:9d:87:12:5a:12:c2

# Set the boot file name based on the matching tag from the vendor class (above)
dhcp-boot=net:UEFI32,i386-efi/ipxe.efi,,10.100.10.22
dhcp-boot=net:UEFI,ipxe.efi,,10.100.10.22
dhcp-boot=net:UEFI64,ipxe.efi,,10.100.10.22
dhcp-boot=tag:UEFI,tag:ParallelsEFI,intel.efi,10.100.10.22,10.100.10.22

# The boot filename, Server name, Server Ip Address
dhcp-boot=undionly.kpxe,,10.100.10.22

# PXE menu.  The first part is the text displayed to the user.  The second is t$
pxe-prompt="Booting FOG!",1

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=10.100.10.22,proxy

                                  Here is my NetworkManager.conf where I removed the “DNS=DNSMASQ” line:

                                  [main]
plugins=ifupdown,keyfile,ofono

[ifupdown]
managed=false

                                  I noticed that I get a new connection named en32 when I install DNSMasq (or somewhere along the lines of installing FOG and DNSMasq). I went in that connections settings and saw 127.0.0.1 as the DNS entries so I updated them to our proper DNS entries, reset networkmanager and dnsmasq services, but still could not ping google but 8.8.8.8 pinged fine. Any ideas?

                                  Tom ElliottT george1421G 2 Replies Last reply Reply Quote 0
                                  • Tom ElliottT
                                    Tom Elliott @Merilious
                                    last edited by

                                    @Merilious if your DNS is behind a domain you may need to add the domain name to search from. Just a theory no real clue though.

                                    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
                                    • george1421G
                                      george1421 Moderator @Merilious
                                      last edited by george1421

                                      @Merilious said in Dell Inspiron 15 7559:

                                      port=0

                                      It looks like @Quazz has a solution for this here: https://forums.fogproject.org/topic/7193/ubuntu-14-04-lts-with-dnsmasq-no-external-dns/8

                                      I did a little research on this and specifically the command “port=0” and its working as designed (??). From Quazz’s post it looks like you just need to adjust the dnsmasq startup scripts to not throw 127.0.0.1 into the resolv.conf file.

                                      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!

                                      M 1 Reply Last reply Reply Quote 1
                                      • M
                                        Merilious @george1421
                                        last edited by

                                        @george1421

                                        So that did the trick! I added that line and got both EFI and BIOS to boot up to FOG. One thing always needs to another though…

                                        I tried doing a quick registration for each BIOS and EFI. BIOS goes through just fine, but the EFI gets stuck at bzIMAGE… 0%. I tried going in to the FOG web portal and updating the kernel but it still won’t budge. Any ideas?

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

                                          @Merilious said in Dell Inspiron 15 7559:

                                          but the EFI gets stuck at bzIMAGE… 0%.

                                          This is an issue with (around) the iPXE kernel for efi. What file name are you sending for a efi system? ipxe.efi?

                                          If so, for grins try this iPXE kernel instead: ipxe7156.efi Sometimes we’ll find hardware with flaky firmware (not so much Dells). Also make sure your firmware is up to date on that device.

                                          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!

                                          M 1 Reply Last reply Reply Quote 0
                                          • M
                                            Merilious @george1421
                                            last edited by

                                            @george1421

                                            I tried both the ipxe7156.efi and the intel.efi. Both had the same effect. Looked in the syslog and here’s the print out of one of the attempts. Just for verification I went in to the ltsp and changed all bootfile options to either the ipxe7156.efi or intel.efi. The one thing that pops out a little is the line saying
                                            Apr 28 10:33:54 fogprod in.tftpd[24188]: tftp: client does not accept options

                                            Apr 28 10:33:50 fogprod dnsmasq-dhcp[24056]: 1914483971 available DHCP subnet: 10.100.10.22/255.255.255.0
Apr 28 10:33:50 fogprod dnsmasq-dhcp[24056]: 1914483971 vendor class: PXEClient:Arch:00007:UNDI:003016
Apr 28 10:33:50 fogprod dnsmasq-dhcp[24056]: 1914483971 PXE(ens32) 00:1c:42:9a:b9:f7 proxy
Apr 28 10:33:50 fogprod dnsmasq-dhcp[24056]: 1914483971 tags: UEFI, ens32
Apr 28 10:33:50 fogprod dnsmasq-dhcp[24056]: 1914483971 next server: 10.100.10.22
Apr 28 10:33:50 fogprod dnsmasq-dhcp[24056]: 1914483971 broadcast response
Apr 28 10:33:50 fogprod dnsmasq-dhcp[24056]: 1914483971 sent size:  1 option: 53 message-type  2
Apr 28 10:33:50 fogprod dnsmasq-dhcp[24056]: 1914483971 sent size:  4 option: 54 server-identifier  10.100.10.22
Apr 28 10:33:50 fogprod dnsmasq-dhcp[24056]: 1914483971 sent size:  9 option: 60 vendor-class  50:58:45:43:6c:69:65:6e:74
Apr 28 10:33:50 fogprod dnsmasq-dhcp[24056]: 1914483971 sent size: 17 option: 97 client-machine-id  00:7c:9f:53:d6:94:0e:4c:00:b1:f3:2c:59:ba...
Apr 28 10:33:53 fogprod dnsmasq-dhcp[24056]: 1914483971 available DHCP subnet: 10.100.10.22/255.255.255.0
Apr 28 10:33:53 fogprod dnsmasq-dhcp[24056]: 1914483971 vendor class: PXEClient:Arch:00007:UNDI:003016
Apr 28 10:33:53 fogprod dnsmasq-dhcp[24056]: 1049156094 available DHCP subnet: 10.100.10.22/255.255.255.0
Apr 28 10:33:53 fogprod dnsmasq-dhcp[24056]: 1049156094 vendor class: PXEClient:Arch:00007:UNDI:003016
Apr 28 10:33:53 fogprod dnsmasq-dhcp[24056]: 1049156094 PXE(ens32) 00:1c:42:9a:b9:f7 proxy
Apr 28 10:33:53 fogprod dnsmasq-dhcp[24056]: 1049156094 tags: UEFI, ens32
Apr 28 10:33:53 fogprod dnsmasq-dhcp[24056]: 1049156094 bootfile name: ipxe7156.efi
Apr 28 10:33:53 fogprod dnsmasq-dhcp[24056]: 1049156094 server name: 10.100.10.22
Apr 28 10:33:53 fogprod dnsmasq-dhcp[24056]: 1049156094 next server: 10.100.10.22
Apr 28 10:33:53 fogprod dnsmasq-dhcp[24056]: 1049156094 sent size:  1 option: 53 message-type  5
Apr 28 10:33:53 fogprod dnsmasq-dhcp[24056]: 1049156094 sent size:  4 option: 54 server-identifier  10.100.10.22
Apr 28 10:33:53 fogprod dnsmasq-dhcp[24056]: 1049156094 sent size:  9 option: 60 vendor-class  50:58:45:43:6c:69:65:6e:74
Apr 28 10:33:53 fogprod dnsmasq-dhcp[24056]: 1049156094 sent size: 17 option: 97 client-machine-id  00:7c:9f:53:d6:94:0e:4c:00:b1:f3:2c:59:ba...
Apr 28 10:33:54 fogprod in.tftpd[24188]: tftp: client does not accept options
Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 available DHCP subnet: 10.100.10.22/255.255.255.0
Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 vendor class: PXEClient:Arch:00009:UNDI:003010
Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 user class: iPXE
Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 PXE(ens32) 00:1c:42:9a:b9:f7 proxy
Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 tags: UEFI64, ens32
Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 next server: 10.100.10.22
Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 broadcast response
Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 sent size:  1 option: 53 message-type  2
Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 sent size:  4 option: 54 server-identifier  10.100.10.22
Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 sent size:  9 option: 60 vendor-class  50:58:45:43:6c:69:65:6e:74
Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 sent size: 17 option: 97 client-machine-id  00:7c:9f:53:d6:94:0e:4c:00:b1:f3:2c:59:ba...
Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 available DHCP subnet: 10.100.10.22/255.255.255.0
Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 vendor class: PXEClient:Arch:00009:UNDI:003010
Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 user class: iPXE
Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 available DHCP subnet: 10.100.10.22/255.255.255.0
Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 vendor class: PXEClient:Arch:00009:UNDI:003010
Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 user class: iPXE
Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 PXE(ens32) 00:1c:42:9a:b9:f7 proxy
Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 tags: UEFI64, ens32
Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 bootfile name: ipxe.efi
Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 server name: 10.100.10.22
Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 next server: 10.100.10.22
Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 sent size:  1 option: 53 message-type  5
Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 sent size:  4 option: 54 server-identifier  10.100.10.22
Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 sent size:  9 option: 60 vendor-class  50:58:45:43:6c:69:65:6e:74
Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 sent size: 17 option: 97 client-machine-id  00:7c:9f:53:d6:94:0e:4c:00:b1:f3:2c:59:ba...
Apr 28 10:36:55 fogprod in.tftpd[24329]: tftp: client does not accept options
Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 available DHCP subnet: 10.100.10.22/255.255.255.0
Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 vendor class: PXEClient:Arch:00009:UNDI:003010
Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 user class: iPXE
Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 PXE(ens32) 00:1c:42:9a:b9:f7 proxy
Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 tags: UEFI64, ens32
Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 next server: 10.100.10.22
Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 broadcast response
Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 sent size:  1 option: 53 message-type  2
Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 sent size:  4 option: 54 server-identifier  10.100.10.22
Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 sent size:  9 option: 60 vendor-class  50:58:45:43:6c:69:65:6e:74
Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 sent size: 17 option: 97 client-machine-id  00:7c:9f:53:d6:94:0e:4c:00:b1:f3:2c:59:ba...
Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 available DHCP subnet: 10.100.10.22/255.255.255.0
Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 vendor class: PXEClient:Arch:00009:UNDI:003010
Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 user class: iPXE
Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 available DHCP subnet: 10.100.10.22/255.255.255.0
Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 vendor class: PXEClient:Arch:00009:UNDI:003010
Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 user class: iPXE
Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 PXE(ens32) 00:1c:42:9a:b9:f7 proxy
Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 tags: UEFI64, ens32
Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 bootfile name: ipxe.efi
Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 server name: 10.100.10.22
Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 next server: 10.100.10.22
Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 sent size:  1 option: 53 message-type  5
Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 sent size:  4 option: 54 server-identifier  10.100.10.22
Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 sent size:  9 option: 60 vendor-class  50:58:45:43:6c:69:65:6e:74
Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 sent size: 17 option: 97 client-machine-id  00:7c:9f:53:d6:94:0e:4c:00:b1:f3:2c:59:ba...
                                            1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 1 / 2
                                            • First post
                                              Last post

                                            162

                                            Online

                                            12.1k

                                            Users

                                            17.3k

                                            Topics

                                            155.4k

                                            Posts
                                            Copyright © 2012-2024 FOG Project