@Tom-Elliott I can confirm that it works with v1.5.10.1760. 🎉 Thank you very much! 🙇

@Tom-Elliott

So f144ad5 is the last working commit. In case anyone else have the same problem, this is my script to grab it and modify so it works fine with EFI keyboard in some PCs as discussed here: https://forums.fogproject.org/topic/17870/fog-ipxe-menu-no-input. It also removes neverssl.com site because it’s down now so script hangs on checking internet connection. Don’t mind main sed part, it’s probably overcomplicated since I used ChatGPT for it, but it works fine so who cares 😉

#!/bin/bash # Checkout last working FOG project commit cd git git clone https://github.com/FOGProject/fogproject.git cd fogproject git checkout f144ad5a30bdab23be4d207b471ca80057e367fd # Modify functions.sh to remove non working neverssl.com site cd ~/git/fogproject/lib/common sed -i 's+http_sites=("neverssl.com" "httpbin.org")+http_sites=("httpbin.org")+g' functions.sh # Modify buildipxe.sh to grab last working ipxe commit and fix EFI USB drivers cd ~/git/fogproject/utils/FOGiPXE cat > transform_buildipxe.sed <<'SED' /^[[:space:]]*git pull$/a\ git checkout 6cccb3bdc00359068c07125258d71ce24db5118a /^ cd \${BASE}\/ipxe\/src\/$/c\ cd \${BASE}/ipxe/\ git checkout 6cccb3bdc00359068c07125258d71ce24db5118a\ cd \${BASE}/ipxe/src/ /^ cd \${BASE}\/ipxe-efi\/src\/$/c\ cd \${BASE}/ipxe-efi/\ git checkout 6cccb3bdc00359068c07125258d71ce24db5118a\ cd \${BASE}/ipxe-efi/src/ /^sed -i 's+#define[[:space:]]*USB_HCD_USBIO+\/\/\#define[[:space:]]*USB_HCD_USBIO+g' config\/usb\.h$/c\ sed -i 's+#define<----->USB_HCD_USBIO+//#define>USB_HCD_USBIO+g' config/usb.h /^sed -i 's+\/\/\#define[[:space:]]*USB_HCD_USBIO+\#define[[:space:]]*USB_HCD_USBIO+g' config\/usb\.h$/, /^sed -i 's+\/\/\#undef[[:space:]]*USB_EFI+\#undef[[:space:]]*USB_EFI+g' config\/usb\.h$ #sed -i 's+//#define\tUSB_HCD_USBIO+#define\tUSB_HCD_USBIO+g' config/usb.h\ #sed -i 's+//#undef\tUSB_KEYBOARD+#define\tUSB_KEYBOARD+g' config/usb.h\ #sed -i 's+//#undef\tUSB_EFI+#undef\tUSB_EFI+g' config/usb.h\ sed -i 's+//#define+#define+g' config/usb.h\ sed -i 's+#define USB_CMD+//#define USB_CMD+g' config/general.h SED sed -i -f transform_buildipxe.sed buildipxe.sh rm -f transform_buildipxe.sed # Start FOG install/update cd ~/git/fogproject/bin ./installfog.sh

@Tom-Elliott said in FOG Client service disconnection, pending snapins are not even being detected:

@Jamaal The client lives on the Machine itself. not on the fog server.

Those logs live on teh Windows machine I forget the exact path but something like:

c:\program files\fog client\fog-error.log or something like that?

Yes, it’s c:\program files (x86)\fog\fog.log

I figured out the issue, lol. I was having a moment, but thanks for helping me out.

Hello,

It’s working again.
I have update to the last version (1.6.0-beta.2273) but I’m not sure it’s fixed with this.
I have also clean DB using this : https://wiki.fogproject.org/wiki/index.php/Troubleshoot_MySQL#Database_Maintenance_Commands

Thank you.

@Tom-Elliott Thanks Tom, yes that looks to have sorted it out thankyou…

@Greg-Plamondon I’m not sure I fully understand:

When I look at the dev-branch files I see that the sprintf method you are doing for PingHosts is what is happening for ImageSize/ImageReplicator

The code you’re changing is within the sprintf stanzas?

@thezman007 I would say the pcap file you provided is a model of how a proxy dhcp and dhcp server should interact. The first part of the pcap is perfect.

The second part starting at second #19. The client issues a dhcp discover and the dnsmasq answers right away, the client had to issue a second discover request before the main dhcp server @ 2.2 address responded. This pattern is repeated at the end of the pcap (you can see this if you look at the pcap with wireshark).

So this is only me reading the tea leaves but I think there is something up with your main dhcp server because its being slow to respond to dhcp requests. Understand I only can see 25 second pcap but I find it abnormal. When things go sideways (and it probably will) get a pcap of the failure, that’s going to tell us what’s missing.

I’m going to remove your pcap from your post because its not needed now.

@rodluz yes, directly from 1.5.10.1754 to 1.5.10.1763 when I saw the prompt in the FOG gui that I’m not using the latest version - it was up to date before.

in 1.5.10.1754 recapture didn’t added up, just updated the image size to the latest one.

@Greg-Plamondon
Hi,

we got a dhcp server. The computer got network, the path to the efi file is connected.
I have no access to the dhcp settings that i could set the next-server or anything else.
But i think the efi file maybe is corrupt? i have tried to edit the efi file, but then the boot stick does not work anymore.

@Tom-Elliott Do the values in .fogsettings get applied only the first time installfog.sh is executed, or are they supposed to be applied on every subsequent run as well?
In my case, updating .fogsettings after the initial installation doesn’t seem to change anything, so I want to confirm whether this is expected behavior or if I’m missing something.

