Trying to build FOG server on standalone network

[george1421]

@davidjor Ok a couple of things.

1. Use my ltsp.conf file
2. The one you provided only supports bios systems, and you are missing a few details.
3. You have a few additional settings that could possibly confuse certain target PXE Roms.
4. Make sure you don’t have any other .conf files in the same directory as the ltsp.conf file.

From the linux command prompt on the FOG server please run this command and post the version number displayed dnsmasq -v Lets hope its 2.76 or newer.

If you were pxe booting a uefi system it would have failed for sure.

# 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,,<fog_server_IP>

# 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,,<fog_server_IP>
dhcp-boot=net:UEFI,ipxe.efi,,<fog_server_IP>
dhcp-boot=net:UEFI64,ipxe.efi,,<fog_server_IP>

# 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=<fog_server_ip>,proxy

[davidjor]

everywhere this conf file says <fog_server_IP> I need to edit for my ip Address, correct?

[george1421]

@davidjor yes, that was in the link I provided. BUT I should have also restated it, my mistake.

Also you need dnsmasq 2.76 or later to support dynamic support for both uefi and bios systems

[davidjor]

@george1421 Thank you.

[davidjor]

@george1421 I am getting the same result. I am running dnsmasq 2.78

[george1421]

@davidjor OK then follow the second link to capture a pcap file from the FOG server: https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue

Post a link to the pcap file here. (FWIW: I have a similar setup wrt54/dd-wrt/dnsmasq/fog in my home lab, so I know it does work).

[davidjor]

@george1421 George, please see the link attached. https://www.dropbox.com/s/6y7ci7g8huegm9p/output.pcap?dl=0

[george1421]

@davidjor Look at the chat bubble on the FOG tool tray. I have a few questions

[george1421]

Looking at the pcap it appears the fog server is telling the client to load pxelinux.0, which of course is wrong. What confuses me is that dnsmasq does tell the client the right file name to use in the initial Offer packet.

[Sebastian Roth]

@davidjor I think things are being a bit mixed up here. Let’s step back and take the whole picture. In your initial post you said you wanted a FOG standalone setup and you thing dnsmasq could cause the issue. Let me ask, why do you use dnsmasq at all. What is providing DHCP in this scenario? Looks like an external server is doing this. What is it? Why can’t you add PXE boot options to that DHCP server?

If you can’t modify that DHCP server then dnsmasq is the right way to go. But as it can be a little tricky I first wanted to check if we really need to go that way.

Looking at the config you initially posted I see a line pxe-service=X86PC, "Boot from network", pxelinux which could be causing that we see pxelinux in the pcap file. Please make sure you only use Georges config (not a combined one) and put in your IP addresses where needed.