wake on lan not working
-
hi,
I did all the configuration on the client machine and via wake on lan from pfsense, I can start the machine, but from fog, it doesn’t work.
Your version of FOG is up to date. You're running the latest stable version: 1.5.9 Versões do kernel bzImage Version: 5.10.71 bzImage32 Version: 5.10.71Is there any extra configuration to be done?
-
@eliaspereira Is pfsense your dhcp server? If yes it will work with FOG. I say this from memory so I might not have the exact menus, but in the dhcp server settings you need to enable netboot option. In that section there will be four boxes. One may be labeled next-server or boot server. That should be the IP address of the fog server. Then there are 3 fields. One for bios, that should be this value: undionly.kpxe one for 64 bit uefi: ipxe.efi and one for 32 bit uefi: i386/ipxe.efi Once that is set and you have net booting enabled you should be able to pxe boot into the FOG iPXE menu.
now if this is already configured correctly, make sure you turn off “Secure boot” in the pxe booting computer’s bios (firmware).
If all above fails, please give us a clear screen shot of the error taken with a mobile phone and post it here so we can see where it stops.
-
@george1421 said in wake on lan not working:
@eliaspereira Is pfsense your dhcp server? If yes it will work with FOG. I say this from memory so I might not have the exact menus, but in the dhcp server settings you need to enable netboot option. In that section there will be four boxes. One may be labeled next-server or boot server. That should be the IP address of the fog server. Then there are 3 fields. One for bios, that should be this value: undionly.kpxe one for 64 bit uefi: ipxe.efi and one for 32 bit uefi: i386/ipxe.efi Once that is set and you have net booting enabled you should be able to pxe boot into the FOG iPXE menu.
now if this is already configured correctly, make sure you turn off “Secure boot” in the pxe booting computer’s bios (firmware).
If all above fails, please give us a clear screen shot of the error taken with a mobile phone and post it here so we can see where it stops.
I think you misunderstood my question.
This configuration I already have and it works correctly.
My problem is with the wake on lan via fogserver.
-
@eliaspereira said in wake on lan not working:
My problem is with the wake on lan via fogserver.
Ah sorry, I was focused on people not being able to pxe boot.
Wake on LAN is a tricky problem.
- The target computer must be on the same subnet as the FOG server.
- Windows will disable WOL being nice to you. This one you can test by unplugging the computer waiting 10 seconds then plug in. Once PC inits it will power off. This is ACPI state G3 (mechanical off). See if WOL works in this state. At this point windows has not booted to mess with the network adapter.
I think pfsense also has a WOL module you can add. The idea is to test to see if the problem is with FOG, WOL protocol, or windows powering off the network adapter or disabling WOL functionality.
-
@george1421 said in wake on lan not working:
The target computer must be on the same subnet as the FOG server
We work with vlans and the fogserver is in a different vlan from the vlans of the computer labs, which we want to activate the wol.
I created a rule in our pfsense allowing the fogserver to go to the labs’ vlans, but it didn’t work.
Is there any other way to make this work?
-
@eliaspereira said in wake on lan not working:
fogserver is in a different vlan from the vlans
This is going to be your first problem. The wol magic packet is not a proper IP packet so it typically can’t traverse a router. There is a way to send WOL packet but you need to send as a directed broadcasts. On most routers this “feature” is disabled because it could be used to abuse your networks.
Are you using (or wanting to use) WOL to wake up computers for imaging or just to wake up computers at a specific time?
Understand this subnet issue is a limitation of the WOL protocol and not FOG.
