Windows 10 UEFI PC opens from fog server but boots into Windows instead PXE

Sebastian Roth · Mar 29, 2016, 4:56 AM

@hariskar Thanks a lot for the PCAP file!!! I knew that dnsmasq is not very flexible but unfortunately this is another example. The matches and options do work but still dnsmasq is sending 192.168.1.1 in the DHCP header next-server field (so option 67 is pointing to 192.168.1.5 but next-server field is pointing to 192.168.1.1). Turns out that I only tested the dnsmasq config when running it on the same host where the TFTP server is running as well… So I didn’t notice.

But it seams to work with ‘dhcp-boot’ option as well - at least when I just tested here on my debian machine (only tested BIOS and 64 bit UEFI so far). Maybe this depends on dnsmasq version and does not work for others. So please give it a try:

dhcp-match=set:bios,60,PXEClient:Arch:00000
dhcp-boot=tag:bios,undionly.kpxe,192.168.1.5,192.168.1.5

dhcp-match=set:efi32,60,PXEClient:Arch:00006
dhcp-boot=tag:efi32,i386-efi/ipxe.efi,192.168.1.5,192.168.1.5

dhcp-match=set:efibc,60,PXEClient:Arch:00007
dhcp-boot=tag:efibc,ipxe.efi,192.168.1.5,192.168.1.5

dhcp-match=set:efi64,60,PXEClient:Arch:00009
dhcp-boot=tag:efi64,ipxe.efi,192.168.1.5,192.168.1.5

I am pretty sure I tested the ‘dhcp-boot’ option back when I added it to the wiki article. Either it didn’t work or I didn’t like it for some reason. Can’t remember. Please let us know if this is working for you and I will add this to the wiki!

Wayne Workman · Mar 29, 2016, 2:32 PM

@Sebastian-Roth Is that for proxy mode or non-proxy mode?

hariskar · Mar 29, 2016, 9:19 AM

Thank you Sebastian!
There is big progress! :

I opened both (UEFI, BIOS) PCs and got into PXE menu in both PCs. I successfully fully registered them both. With Host EFI Exit Type=REFIND_EFI UEFI PC goes into windows after PXE exit. BIOS PC goes into windows after PXE exit without putting something in Host Bios Exit Type.

But there is still some problem: fog can not boot both PCs. Scheduled or instant tasks don’t start. Time is correct, I put local time in General Settings, I restarted fog scheduler with

sudo service FOGScheduler restart

but nothing happens.
Thank you again!

Quazz · Mar 29, 2016, 3:51 PM

@Wayne-Workman If I’m not mistaken matching doesn’t work in proxy mode (meaning BIOS + UEFI compatibility is not possible in dnsmasq)

Wayne Workman · Mar 29, 2016, 3:53 PM

@Quazz I know, just was wanting to check if that fact has changed. Sebastian is always up to something.

Tom Elliott · Mar 30, 2016, 1:24 AM

@hariskar what’s the error you’re seeing with instant tasks? What about for scheduled tasks? Do they say there were started okay?

hariskar · Mar 30, 2016, 1:12 AM

I use fog trunk 6957 and Firmware: DD-WRT v24-sp2 (02/04/15) mega

The log is (times are correct):

Instant Task:

1 active task waiting to wake up.
[03-30-16 8:28:12 am] | Sending WOL Packet(s)
[03-30-16 8:28:12 am] - Host: ERGASTIRIO WOL sent to all macs associated

Scheduled Task:

[03-30-16 8:31:12 am] * Task run time: Wed, 30 Mar 2016 08:31:00 +0300
[03-30-16 8:31:12 am] * Found a task that should run…
[03-30-16 8:31:12 am] - Is a host based task.
[03-30-16 8:31:12 am] - Unicast task found!
[03-30-16 8:31:12 am] - Host ERGASTIRIO
[03-30-16 8:31:12 am] - Tasks started for host ERGASTIRIO!
[03-30-16 8:32:12 am] * 1 active task waiting to wake up.
[03-30-16 8:32:12 am] | Sending WOL Packet(s)
[03-30-16 8:32:12 am] - Host: ERGASTIRIO WOL sent to all macs associated
[03-30-16 8:32:12 am] * No tasks found!
[03-30-16 8:33:12 am] * 1 active task waiting to wake up.
[03-30-16 8:33:12 am] | Sending WOL Packet(s)
[03-30-16 8:33:12 am] - Host: ERGASTIRIO WOL sent to all macs associated
[03-30-16 8:33:13 am] * No tasks found!

Sebastian Roth · Mar 30, 2016, 11:19 AM

@Wayne-Workman said:

@Sebastian-Roth Is that for proxy mode or non-proxy mode?

Quazz is right! Just for the records, definitely not in proxy mode as far as I know. Too bad.

Sebastian Roth · Mar 30, 2016, 1:10 PM

@hariskar said:

But there is still some problem: fog can not boot both PCs.

Is WOL (wake on LAN) enabled in BIOS/UEFI for both PCs ???

PS: Updated the wiki article to use ‘dhcp-boot’ instead of ‘dhcp-option-force’ as I can’t think of why ‘dhcp-boot’ should not work for others as well. We’ll see. Please prove me wrong.

hariskar · Mar 30, 2016, 8:53 PM

Yes of course. WOL was working in both PCs with undionly.PXE. After I put the 12 lines in DNSMasq it does not work with fog. But I can wake up my PCs from the routers interface.

Sebastian Roth · Mar 30, 2016, 3:44 PM

