How do I get wireless Wake-on-Lan work with an Intel 5100 AGN?

Question

How can I make a wireless wol with Intel PRO/Wireless 5100 AGN from a hp laptop ?

Solution

Actually the other answer is quite old and not up to date.

Please use the iw tool.

To check whether it's supported: iw phy0 info

Check the status: iw phy0 wowlan show.

Activate several options: sudo iw phy0 wowlan enable magic-packet disconnect.

The kernel wiki has some information as well. If wake on wlan does not work from suspend mode try freeze mode: Close all applications, then sync && echo freeze | sudo tee /sys/power/state. This is not as low power, but less than a running system and nice to test whether the magic packets at get there and the driver interprets them.

Comments

[Admin]

maybe you wanna look up johnlewis.ie/wake-on-lan-over-wireless

[roy429]

How would I know if it is supported ? I gave you its reference.

[zuberuber]

to check if your chip is supported go to bios and search for wake on lan options.

[roy429]

There is a boot option, and there is a drop down box with 3 options, disabled, network boot or boot order. I have it set to network boot. ethool eth0 shows pg as wol. Why would the kernel version matter if the OS is not even loaded ??

[roy429]

Moreover this site seems to say that magic pacckets for wireless lans don't exist, this one seems to say differently: revolutionwifi.blogspot.fr/2010/11/wake-on-wireless-lan.html From what I understood, the link you mentionned offers to wake up by ping. How would that work, and isn't it a security concern ?

[zuberuber]

WoWL its like WoL, You must ping PC with magic packet. And Why would it be security concern if You can only WoWL and WoL only in local network.

[roy429]

Ok. So what is it that you want me to do exactly? If I try what the link says, the output is sudo ethtool -s eth0 wol u--> Cannot set new wake-on-lan settings: Operation not supported (not setting wol)

[Oxwivi]

@roy429, Are you sure your hardware supports it? zuberuber, please summmarize the content of the link in the answer. It's a StackExchange policy to avoid link rot, thank you.