Here is the new packet capture: https://www.dropbox.com/sh/eapomuoyecmgbsw/AAAy03IERwJLx3f7cm_-DeGXa?dl=0

This is now working thanks to @george1421’s help. What happend was that I had two versions of dnsmasq installed causing this issue. I was able to remove the 2.75 version that came with the OS and recompile and reinstall 2.76. Now everything is working as expected.

This is now working thanks to @george1421’s help. What happend was that I had two versions of dnsmasq installed causing this issue. I was able to remove the 2.75 version that came with the OS and recompile and reinstall 2.76. Now everything is working as expected.

Here is the new packet capture: https://www.dropbox.com/sh/eapomuoyecmgbsw/AAAy03IERwJLx3f7cm_-DeGXa?dl=0

@george1421 I just tried the ltsp.conf file you gave and restarted the dnsmasq service. It is still doing the same thing. I’ll try another packet capture when I have more time and use your suggestions regarding the port filtering.

Thanks!

I also did a packet capture on the FOG server and this is what I see regarding the boot file:

Sure,

port=0
log-dhcp
tftp-root=/tftpboot
dhcp-no-override

dhcp-vendorclass=BIOS,PXEClient:Arch:00000
dhcp-vendorclass=UEFI32,PXEClient:Arch:00006
dhcp-vendorclass=UEFI,PXEClient:Arch:00007
dhcp-vendorclass=UEFI64,PXEClient:Arch:00009

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

dhcp-boot=undionly.kpxe,10.250.0.2

pxe-prompt=“Press F8 for boot menu”, 3
dhcp-range=10.250.0.2,proxy

I remember initially adding the dhcp-vendorclass lines to get this to work initially last year. I’m not sure if those are still needed?

Thanks

Dnsmasq version 2.76

DHCP server is our firewall at 10.250.0.1. The Fog server is 10.250.0.2. I know originally I did have to go through a lot of hurdles to get the proxy dhcp working and at the moment, I don’t recall exactly how I fixed it. I did install dnsmasq though.

I originally had an issue with pxe booting gen 1 Hyper V due to WIndows 10 1709. I was able to get that going with this topic https://forums.fogproject.org/topic/11348/hyper-v-and-pxe-boot-to-fog-problems?page=1

Now when I am trying to capture a Hyper V Gen 2 image, I see it attempt to PXE boot and I see it loads undionly.kpxe as well but as soon as I see that part completes, it then boots normally into the VM. Gen 2 VMs should get an uefi based network file correct? If so how can I fix this? I was able to capture a gen 2 image in October so this has worked in the past.

I have already tried to put back the original undionly.kpxe file to see if this helps at all, but I see the same thing happen.

Here is my set up:

Fog Server 1.5.2 on Ubuntu 16.04
Windows 10 1709 with Hyper V

@lukebarone I was able to copy the file over and now I’m currently capturing my image! Thanks again!

@lukebarone Thanks! I’ll try that.