Wake on LAN?

  • Thread starter Thread starter Deleted User 298457
  • Start date Start date

Deleted User 298457

Deleted User 298457

Hi folks,

Are there any tricks to this? I have tried to configure it before but given up and can't remember why. Long story short - I have a PC ~35M away (little HP desktop thing), and I've just setup another (MSI Gaming7 Intel i7 4790k) in the workshop (~20M away). I have a little HP thing also running HomeAssistant.

It is the one thing that I've always allowed to defeat me - is it as simple as a BIOS setting and then an "app" to send the magic packet?

Thanks!
 
Meddling-Monk said:
WOL works fairly easily. But you need to be aware of a few basic things:

1. WOL from a non onboard NIC will not be able to wake the computer, as they are not powered and communicating with the motherboard that boots up in that fashion, no matter what your NIC may say; if it's not a soldered one on the IO of the motherboard, it's not going to wake your system. Supposedly servers and other specific devices can do this, but general consumer stuff doesn't.

2. This is why you need the BIOS setting that enables onboard WOL (with the onboard NIC). Without this, the system will not check for incoming WOL signals to power the system up (WOL).

3. Altogether, this means that if you're using a non motherboard NIC (say 2.5/5/10g card), these won't be able to wake the system, but you can use WOL (send signal to the one) on the motherboard NIC and then that'll wake the system up. You can set up the system that wakes to use the faster connection NIC instead (depends on OS). The weighting is listed in the Network settings of Windows, so if you set one higher than the other, it'll know to use one in preference of the other.

4. In Windows, remember to disable the check for Matching Packets, as otherwise the system can be woken by all sorts of signals hitting the WOL NIC.

That's pretty much most of what I remember when setting up my rigs lately. BUt yeah, should be fairly simple. I personally use a Powershell script that fires a WOL call to a specific MAC address on the local network to wake that system up instead of using an app. But either should work.
Click to expand...
Extremely helpful! And possibly uncovered some of the root causes of my previous issues lol. Thanks man. Will take a look once my 3M IEC extension comes lol.
 
After reading all the comments; I think I may just use a "startup once power is restored" BIOS setting and a smart plug, lol.
 
Vimes said:
My HP N54L had been using it's 1Gb LAN for years and worked fine with WOL.
I have very recently bought 2.5Gb LAN cards, Realtek chipset, and fitted one of those to the HP.
That works a treat for the WOL function when I selected it within the device manager to wake up, only from magic packets.

I have the set on a timer to wake, and sleep, or manually do it via a WOL magic packet sender from my main PC.
Click to expand...
What app are you using to send the packet?
 
Had a quick play earlier. Downloaded the WolOn App for Android to simplify things. The ASRock B650M-HDV/M.2 2.5Gb LAN worked a treat. There are about 4 settings in the controller properties so I just whacked everything to 11.

The MSI Gaming7 board with the Killer NIC isn't behaving as well - pretty sure it had a single WoL setting and it hasn't worked. Will check the BIOS tomorrow.

Thanks chaps - fear of WOL over lol.

Edit: Killer NIC in the Gaming7 board seems to behave when you enable PCI devices to bring the computer out of sleep. Too well infact, had to enable only let this device wake up on a magic packet as it seemed any packet was triggering it to turn on.
 
Last edited by a moderator:
Simon42 said:
Yes turn Wake on pattern match off. Otherwise various network queries and traffic in addition to just the magic packet will wake it up.
Click to expand...
Spot on thank you. Seems to have cured it (y). Working great! Thanks all
 
You must log in or register to reply here.
Back
Top Bottom