Isolated Network Setup (Stuck in Start PXE over IPv4)

[george1421]

@Enigma Your post is missing enough info to help.

Is 192.168.107.x an isolated network?
Is there an existing dhcp server on this subnet?
What error are you getting on the client computer?

[Enigma]

@george1421 said in Isolated Network Setup (Stuck in Start PXE over IPv4):

Is 192.168.107.x an isolated network?
Yes, its isolated

Is there an existing dhcp server on this subnet?
No, Fog will be it

What error are you getting on the client computer?
Machines are not getting pass the Start PXE over IPv4 screen

[george1421]

@Enigma ok on the fog server linux console. Key in the following command netstat -an | grep :67 That should return a line like 0.0.0.0:67 This will show if the dhcp server is running on the fog server. You can also run this command ps aux| grep dhcp to see if the isc-dhcp server is running in memory. Lets confirm that dhcp is functioning on the fog server

[Enigma]

@george1421

Ok, here are the results

[george1421]

@Enigma Well it look like I forgot to hit submit earlier when I responded. Looks like the dhcp server is up and running and listening on port 67. So that is the first half of getting things to boot.

I think the next step is to configure the fog server to capture a pxe boot packet to see if there are any other actors involved. Here are the steps needed to configure tcpdump on the fog server to capture the pxe booting process.
https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue?_=1687300270627

Other things I’ve seen cause pxe booting issues.
If dhcp snooping is enabled on your network to only allow dhcp packets to get to the defined dhcp server and that dhcp server is not the FOG server.
If you have more than one dhcp server on your subnet and the other dhcp server responds before the fog server.
You have a proxy dhcp server configured on your network
Your fog server is running as a VM on a vm host server that doesn’t have the promiscuous network mode enabled.

Most of these questions will be answered with the pcap. Once you collect the pcap upload it to a file share site and share it as public read only. Then either post the link here or use the fog forum chat and DM me the link. I will take a look and let you know what we found.

[Enigma]

@george1421

I sent over the Wireshark traffic cap over DM, also some screenshots.

[Enigma]

@george1421 I’ve disabled the firewall on the server and I’m seeing the same results (only DHCP discover packets going through)

[Tom Elliott]

@Enigma Are you sure it’s booting PXE and not UEFI?

In case it is UEFI, please disable secure boot on the machine.

[Enigma]

@Tom-Elliott
Hello, Yes you are right it was not but now it is but now stuck here.

[Tom Elliott]

@Enigma Can you edit your /etc/dhcpd.conf file and change the instances of undionly.kpxe to undionly.kkpxe, if that still doesn’t work, attempt ipxe.pxe?

Once you change the file, you’ll need to restart dhcpd service with:
systemctl restart dhcpd

[Enigma]

@Tom-Elliott Ok, but the dhcpd.conf file is empty, where should add those details?

[george1421]

@Enigma ok so how did you add dhcp services to your fog server (a blank dhcp config file would do exactly what you are seeing. ISCDHCP listening but not responding to any requests)? Did you add dhcp services when you installed FOG? Did you add the isc-dhcp server after fog was installed from your repo?

So you’ll probably ask what goes in that file? Look at this example: https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence#Example_1 The dhcp pool will probably need to be updated to match the subnet of your dedicated imaging network.

[Enigma]

@george1421 Hello thank you, For the fog setup I let dhcp service to be handled by fog. not sure why the dhcp config is empty.

Can add these details to the from the 2 screenshots to the dhcp config file?

[george1421]

@Enigma I would start with example #1 from that url. You will need to update the subnet, netmask range values so its appropriate for your isolated network. Anywhere you see the default 192.168.1.x you need to update so its appropriate for your imaging network.

[Enigma]

@george1421 Ok thank you I updated the dhcp config from example 1 and now i’m seeing different results. Can i share a traffic cap?

[george1421]

@Enigma yes same method as before.

[Sebastian Roth]

@Tom-Elliott said in Isolated Network Setup (Stuck in Start PXE over IPv4):

/etc/dhcpd.conf

I might be wrong here but from the top of my head I wouldn’t think that’s the right config file. Guess it is /etc/dhcp/dhcpd.conf though.

[Enigma]

@george1421 Hello I’ve DM the traffic cap

[Tom Elliott]

@Sebastian-Roth Probably, yeah, sorry

[george1421]

@Enigma said in Isolated Network Setup (Stuck in Start PXE over IPv4):

Hello I’ve DM the traffic cap

Ok that is looking much better I now see the DORA process (Discover, Offer, Request, Ack). BUT there is something missing. When I look at the ethernet header I see the next server being 192.168.107.2 (hopefully is your fog server). The boot file is undionly.kpxe (this is good), but what is missing is the dhcp options 66 and 67. So that is telling me you are missing something in the config file. You are so close to having this work.

Could you post your complete dhcpd.conf config file?