Does WOL (wake on lan) work for hibernation?

Has anyone attempted to do a wake on lan to a pc that is hibernated?
I would assume this would work but I just don't know.

On 1 Jan 2004 10:10:36 -0800, (E-Mail Removed) (ishtarbgl) wrote:

>Has anyone attempted to do a wake on lan to a pc that is hibernated?
>I would assume this would work but I just don't know.

fwiw, it doesn't work on any of the systems I have that otherwise can be waken
from the Standby state via WOL, keyboard or mouse.

These same systems won't be waken by keyboard or mouse from Hibernate, either,
so my assumption is the prevailing implementation is not to support WOL from
Hibernate...

/daytripper

"daytripper" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> fwiw, it doesn't work on any of the systems I have that otherwise can be
waken
> from the Standby state via WOL, keyboard or mouse.
>
> These same systems won't be waken by keyboard or mouse from Hibernate,
either,
> so my assumption is the prevailing implementation is not to support WOL
from
> Hibernate...

How exactly does the WOL function work anyways? What is the special signal
that is sent that wakes a computer from standby?

Yousuf Khan

On Fri, 02 Jan 2004 00:11:51 GMT, "Yousuf Khan"
<(E-Mail Removed) > wrote:

>"daytripper" <(E-Mail Removed)> wrote in message
>news:(E-Mail Removed).. .
>> fwiw, it doesn't work on any of the systems I have that otherwise can be
>waken
>> from the Standby state via WOL, keyboard or mouse.
>>
>> These same systems won't be waken by keyboard or mouse from Hibernate,
>either,
>> so my assumption is the prevailing implementation is not to support WOL
>from
>> Hibernate...
>
>How exactly does the WOL function work anyways? What is the special signal
>that is sent that wakes a computer from standby?
>
> Yousuf Khan

WOL utilizes a "magic packet" sent across a network by a management station to
the nic within the snoozing system. If the nic spots such a packet it triggers
the host system to return to the fully-powered state and proceed through POST
and boot. Finally, during the boot process the OS tests a "magic cookie" to
determine if the system is returning from the Stand By state (as opposed to a
Hibernate or a fully-powered down state).

Hardware implementation depends on the platform and the nic, but pre-PCI PME#
implementations depend on a three-wire cable connected from nic to a dedicated
WOL/WOR (Wake On modem Ring) header on the motherboard. NICs and host systems
that support PME# can communicate through a that dedicated bus signal and thus
require no special cable.

Beyond that, it means that enough of the nic (and the host "turn-on" logic)
has to be powered by the system's "stand-by" power rails to be able to
recognize a "magic packet" aimed at that specific nic even while the bulk of
the system power has been removed...

/daytripper

"daytripper" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> WOL utilizes a "magic packet" sent across a network by a management
station to
> the nic within the snoozing system. If the nic spots such a packet it
triggers
> the host system to return to the fully-powered state and proceed through
POST
> and boot. Finally, during the boot process the OS tests a "magic cookie"
to
> determine if the system is returning from the Stand By state (as opposed
to a
> Hibernate or a fully-powered down state).

Well, if I wanted to be taught about magic packets and stuff, then I
wouldn't have even asked in this newsgroup, I'd have just asked in
alt.folklore.urban. :-)

Anyways, I think I found the information in here:

http://gsd.di.uminho.pt/jpo/software...o-2.html#ss2.1

Yousuf Khan

On Fri, 02 Jan 2004 07:24:55 GMT, "Yousuf Khan"
<(E-Mail Removed) > wrote:

>"daytripper" <(E-Mail Removed)> wrote in message
>news:(E-Mail Removed).. .
>> WOL utilizes a "magic packet" sent across a network by a management
>> station to the nic within the snoozing system. If the nic spots such a packet it
>> triggers the host system to return to the fully-powered state and proceed through
>> POST and boot. Finally, during the boot process the OS tests a "magic cookie"
>> to determine if the system is returning from the Stand By state (as opposed
>> to a Hibernate or a fully-powered down state).
>
>Well, if I wanted to be taught about magic packets and stuff, then I
>wouldn't have even asked in this newsgroup, I'd have just asked in
>alt.folklore.urban. :-)