@hariskar Can you make sure the WOL packets are sent to the network? Install tcpdump package on your FOG server and run tcpdump -i any -w wol.pcap port 9. Leave the command on the console and schedule a task for the PCs, check the logs for WOL packets being sent and then stop tcpdump (Ctrl-c). Please upload the wol.pcap file to the forum so we can have a look.

hariskar · Mar 31, 2016, 5:03 AM

0_1459400650652_wol.pcap

Fog Log Viewer/Service Master newest entry is 2 days ago, is this correct?

[03-27-16 2:20:17 pm] FOGTaskScheduler fork()ed child process (9831).
[03-27-16 2:20:17 pm] FOGTaskScheduler child process (9831) is running.
[03-29-16 12:55:48 pm] service_signal_handler (9812) received signal 15.
[03-29-16 12:55:48 pm] service_signal_handler (9812) killing child (9831).
[03-29-16 12:55:48 pm] service_signal_handler (9812) exiting.
[03-29-16 3:55:48 pm] FOGTaskScheduler Start
[03-29-16 3:55:48 pm] FOGTaskScheduler fork()ed child process (16875).
[03-29-16 3:55:48 pm] FOGTaskScheduler child process (16875) is running.
[03-29-16 3:57:05 pm] service_signal_handler (16859) received signal 15.
[03-29-16 3:57:05 pm] service_signal_handler (16859) killing child (16875).
[03-29-16 3:57:05 pm] service_signal_handler (16859) exiting.
[03-29-16 4:10:24 pm] FOGTaskScheduler Start
[03-29-16 4:10:24 pm] FOGTaskScheduler fork()ed child process (5292).
[03-29-16 4:10:24 pm] FOGTaskScheduler child process (5292) is running.
[03-29-16 5:52:09 pm] service_signal_handler (5273) received signal 15.
[03-29-16 5:52:09 pm] service_signal_handler (5273) killing child (5292).
[03-29-16 5:52:09 pm] service_signal_handler (5273) exiting.
[03-29-16 5:52:09 pm] FOGTaskScheduler Start
[03-29-16 5:52:09 pm] FOGTaskScheduler fork()ed child process (6073).
[03-29-16 5:52:09 pm] FOGTaskScheduler child process (6073) is running.

Sebastian Roth · Mar 31, 2016, 6:51 AM

@hariskar The PCAP file is completely empty. Either something went wrong with capturing or your server does not send WOL packets. The ServiceMaster Log looks ok to me! Please check the FOGScheduler log again. Change “Number of lines” to 1000 so you see it all. On (re)start the scheduler should print the FOG logo and then a couple of lines like:

Interface Ready with IP Address: ...

Please post that part of the logs here.

hariskar · Mar 31, 2016, 8:52 AM

###########################################
 # Free Computer Imaging Solution #
 # Credits: #
 # http://fogproject.org/credits #
 # GNU GPL Version 3 #
 ###########################################

[03-31-16 11:50:20 am] Interface Ready with IP Address: 94.69.139.243
[03-31-16 11:50:20 am] Interface Ready with IP Address: 192.168.1.5
[03-31-16 11:50:20 am] Interface Ready with IP Address: debian-server
[03-31-16 11:50:20 am] Interface Ready with IP Address: ppp-94-69-139-243.home.otenet.gr
[03-31-16 11:50:20 am] * Starting TaskScheduler Service
[03-31-16 11:50:20 am] * Checking for new items every 60 seconds
[03-31-16 11:50:20 am] * Starting service loop
[03-31-16 11:50:20 am] * 0 active tasks waiting to wake up.
[03-31-16 11:50:20 am] * No tasks found!
[03-31-16 11:51:20 am] * 0 active tasks waiting to wake up.
[03-31-16 11:51:20 am] * No tasks found!
[03-31-16 11:52:20 am] * 0 active tasks waiting to wake up.
[03-31-16 11:52:20 am] * No tasks found!

Sebastian Roth · Mar 31, 2016, 8:59 AM

@hariskar said:

[03-31-16 11:52:20 am] * 0 active tasks waiting to wake up.
[03-31-16 11:52:20 am] * No tasks found!

Did you actually schedule a task when capturing the PCAP dump?? Sorry for asking those questions but I cannot help myself. WOL is working great here and I cannot reproduce what’s going wrong on your system.

hariskar · Mar 31, 2016, 3:18 AM

Sebastian, sorry for confusing you. The log above is just from Scheduler restart, without any task. I upload here a new wol.pcap where you should see a packet from an instant task.0_1459415578972_wol.pcap

[03-31-16 12:14:22 pm] * 1 active task waiting to wake up.
[03-31-16 12:14:22 pm] | Sending WOL Packet(s)
[03-31-16 12:14:22 pm] 		- Host: ergastirio WOL sent to all macs associated
[03-31-16 12:14:22 pm] * No tasks found!

Sebastian Roth · Mar 31, 2016, 9:24 AM

@hariskar Thanks for log info and the new PCAP. It’s empty again… I am kind of lost with this. Will check the code to see how we can further debug this.

Sebastian Roth · Mar 31, 2016, 9:31 AM

@hariskar Please get another pcap dump and while it is waiting access this URL from your browser: http://192.168.1.5/fog/management/index.php?node=client&sub=wakeEmUp&mac=00:00:00:00:00:01 (put in your client’s MAC address instead)

hariskar · Mar 31, 2016, 11:21 AM

I re-installed fog and everything works fine!

hariskar · Apr 1, 2016, 3:23 PM

As I said everything works great! Thank you again for great support!

Windows 10 UEFI PC opens from fog server but boots into Windows instead PXE

117

12.1k

17.3k

155.3k