Wake on lan settings in ethtool
 

Hi all,

Im trying to remote power on my debian machine with gnome with the wake on lan function.

I enabled it on my mainboard and was configuring my ethtool.

There i see:
root@lappy:~# ethtool eth0
Settings for eth0:
Supports Wake-on: g
Wake-on: d
Link detected: yes

and after this command ethtool -s eth0 wol g

i get this:
root@lappy:~# ethtool eth0
Settings for eth0:
Supports Wake-on: g
Wake-on: g
Link detected: yes

So i enabled it on software and hardware. Now im trying to sent the magic packets with a windows tool "wake on lan"
I see that the package has been sent but the pc wont turn on. So when i check the ethtool settings again i see that it turned to:

Wake-on: d

What am i missing?

WOL seems to be broken in the kernel at the moment.
Search for WOL broken Kernel
The problem seems to be that when your computer shuts down, it fully shuts down your LAN card, so it is no longer listening for the magic packet.
There have been some "workarounds" posted, but none of them worked for me :(

Put this in "/etc/network/if-up.d/wol-enable"

make it executable.

hello i have applied these changes and WOL is working fine when i used it to wake my machine from turn off mode....

But it is not working when i switches my machine to sleep mode. My machine is not responding to magic packet sent , if it is in sleep mode. Also this all happens with ubuntu only .....If i go to sleep mode through Windows 7 ultimate. Then my machine can detect the magic packet and resume all the state of machine as earlier.

Can WOL for sleep/suspend/hibernate is possible in ubuntu......if yes do we require some more changes and what are those changes required.

please reply.

sipu123;

Please do not make multiple posts with the same question. In this case, you have stated "I have applied these changes" in response to 4 different threads---I'm not goin to check in detail, but I doubt that this really fits all four.

Normally, you should start a new thread with a new question (but search first, and make reference to other relevant threads.)

Reported