Noob needing help! TFTP timout

[tbaumann]

I created a VM and put CentOS 7 on it.
I installed the Fog Server on CentOS.
I have a Watchguard Firewall
I set up options 66 and 67 per directions.

When I start a new Windows 10 laptop I get this

Server IP address is 10.18.0.1 (Watchguard Firewall)
NBP filename is undionly.kpxe
NBP filesize is 0 Bytes
PXE-E18: Server response timeout.

When I restart it with Legacy Bios this is what shows up

Client IP: 10.18.21.5 Mask 255.255.0.0 DHCP IP:10.18.0.1
Gateway IP: 10.18.0.1

PXE-E32: TFTP open timeout
PXE-M0F: Exiting PXE ROM

Any help with this would be great. Again I’m completely new to all of this and really struggling with it.
Thanks

[george1421]

@tbaumann said in Noob needing help! TFTP timout:

Server IP address is 10.18.0.1 (Watchguard Firewall)
NBP filename is undionly.kpxe
NBP filesize is 0 Bytes
PXE-E18: Server response timeout.

There are a couple of things going on here.

(Almost) any time you see NBP that is a uefi system. From your post you are sending undionly.kpxe to a uefi system. This will surely not work. For uefi systems you need to send ipxe.efi. For bios system you send undionly.kpxe.

Secondly your dhcp server is your firewall. Those devices (routers in general) are notorious for sending out its own IP address as the boot server instead of what you have configured for dhcp option 66.

While I don’t like to jump directly into techie stuff, I think in this case to understand what is going on we’ll use the FOG server to listen in on the pxe booting process of that computer.

First lets set the boot file to ipxe.efi in your firewall. That should be set for dhcp option 67. For dhcp option 66 {next-server} that should be the IP address of your FOG server.

Now follow this tutorial: https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue

Upload the pcap to a file share service like google drive. Make sure the link is shared public and finally post the link here and I will look at the results. If you are interested you can look at the results in wireshark too.

[tbaumann]

Okay here is the link!

https://drive.google.com/file/d/1HO7mixTUgIx-nAZWhyuFnuNWo48Py8Wt/view?usp=sharing

[Sebastian Roth]

@tbaumann What is the IP of your FOG server? I suggest you take a picture of the error on screen and post here as there is usually some important piece of information missing when people type the stuff seen on screen.

Also make sure SELinux and firewall on the FOG server are disabled and TFTP is running! https://wiki.fogproject.org/wiki/index.php?title=CentOS_7#CentOS_7_pre-config

[tbaumann]

@Sebastian-Roth the Ip of the fog server is 10.18.21.2

Here is the pic of the newest error.

And here is the pic of the latest tcpdump

I’ll be gone until Wednesday of next week. Thanks for all your help on this!

[george1421]

@tbaumann Yeah, I should have said, I need the entire pcap file to review it. Please post the entire pcap file there are ethernet header fields I need to see.

[Sebastian Roth]

@tbaumann Again: Also make sure SELinux and firewall on the FOG server are disabled and TFTP is running! https://wiki.fogproject.org/wiki/index.php?title=CentOS_7#CentOS_7_pre-config