Difference between revisions of "Enabling WOL"
(Created page with "To enable Wake-On-Lan (WOL) on your hda: 1. Open a terminal and execute <code>su</code> to get root access 2. Assuming your LAN interface is on eth0, run <code>ethtool eth0</co...") |
(No difference)
|
Revision as of 20:30, 18 January 2011
To enable Wake-On-Lan (WOL) on your hda:
1. Open a terminal and execute su
to get root access
2. Assuming your LAN interface is on eth0, run ethtool eth0
The output will look similar to this:
[root@localhost ~]# ethtool eth0
Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: MII
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000033 (51)
Link detected: yes
3. Look for a line similar to this:
Wake-on: g
This means that WOL by magic packets is enabled on that interface.
If the line is
Wake-on: d
then WOL is disabled. Activate it by running ethtool -s eth1 wol g
If you don't find any line containing Wake-on at all, then your interface card doesn't support WOL, or the OS cannot detect it.
Check the ethtool man pages for a full explanation of the Wake-on options
- Note: Some legacy drivers forget the setting during boot. Run
ethtool eth0
again if you suspect this is the case
- Reference: See this link http://www.energystar.gov/index.cfm?c=power_mgt.pr_power_mgt_wol for a general explanation of WOL.