UEFI and windows 10
-
@hammett131 If you use this filter
tcpdump -w output.pcap port 67 or port 68 or port 69 or port 4011
it should create output.pcap in the current directory where you ran the tcpdump command. -
This post is deleted! -
@george1421 Silly me…long day clearly.
https://drive.google.com/open?id=0B3KPegStLS26aXVURGJ2X3psVS1qOFI1Vk1RdzRQU09zOUg4 -
@hammett131 ok I see why it doesn’t boot.
The device is saying its a uefi system (EF-BC type 7) but 10.0.2.1 is sending undionly.kpxe as the boot file name. The target computer promptly downloads the file and chokes on it. Its saying the next server is 10.0.2.122, which is your fog server?
-
@george1421 I downloaded wireshark to check it real quick. Saw that to… but my setting on my sonic wall is ipxe…hmmmm sounds like something over there. Thanks for the help maybe I’ll try restarting it.
-
@hammett131 If you can’t get your sonicwall to cooperate you can install dnsmasq on the FOG server to dynamically supply the boot information while you still use the sonicwall for dhcp services. There are a number of ways to get things working in your environment.
-
@george1421 yes it is and I found where in the sonicwall it had undionly.kpxe. It is booting to fog as we speak! Thanks so much just needed another set of eyes!
-
@hammett131 Do you mind explaining where in your sonicwall you found it showing undionly.kpxe?
I have the exact issue - I changed my option 67 to ipxe.efi, but my pcap shows undionly.kpxe is being requested. I’ve been beating my head against my desk all day trying to get this figured out. Any help would be greatly appreciated! -
I finally found it!
For anyone else with this issue, check the advanced tab of your Dynamic Lease Scope in your DHCP settings.
I found the answer here that included the screenshot to make it super clear: https://community.spiceworks.com/topic/1772601-pxe-booting-with-a-sonic-wall -
@kellym Sorry I didn’t check the forums yesterday, glad you found it!
