SOLVED Does FOG server require nic card to support Wake on Lan for other hosts to recognize?
I’m new to FOG and recently installed the server in a virtual environment. I run ESXi 6.5 Server, where I run my virtualized pfSense firewall along side FOG. The pfSense is connected to a cisco switch that handles the layer 2 switching (VLAN). The nic card my FOG server is connected to doesn’t support wake on lan. I have connected a laptop I want to image to the cisco switch and on the same subnet/ VLAN as the FOG server, set the laptop to boot from LAN but doesn’t work (won’t get and IP from DHCP).
I’m I having this problem because the FOG nic card doesn’t support wake on lan and can’t send/ receive magic packets?
PS: I have set the laptop to wake on lan with PXE Boot
Hi @Sebastian-Roth yes, you’re right. pfSense was the problem and solution. Found the solution on this post ((https://forums.fogproject.org/topic/9513/pfsense-is-great/2)
Thanks for the assistance. I love this community.
Hi @george1421 ,
Thanks for you reply. It was very helpful to see running FOG on ESXi server wasn’t the problem.
I found the issue and fortunately you and @dureal99d had the solution on a different post lol.(https://forums.fogproject.org/topic/9513/pfsense-is-great/2)
pfSense supports network booting on the DHCP Server side. I had to enable that feature and put my FOG Server IP in the name server. God, I love pfSense.
I have to continue working on other FOG issues lol.
Thanks guys you’re a lifesaver.
I have connected a laptop I want to image to the cisco switch and on the same subnet/ VLAN as the FOG server, set the laptop to boot from LAN but doesn’t work (won’t get and IP from DHCP).
This is the main question, do I get this right? Well I need to ask, what is serving DHCP in your network?? You said something about pfSense which I know is capable to doing DHCP (including PXE boot information) but not sure. Could be a Windows DHCP server in your network or even the FOG server (if enabled when installing). Make sure you only have one DHCP server in your VLAN and that needs to provide PXE boot information (extra DHCP infos) to your clients.
WOL is impacted by the target computer more than the fog server.
In my environment I have FOG running on ESXi 6.7 VM. I just had to look but I’m running a vmxnet3 virtual network interface on a centos 7.5 server for my fog server.
I know when I deploy an image to a Dell computer on the same subnet as the FOG server, the target computer will start up.
So what I’m wondering is… is the problem with the fog server or the target computer? One way to test would be to get a windows utility app that sends out WOL packets to see if the computer starts correctly. I’ve used the nirsoft wakemeonlan https://www.nirsoft.net/utils/wake_on_lan.html its pretty basic but should test if the workstation is setup correctly.
On the FOG server side make sure the mac address is right and matches the target computer.
Lastly Windows 10 messes with WOL, messes as is disables it. A way to test if Win10 is messing with WOL. Test WOL by unplugging and plugging in the power cable. This is state G0, if I remember correctly. Test WOL here if it works then great. Next boot into windows and then shutdown. This is state S5. Test WOL again. My bet is that it will not boot with WOL here.