@george1421 said in PXE issues:

@Jamaal This problem is solvable but it make take some effort on your part.

Lets start with the basics.

For the DHCP IP zone where your pxe booting clients live, you need to set dhcp options 66 to the IP address of your fog server. And for dhcp options 67 that needs to be snponly.efi or snp.efi. With those settings configured on a MS Windows based dhcp server a pxe booting client should boot. Make sure on your dhcp server that is responding to bootp and dhcp requests. Its been a while since I messed with windows but on the dhcp server there should be a setting of dhcp bootp or both. Select both.

Now lets talk about WDS for a second. A WDS server can use dhcp options 66 and 67 as above, but it can also run a proxy dhcp service that tells the client to ignore the dhcp options and come talk to it for boot information after it gets an IP address for the dhcp server. This maybe called a netboot service or something like that on your WDS server. Its not part of the main WDS service. If this service is still enabled it will override any settings you make in dhcp for pxe booting.

So how do you figure this out to what’s wrong?

The easiest and most complicated issue is to identify what is flying down your network during the pxe booting process. You can do this with wireshark on a witness computer (computer not part of the pxe booting process). This witness computer can either be a ms windows or linux computer, the key is to have wireshark loaded. When you start up a capture use a capture filter of port 67 or port 68 or port 4011 That will limit what wireshark sees to only the dhcp packets. Make sure the witness computer is connected to the same subnet as the pxe booting computer.

Start the packet capture and then attempt to pxe boot the target computer. Continue to capture the packet until the pxe booting computer either reaches the fog iPXE menu or errors out. Then stop the capture.

In the top section you should see the DORA (discover, offer, request, and finally ack/nack) process. The process goes as follows:
Client -> Discovery
Server-> Offer
Client -> Request
Server -> Ack/Nack

In this process you are most interested in the one or more OFFER packets. In a normal network you should only see one OFFER packet. When WDS is involved you will see one OFFER packet from your main dhcp server and a second OFFER packet from your WDS server. If you are seeing the OFFER from your WDS server then you don’t have the proxy-dhcp service disabled, and that is causing your issue. If you are seeing two offer packets from two different dhcp servers, such as a primary / secondary setup make sure both dhcp server are configured to boot from FOG server.

Now what do you do if you only have one OFFER packet and its still not working. This is where you need to select the OFFER packet and then look at the data in the parameters box. There will be the bootp fields of next-server and boot-file these need to be configured for the fog server IP and snp.efi. Then in the dhcp options section options 66 and 67 need to be set correctly. If one or the other sections are not set correctly you will get random machines not booting while others are.

If you can’t figure it out save the packet capture file “be sure you only captured the dhcp process” and up load the file to a file share site and post the link here and one of us will take a look to see what’s wrong. But I think from what I covered here you should be able to figure out what the pxe booting client is being told to do incorrectly.

George,

I ran the idea with the system administrator at my job and of course he was doubtful (conceited), he turned off the server thinking that would solve the issue. I ended up looking at an older forum and made a USB with the ipce file and booted up the machines that were given me issues and that worked. You guys can close this and mark as resolved. Again, I appreciate your guidance on this.

@dimoura

Hello!

Do you have Secure Boot enabled?

I worked with this Dell Machine about 6 months ago and don’t have it with me now.

So here it goes.

Ensure secure boot is disabled. You will need to re-enable it for Windows 11 to work., You need to ensure your SATA mode setting is set to “AHCI”. - If you have “RAID” selected (which was the default from the Dell Machines I tried) it will not work. If you have legacy IPv4 PXE booting that would work best, newer computers no longer have a legacy PXE boot, but use UFEI IPv4 PXE booting. Check if that is enabled.

Otherwise, check what bzImage files you are using. The bzImage files have the linux kernel drivers which I think I used the latest stable ones I could find. These are placed in /var./www/html/fog/service/ipxe

There are 4 files in there which need to be there
bzImage
bzImage32
init.zx
init_32.zx

Or others depending on what CPU architecture your machines use. These are available on the following URL
https://github.com/FOGProject/fos/releases

I found that some work better than others as the FOG project is maintaining their FOS releases and adding computers. It is possible that one you are using simply does not have the drivers for the PC you are using. I would back up these files before updating these to ensure your older machines can PXE when updating your FOS (fog OS).

Matt

I have just discovered that somehow all the MACs are changing sometime after the final successful DHCP lease.
My DHCP server is set to only answer to specific MACs, so if I add in the “new” one, it works.
No idea how this is happening, I’ve never seen MACs just suddenly change like this.
It sucks that now I have another MAC per server to deal with, but at least it’s working.

I’m also interested in knowing if a solution exists.

@jas777 It looks like you are running an old version of iPXE. The newest version, as of 10 minutes ago when I built it, is 1.21.1+ (g21b5b).
I may be wrong, since I don’t use my own custom certificate, but you probably need to rebuild your iPXE with the new certificate.

@christop Can you post your apache error log (or php-fpm www-error.log if redhat based) showing the message immediately after the HTTP 5xx Server Error.

@deharter i could capture changing the image type , from “Single Disk - Resizeable” to “Multiple Partition Image - Single Disk (Not Resizeable)”

In Reports Menu, Imaging Log You will find this information.

@The-Dealman Awesome thank you! and we did publish 1754 specifically due to this issue (manually running the automated processes just in case your org is worried at all 🙂 )