<yawn> I'll be sure to note that the next time you ask such an open-ended
question on a networking group, like this beauty:

>>>How exactly does the WOL function work anyways? What is the special signal
>>>that is sent that wakes a computer from standby?

Yeah, that's a well-bounded query alright :-p

>Anyways, I think I found the information in here:
>
>http://gsd.di.uminho.pt/jpo/software...o-2.html#ss2.1

And the information provided therein differs from what I already provided you
- how?

/daytripper (who now wonders what the point was...)

"daytripper" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> >Anyways, I think I found the information in here:
> >
>
>http://gsd.di.uminho.pt/jpo/software...l-mini-howto-2.
html#ss2.1
>
> And the information provided therein differs from what I already provided
you
> - how?

It tells you what is contained within the magic packet.

Yousuf Khan

On Fri, 02 Jan 2004 19:40:15 GMT, "Yousuf Khan"
<(E-Mail Removed) > wrote:

>"daytripper" <(E-Mail Removed)> wrote in message
>news:(E-Mail Removed).. .
>> >Anyways, I think I found the information in here:
>> >
>>
>>http://gsd.di.uminho.pt/jpo/software...l-mini-howto-2.
>html#ss2.1
>>
>> And the information provided therein differs from what I already provided
>you
>> - how?
>
>It tells you what is contained within the magic packet.
>
> Yousuf Khan

Of course, it should have been obvious that's what you were looking for ;-)

/daytripper

"daytripper" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Of course, it should have been obvious that's what you were looking for
;-)

Actually, now I gotta wonder, I gotta a typical WiFi router with Ethernet
connections too. I wonder if WOL can be used between the WiFi and Ethernet
parts of the network? I tried sending a WOL signal from my wireless laptop
to my wired desktop. Didn't wake it up.

Actually maybe another related question. Would a motherboard Ethernet
automatically be capable of WOL, I mean without requiring a special cable?

Yousuf Khan

On Sat, 03 Jan 2004 21:27:05 GMT, "Yousuf Khan"
<(E-Mail Removed) > wrote:

>"daytripper" <(E-Mail Removed)> wrote in message
>news:(E-Mail Removed).. .
>> Of course, it should have been obvious that's what you were looking for
>;-)
>
>Actually, now I gotta wonder, I gotta a typical WiFi router with Ethernet
>connections too. I wonder if WOL can be used between the WiFi and Ethernet
>parts of the network? I tried sending a WOL signal from my wireless laptop
>to my wired desktop. Didn't wake it up.

at the risk of competing with alt.folklore.urban...

can you wake the desktop up from a wired system?

I have a laptop using a netgear 802.11a nic, and the companion netgear WAP is
plugged into a lan port on my linksys router. I just tried your experiment and
can WOL my wired systems just fine from the wireless laptop. I use a freebie
applet (MC-WOL.exe) to generate the magic packet and aim it at the wired nic's
MAC address, and it works just like it does when I run the same applet from
one of my wired nodes.

>Actually maybe another related question. Would a motherboard Ethernet
>automatically be capable of WOL, I mean without requiring a special cable?

It'd be a rare current or even recent generation desktop motherboard that had
an embedded network adapter but didn't *support* WOL. That's not "automatic"
but close to it.

You get WOL nearly for free if you design the motherboard to support the rest
of Microsoft's definitions for standby operation. The additional WOL circuitry
is trivial (basically, it's a nic chip output wired to an otherwise unused SIO
GPIO input, and then connecting certain nic chip power pins to the standby
voltage rail instead of the "normal" voltage source) and the rest is simply
rom bios code...

It's probably not enabled by default, either. You would likely have to enable
WOL via the system cmos setup utility, and set the appropriate nic driver
switch(es)...

/daytripper