My first thought was to simply start broadcasting WOL magic packets over the network, but my Raspberry Pi is not waking up. So I'm assuming it either doesn't support WOL, or I haven't properly configured it.
What do I have to do to enable Wake-on-LAN?
It doesn't support WoL.
Considering the device draws so little power, the benefits of shutting it of and waking it with WoL are few and far between. Just leave it on!
I beg to differ. If you dig a bit deeper you find out the LAN micro chip, which incidentally is also the 2 port USB hub.
The manufacturer of the LAN microchip clearly says in their specifications the there is WoL on the LAN module.
Ethernet features: 10/100 Ethernet controller supports numerous power management wakeup features, including Magic Packet™, Wake-on LAN (WOL) and Link Status Change.
Now how you use it is another question. End of the day as long as there is power connected to Raspberry Pi (even if it off state or sleeping), you can use the WoL with out problem.
I know the other answers say you cannot shut down or sleep the Raspberry Pi (maybe with existing OS's), but the answer is still there is WoL in the LAN Module and that is a fact.
One thing to cry about if the fact that PoE has been omitted, but luckily Raspberrians questioned this fact and it turns out.. they just forgot about it.. oops.
Is power over Ethernet (PoE) possible?
Not in the base device, but it’s been a very commonly requested feature, so we’re examining options for later releases.
Somewhere on their blog they admitted to forgetting about it.. cannot find it now.
The RPi doesn't need Wake On Lan.
If it's connected to the power supply then it's on. There is no suspend or hibernation.
If it's not connected to the power supply, then it's definitely not going to turn on.
I'm facing the same issue for a long time. But I use a trick to WOL my Raspberry Pi's (I use several RPi's in the museum where I work). I tackled the issue using an inexpensive ethernet power relay.
Here is my trick: I connect an ETH002 board (from Devantech) to the network. Power of the RPi is connected through the output NC (Normally Closed) of a relay. As the relay is normally closed, when main power is switched ON, both systems start up.
When I send a "sudo halt" command to the RPi, this goes off. To wake it again, I send the following command to the relays board (assuming the Relay 1 is in use):
//deactivate relay 1
PacketSender\PacketSender.exe -txw 500 IPaddress 17494 "21 01 00"
// wait some seconds...
//reactivate relay 1
PacketSender\PacketSender.exe -txw 500 IPaddress 17494 "20 01 00"
where IPaddress is the IP address of the relays board and port 17494 by default.
-- PacketSender is a very good freeware, Thanks to the developer --
Doing so, I completely switch off the RPi and power it on again. e.g when there is an evening event in the museum. Looks like WOL.
That 's it! Et voila!
Regards to all,
Yvan.
You can use PoE with the pi, use a PoE switch and a PoE splitter at the pi end. Works well and with a smarter, yet more expensive switch, you can reset the port to power cycle the pi.
It would be nice to use WOL on the pi, but not seeing any input on anyone getting that to work, even though the nic chip will "support" it.
RPi gets power from a normal phone charger like a old PC AT power supply where you need to manually power on and off. For this reason pi cannot power cycle itself and functions like WoL cannot work.
I'm no expert, but if the ethernet chip is also the controller for the USB ports, the answer may be to get power via the main USB ports for the PI via a USB hub that support power back-feed.
