SOLVED Cannot PXE boot target capture device.
I am trying to capture an image but the but any device that I boot to the network with will not load the undionly.kpxe and states Could not start download: Operation not supported. I have set the the static ip address of the fog server and undionly.kpxe on option 66 and 67 respectively on DHCP.
My fog server and target capture machine are both Virtualbox VM’s that can be pinged from other machines on the network and vice versa as well as each other. On iPXE it shows that option 66 and 67 are configured correctly.
I have tested TFTP by running the command tftp -i x.x.x.x get undionly.kpxe and the transfer was successful. And also created a symbolic link undionly.0 between undionly.kpxe with the command sudo ln -s -r undionly.kpxe undionly.0 with no luck.
I have also enabled portfast and disabled BDU on the VM Host computer’s switch port. I have also created another fog VM that has dhcp enabled and connected to an internal network with my target capture machine to test if it works and was able to PXE boot with no issues.
I feel like I’ve tried every solution that I could find online but still unable to fix this issue. Hopefully someone will be able to help me out.
I boot to the network with will not load the undionly.kpxe
Realize that undionly.kpxe will only boot on bios (legacy) based machines. For uefi based machines you will need to send ipxe.efi
e both Virtualbox VM’s
For virtualbox make sure you are using a bridged connection to your network and not natted
And also created a symbolic link undionly.0
FOG doesn’t use undionly.0 files. That symlink is not needed.
So lets start out with what is your dhcp server for this network?
What do you have configured for dhcp options 66 and 67?
Pick a physical computer to test with:
What mode is the firmware in? (bios or uefi).
From a physical computer on the same subnet as the FOG server, can you ping the FOG server?
When you PXE boot the target computer and receive an error, snap a picture of the error on the screen and post the picture here. We need to see the context of the error message.