64
edits
Changes
From Amahi Wiki
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..."
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</code>
The output will look similar to this:
<code>
[root@localhost ~]# ethtool eth0<br>
Settings for eth0:<br>
Supported ports: [ TP MII ]<br>
Supported link modes: 10baseT/Half 10baseT/Full <br>
100baseT/Half 100baseT/Full <br>
1000baseT/Half 1000baseT/Full <br>
Supports auto-negotiation: Yes<br>
Advertised link modes: 10baseT/Half 10baseT/Full <br>
100baseT/Half 100baseT/Full <br>
1000baseT/Half 1000baseT/Full <br>
Advertised auto-negotiation: Yes<br>
Speed: 1000Mb/s<br>
Duplex: Full<br>
Port: MII<br>
PHYAD: 0<br>
Transceiver: internal<br>
Auto-negotiation: on<br>
Supports Wake-on: pumbg<br>
Wake-on: g<br>
Current message level: 0x00000033 (51)<br>
Link detected: yes<br>
</code>
3. Look for a line similar to this:
<code>Wake-on: g</code>
This means that WOL by magic packets is enabled on that interface.
If the line is
<code>Wake-on: d</code>
then WOL is disabled. Activate it by running <code>ethtool -s eth1 wol g</code>
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 <code>ethtool eth0</code> 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.
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</code>
The output will look similar to this:
<code>
[root@localhost ~]# ethtool eth0<br>
Settings for eth0:<br>
Supported ports: [ TP MII ]<br>
Supported link modes: 10baseT/Half 10baseT/Full <br>
100baseT/Half 100baseT/Full <br>
1000baseT/Half 1000baseT/Full <br>
Supports auto-negotiation: Yes<br>
Advertised link modes: 10baseT/Half 10baseT/Full <br>
100baseT/Half 100baseT/Full <br>
1000baseT/Half 1000baseT/Full <br>
Advertised auto-negotiation: Yes<br>
Speed: 1000Mb/s<br>
Duplex: Full<br>
Port: MII<br>
PHYAD: 0<br>
Transceiver: internal<br>
Auto-negotiation: on<br>
Supports Wake-on: pumbg<br>
Wake-on: g<br>
Current message level: 0x00000033 (51)<br>
Link detected: yes<br>
</code>
3. Look for a line similar to this:
<code>Wake-on: g</code>
This means that WOL by magic packets is enabled on that interface.
If the line is
<code>Wake-on: d</code>
then WOL is disabled. Activate it by running <code>ethtool -s eth1 wol g</code>
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 <code>ethtool eth0</code> 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.
