@george1421 Thank you for your help. I managed to speak with one of the techs from our central IT this morning. He informed me that they block PXE boot on our network. PXE traffic is automatically being filtered and dropped by the switches. I think it is unlikely that they would add my FOG server to the DHCP relay. Which makes sense I was only able to get tcpdump to see the discover traffic when I connected both machines to their own unmanaged switch.

Still not sure why dnsmasq did not respond to the DISCOVER packet. I will try reinstalling the service. Although following this revelation I may just reconfigure FOG to run DHCP and use it on its own isolated network. Thank you!

@george1421 Thank you for your help. I restarted dnsmasq again.

Here is the output from the ps aux|grep dnsmasq command:

dnsmasq 217786 0.0 0.0 10248 384 ? S 15:56 0:00 /usr/sbin/dnsmasq
oracle 222748 0.0 0.0 6380 2188 pts/0 S+ 17:13 0:00 grep --color=auto dnsmasq

I then ran a capture with tcpdump according to the link you sent. When viewing in Packet Tracer I can see the DHCP discover packet going out it receives two DHCP offer packets back however these both come from the DHCP relay address (10.163.96.3) and not my FOG server (10.163.97.121). We have two subnets in our building for our general data VLAN and clients can have IPs in the 10.163.96.0/24 range and 10.163.97.0/25 range.

This pattern of discover packets and offer packets repeats a few more times before the error is encountered. None of the offer packets come from the FOG server. Would this indicate that there is some issue with dnsmasq not responding properly to the initial Discover packet? Please let me know if you need any additional information I can also send the capture file if you would like to inspect them more closely.

@george1421 Great! Thanks so much I will do that now and update as soon as I can.

Hi. Like the title says I am unable to get a bootfile when booting a computer through PXE boot. It looks like the computer is able to grab the IP from DHCP but doesn’t get any further than that. Our network already has a DHCP and DNS server that I do not have access to and the network admins did not want to setup an IP helper address or modify the DHCP to point to FOG. I followed the steps in this article to setup a proxy DHCP https://wiki.fogproject.org/wiki/index.php?title=ProxyDHCP_with_dnsmasq but after configuring that I still receive the above error.

dnsmasq service is on version 2.86 and is actively running. I was able to successfully connect to the TFTP server from my workstation PC. Here is the conf file from /etc/dnsmasq.d/ltsp.conf.

#dont function as a dns server
port=0

#Log lots of extra info about DHCP transactions.
log-dhcp

#Set the root directory for files available via ftp.
tftp-root=/tftpboot

#The boot filename
dhcp-boot=undionly.kpxe,10.163.97.121

#Disable re-use of the dhcp servername and filename fields
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,10.163.97.121
dhcp-boot=net:UEFI,ipxe.efi,10.163.97.121
dhcp-boot=net:UEFI64,ipxe.efi,10.163.97.121

#pxe menu. the first part is text displayed to the user. The second is the tim>
pxe-prompt=“Booting FOG Client”, 1

#The known types are x86PC, PC98, IA 64_EFI, Alpha, Arc_x86
#Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_efi and X86-64_EFI
#This option is first anf will be the default if there is no input from the us>
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.163.97.121,proxy

Both the FOG server and target machine are attached to the same non-managed switch and should be within the same subnet. Is there anythingI am missing or did not configure correctly. Any help would be appreciated.

@george1421 That makes much more sense. I happened to notice the installer mention it will use undionly.kpxe for the Bootfile and wanted to make sure I didn’t somehow configure it to only use that Bootfile. I will look over that wiki article. Thank you for your help!

Hi. I am pretty new to FOG and have some questions concerning the bootfile used in the PXE boot process.

During the initial install process the installer said that the default bootfile it will use is undionly.kpxe. Which if I understand correctly is mainly intended for use with legacy BIOS systems. Most of our machines currently are UEFI.

Will undionly.kpxe work with UEFI systems if legacy boot is enabled or will only the ipxe.efi work for these computers. Does FOG automatically use both bootfiles or do you need to specify which one you will need it to use?

Similarly when setting option 67 on your DHCP server can you only set one Bootfile name?

Any help or guidance would be appreciated. Thanks.

@sebastian-roth Thank you very much for the quick reply! PhP was running on version 8.x. Downloading and running the current dev-branch now allows me to connect to the web interface. Thank you for your help!

Hi I am unable to access the fog management page to finish the installation during the initial install. Trying to access the page on Firefox only yields a blank page. Connecting on Google Chrome gives me a http 500 error “the server could not handle the request right now”.

I checked the apache error log in /var/log/apache2 which had the following error “httpd: Could not reliably determine the server’s fully qualified domain name”. I then attempted to edit the hosts file in /etc/hosts by adding the following entry fogmachine.10.163.97.121. I am not sure if this is the proper format. Our network already has a DHCP and DNS server so I am not using the fog server to provide either of those services.

I am trying to install fog 1.5.9 on Fedora Server 36. I am still learning Linux so any help/guidance would be greatly appreciated. Please let me know if I need to provide more information.