Solved Client unable to boot from FOG server running dnsmasq (CentOS 7.5)

[jgiovann]

Greetings,

I’m new to the FOG project and seems quite promising with an active community. In any case I was wondering if any one has has success in setting up a FOG server (as a DHCP proxy server) running CentOS 7.5

I’ve followed the guide at: https://forums.fogproject.org/topic/12133/fog-on-existing-dhcp-server, to the point where a client successfully obtains an IP address from the primary DHCP server and subsequently successfully communicates with the FOG server (running the dnsmasq service).

However I get the following from the client side:

Auto-select:
Boot to FOG

BOOT SERVER IP: 192.168.0.85
TFTP.
PXE-T01: File not found
PXE-E3B: TFTP Error - File not found
PXE-M0F: Exiting Intel PXE ROM
Operating system not found.

The documentation specifies the creation of the following symlinks:
ln -s /tftpboot/undionly.kpxe /tftpboot/undionly.0
ln -s /tftpboot/ipxe.efi /tftpboot/ipxe.0

… what else needs to be configured for a successful boot. Is there anything I need to setup on the FOG server ?

Any tips would be welcomed.

[Sebastian Roth]

@george1421 @jgiovann I just updated the wiki article. dnsmasq 2.76 is now available in most distros (Ubuntu, Debian, CentOS 7, …), so I moved the part about compiling it far down.

[jgiovann]

@george1421 No problem. Admittedly some IT folks don’t mind documentation (I’ll count myself) but am not up to speed with FOG and and just tipping my toes in the water.

Thanks again. By the way I noticed the post is marked as “Unsolved”. Can I change it to “Resolved” or is something you or the moderator are happy to do ?

[george1421]

@jgiovann Well done on getting this rolling!

The reason why 2.76 is two fold before 2.76 you would need to append .0 to all of your boot files. 2.76 and later you can just call the boot files by name. Secondly 2.76 is the first version to truly support uefi booting.
Lastly I agree that some of the documentation is out of date and should be updated. The FOG Project is built on IT volunteers and the last thing IT folks like to do is documentation.

[jgiovann]

Thanks for the fast responses.

George, your tips helped. Simply a case of the documentation is not up-to-date (https://wiki.fogproject.org/wiki/index.php?title=ProxyDHCP_with_dnsmasq)

It came down to a number of tweaks and looking at the ltsp.conf file you provided.

1. Confirmed the dnsmasq version running on the FOG server was later than the one you recommended
   dnsmasq -v | head -1
   Dnsmasq version 2.76 Copyright 2000-2016 Simon Kelley

2. Removed the sym links

3. The pxe-service entries didn’t have the full filenames in the last field (e.g. undionly instead of undionly.kpxe)
   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

When I PXE boot the client, I am now presented with the FOG Project boot screen.

Much appreciated

[george1421]

@jgiovann said in Client unable to boot from FOG server running dnsmasq (CentOS 7.5):

ln -s /tftpboot/undionly.kpxe /tftpboot/undionly.0
ln -s /tftpboot/ipxe.efi /tftpboot/ipxe.0

If your version of dnsmasq is 2.76 or later then the above is not needed.

Confirm the version of dnsmasq by keying in the following command dnsmasq -v at the linux console prompt of your fog server.

Use my ltsp.conf from that thread you referenced: https://forums.fogproject.org/topic/12133/fog-on-existing-dhcp-server/2
Ensure you are using the entire file and not just changing your file to match.

Ensure that you update all of the <fog_server_IP> to be the actual IP address of your FOG server.

Restart dnsmasq to ensure it pulls the correct config file.

Confirm that dnsmasq is running by keying in ps aux|grep dnsmasq

PXE boot your target computer, it should work.

[Sebastian Roth]

@jgiovann Please post your current dnsmasq config here. As well run ls -al /tftpboot on your FOG server and post output.