Dnsmasq on your FOG server
-
Hello all,
I followed the configuration: server to make Dnsmasq my FOG server, but when I go to test the results we are unable to boot and the error PXE-E16 no valid offer received appears.Our ltsp.conf file:
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,172.22.21.18
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:00009Set the boot file name based on the matching tag from the vendor class (above)
dhcp-boot=net:UEFI32,i386-efi/ipxe.efi,172.22.21.18
dhcp-boot=net:UEFI,ipxe.efi,172.22.21.18
dhcp-boot=net:UEFI64,ipxe.efi,172.22.21.18PXE 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.efiSubnets=
dhcp-range=<fog_server_IP>,proxy
dhcp-range=192.168.10.0,proxy,255.255.255.0
dhcp-range=172.30.20.0,proxy,255.255.255.0The service runining ok and in windows dhcp i have option 66 to point to FOG server
Any help?