Fog and Pfsense 2.7

[george1421]

@elchapulin Ok follow the instructions to get the pcap. That will tell us what the target computer is being asked to do. With a bios computer it should just work.

[elchapulin]

Sorry I’m new to Linux, I hope it workedoutput.pcap

[george1421]

@elchapulin You created the pcap perfectly.

I can see the pxe booting computer is in bios mode.

Looking at the dhcp OFFER packet, I see in the header the next-server is 192.168.1.22 and the boot file is undionly.kpxe. What is strange is in the dhcp options there is only dhcp option 66 which again points to 192.168.1.22. The issue is there is no dhcp option 67. All 4 fields need to be filled out. Its strange that pfsense is doing this…

Lets try this, in your screen shot the tftp server field is filled out, but that is in a different section than netbooting. Lets remove the tftp server value under the tftp section, but lets leave the next-server field set correctly under network booting. I think the tftp section is overriding the netbooting section.

[elchapulin]

@george1421 Hello, I deleted the TFTP section but it doesn’t work, sorry

[jouni.jokelainen]

I am experiencing this problem also. Same setup in hyper-v environment.

[george1421]

These should be the steps needed to configure network/pxe booting using pfsense firewall: https://forums.fogproject.org/topic/17021/how-to-configure-pfsense-for-netbooting

[jouni.jokelainen]

@george1421
Thanks
Im pretty sure i have those settings in place but i will check them when im back at office next monday.
Pfsense, Fogserver and workstarion are in same lan segment so problem cannot be in firewall rules either.

[jouni.jokelainen]

@george1421

I reinstalled Fog server according to this video: https://www.youtube.com/watch?v=uleFAPmCo7Y

Adjusted Pfsense settings for fog (Thanks for these george) :

Enable DHCP server on LAN interface

Enable network booting

Next Server: FOG palvelimen IP
Default BIOS file name: undionly.kpxe
UEFI 32 bit file name: i386-efi/snponly.efi
UEFI 64 bit file name: snponly.efi
ARM 64 bit file name: arm64-efi/snponly.efi

Note: In Hyper-V 1 generation (BIOS) virtual machines work just fine… BUT you have to disable secure boot if you use 2nd gen virtual machines.

[jouni.jokelainen]

I also noticed that if you use Windows Server DHCP you need to add Server options for DHCP as follows:

066 Boot Server Host Name:: ip or host name of FOG server
067 Bootfile Name: ipxe.efi (for UEFI system)

So do not use snponly.efi (for efi systems) or undionly.kpxe (for bios systems) as you would use if using pfsense as dhcp server.

Googlein around gave different options for 067 Bootfile Name but as im usin EFI in Hyper-V ipxe.efi seems to work. Also you need to disable secure boot in Hyper-V settings in client virtual machines.

[Sebastian Roth]

@jouni-jokelainen said in Fog and Pfsense 2.7:

Adjusted Pfsense settings for fog (Thanks for these george) :

I guess this topic is solved then. Please open a new issue if you have more questions (not related to pfSense).