FOG server Withou dhcp services

[errbravosix]

@george1421

I hope this is help.

Thats is everthing i have in Offer section.

Thanks.

[george1421]

@errbravosix OK I see the problem but not sure right away how to fix.

In the ethernet header we are seeing both the next-server [172.16.1.15] and boot-file [ipxe.efi] fields populated. But there are no dhcp options of 66 and 67. The PXE roms in computers can either look at the header or at the dhcp options or both to find the boot server. Its up to the rom manufacturer where to look.

What dnsmasq is doing at the moment is only filling out the ethernet header fields, this is BOOTP method. and not filling out the DHCP method fields. In your ltsp.conf file the field match is happening because its picking ipxe.efi for the boot file. Whats missing is the sending the dhcp options too. So its 80% working, we just need the remaining 20% to have a functional solution.

[errbravosix]

@george1421

Thanks a lot to reply, i will continue searching for some solution, strange is, when i enable the true dhcp on my pfsense, everthing works fine.

per hour without dhcp just work on legacy no problem, i will try discover whats is cause.

Thank you so much, if you have any idea, please send a message.

[george1421]

@errbravosix said in FOG server Withou dhcp services:

enable the true dhcp on my pfsense, everthing works fine

This is because pfsense is filling out both the bootp and dhcp parts for pxe booting.

dhcp just work on legacy no problem

This can be explained because the legacy bios firmware is probably only looking at the bootp fields and not only looking at dhcp fields for pxe boot info.

The issue “I think” is specifically with dnsmasq and its configuration. There is something missing to tell it to also send dhcp fields and not just boot fields. I’ve just not used dnsmasq this way before I don’t know off the top of my head the answer.

[errbravosix]

@george1421

I understand your point.

So i will continue looking for a solution.

Can we leave this post open for now? Maybe someone can help at some point.

[george1421]

@errbravosix said in FOG server Withou dhcp services:

dhcp-boot=net:UEFI32,i386-efi/ipxe.efi,172.16.1.15
dhcp-boot=net:UEFI,ipxe.efi,172.16.1.15
dhcp-boot=net:UEFI64,ipxe.efi,172.16.1.15

In your LTSP.conf Update this section to:

dhcp-boot=net:UEFI32,i386-efi/ipxe.efi,172.16.1.15,172.16.1.15
dhcp-boot=net:UEFI,ipxe.efi,172.16.1.15,172.16.1.15
dhcp-boot=net:UEFI64,ipxe.efi,172.16.1.15,172.16.1.15

Lets see if that gives you a successful pxe boot.

[errbravosix]

@george1421

I will try here, just a moment.

thanks

[errbravosix]

@george1421
I do what do you want.

but dhcp-proxy stops delivery ip to vm with UEFI.

when i remove your changes, delivery dhcp-proxy works fine, but we go back to zero blue screen nothing happens.

legacy still works with your changes, and without your changes.

[george1421]

@errbravosix The more research I do the more I’m thinking that your config file should just work.

I did put together an alternate configuration for dnsmasq. As long as the dnsmasq server is running on the fog server this config should also justwork.

# 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

# 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-match=set:efi-x86_64,option:client-arch,7
dhcp-match=set:efi-x86_64,option:client-arch,9
dhcp-match=set:efi-x86,option:client-arch,6
dhcp-match=set:bios,option:client-arch,0

# Set the boot file name based on the matching tag from the vendor class (above)
dhcp-boot=tag:efi-x86_64,ipxe.efi
dhcp-boot=tag:efi-x86,i386-efi/ipxe.efi
dhcp-boot=tag:bios,undionly.kpxe

# PXE menu.  The first part is the text displayed to the user.  The second is the timeout, in seconds.
pxe-prompt="Buscando Servidor de Imagens", 5

# 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 (BIOS)",undionly.kpxe
pxe-service=X86-64_EFI,"Boot to FOG (EFI)",ipxe.efi
pxe-service=BC_EFI,"Boot to FOG (EFI)",ipxe.efi

dhcp-range=172.16.1.50,172.16.1.52,255.255.255.0

[errbravosix]

@george1421

Hey boss

I use your config file and, nothing happens.

but i found on the network two more lines of parameter codes.

When i add this lines, its work fine, sounds good.

They are:

# TFTP IP is required on all dhcp-boot lines (unless dnsmasq itself acts as tftp server?)
pxe-service=tag:!ipxe-ok,X86PC,PXE,undionly.kpxe,172.16.1.15
pxe-service=tag:!ipxe-ok,IA32_EFI,PXE,snponlyx32.efi,172.16.1.15
pxe-service=tag:!ipxe-ok,BC_EFI,PXE,snponly.efi,172.16.1.15
pxe-service=tag:!ipxe-ok,X86-64_EFI,PXE,snponly.efi,172.16.1.15

And:

#set ipxe-ok tag if we have correct combination
# http && menu && iscsi ((pxe && bzimage) || efi)
tag-if=set:ipxe-ok,tag:ipxe-http,tag:ipxe-menu,tag:ipxe-iscsi,tag:ipxe-pxe,tag:ipxe-bzimage
tag-if=set:ipxe-ok,tag:ipxe-http,tag:ipxe-menu,tag:ipxe-iscsi,tag:ipxe-efi

After add these lines everthing WORKS SO GOOD.

Change Status to SOLVED, in Gods Name.

Thanks a lot man, for all help you give to me.

[george1421]

@errbravosix Would you provide a complete ltsp.conf file because what you provided here shouldn’t have fixed the problem directly,

BUT from the original config, if you would have modified it to this for the pxe-service section:

pxe-service=X86PC,"Boot to FOG (BIOS)",undionly.kpxe,172.16.1.15
pxe-service=X86-64_EFI,"Boot to FOG (EFI)",ipxe.efi,172.16.1.15
pxe-service=BC_EFI,"Boot to FOG (EFI)",ipxe.efi,172.16.1.15

Then that config should have worked. dnsmasq is a bit cryptic with its optional parameters I do have to say.

BUT I can say if you have it working then its working so no need to change anything. Good job finding the solution.

[errbravosix]

@george1421

Yes, I changed it, exactly as you just mentioned, and it still didn’t work, it worked fine when I added those two lines of code I mentioned earlier.

Anyway, thank you very much for your help and attention.