Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000007 (7) drv probe link Link detected: yes after manual configuration: ethtool -s enp0s25 speed 100 duplex full autoneg on mdix on interface still invalid. Than i try this: ethtool -s enp0s25 speed 10 duplex full autoneg on mdix on Magic, it acquired IP address. The target computer's motherboard and Network Interface Controller have to support Wake-on-LAN. The target computer has to be physically connected (with a cable) to a router or to the source computer for WoL to work properly. Some wireless cards have support for Wake on Wireless (WoWLAN or WoW).
Translation(s): English - Brazilian Portuguese - Español - Français - Italiano - Русский
Some notes on getting the Wake On LAN (WOL) feature to work with a Debian system.
Contents
- Wake On LAN
Hardware
Your first step towards booting your computer from over the network is to make sure your Ethernet card and mother board support some type of Wake On LAN feature. Notably 3Com's -NM (non managed) cards do not support WOL while their -M (managed) cards do.
There are two main systems. The older method uses a Wake On LAN three pin connector between your Ethernet card and your main board. Both headers are usually labelled 'wol'. The newer system uses a Wake On LAN pin on the PCI bus, negating the need for the cable. Some main boards support both and only provide the header for backwards compatibility with Ethernet cards that don't support the PCI pin.
Recent motherboards with onboard NICs support Wake On LAN without the need for any pins/cables.
Firmware / BIOS
Supports Wake On Lan Pumbg
In a nice BIOS under power management you will have a clear, intuitive option labeled 'Wake On LAN'. Unfortunately my system wasn't so clear and has a couple options available. One seems to always work, the other sometimes works. I built upon the information shared by Mark Ivey since I also have a Shuttle XPC SK41G and am using the 'PowerOn by PCI Card' option with success.1
Software
Interface setup
stretch
add this file
reboot. Check if it worked with
Wake-on: g means it worked
Squeeze
As of Squeezeethtool parameters can be set directly from /etc/network/interfaces. The above can be achieved like this:
The script /etc/network/if-up.d/ethtool will then take care of calling ethtool on ifup. See /usr/share/doc/ethtool/README.Debian for more information.
Supports Wake-on: Pubg
You can then power down your system, and prepare the other system to wake it.
Before squeeze
After activating Wake On LAN in hardware it is also necessary to activate it in software. This is done using ethtool, which tells the interface to respond to the magic packet. Replace eth0 with your network interface device name:
This can be automated by editing /etc/network/interfaces:
This runs ethtool after every time eth0 is brought up, and also after it is brought down, so WOL should work even if the network is not brought down correctly.
Sending WOL messages
I installed the etherwake package in the controlling system for the etherwake command to send the 'Magic Packet' to my computer to wake it up. The program must be run as root to send the packet (I use sudo to execute it).
wakeonlan is also available, a program that uses UDP packets not TCP, and hence does not need to be run as root. It is also slightly more configurable.
WOL Sensitivity
I found that I didn't want any of the Wake On LAN settings except Wake on 'Magic Packet' (g). I only wanted my machine to turn on when I specifically told it to, not on unicast messages (u), broadcast messages (b) or multicast messages (m).
However, if you do want Wake On LAN on any of these events (other than 'Magic Packet'), you may find conflicts with pm-utils2. At the time of writing, scripts in this package will set the wake option for all relevant interface cards to 'Magic Packet' only, (g). This will be a problem if you want your machine to wake 'on-demand', when it receives traffic (u), for example. The issue and a fix is discussed below.
WOL Persistence
Hardware looks up to spec, you think the BIOS is set right, but it still doesn't work without some tweaking using the software. According to the Wake On Lan client FAQ most Linux drivers disable the WOL feature on boot3, so we need to get it going.
Kernel 2.6
With a 2.6 kernel we're using /etc/modprobe.d. You may be using /etc/modprobe.conf, but if it's not including /etc/modprobe.d you're probably getting told about that each time you boot and some stuff may not be configured properly. I'm using /etc/modprobe.d and I added a file local.conf into the directory. It says:
ethtool comes from the ethtool package, so you'll need to install that unless your card supports a load option to set WOL. If that's the case I'd make an local.conf file with the appropriate options line, maybe something like:
If your kernel uses an initramfs image (eg. Debian stock kernels), also run update-initramfs -u (or update-initramfs -u -k all if necessary) to rebuild kernel initial ramdisk(s).
Testing on another machine with a C3905B-TXNM and a 3C905C-TXM that uses the 3c59x module to drive them both I found that ethtool was unable to query them or set the WOL setting, but that the enable_wol=1 setting did work and was required.
While I was messing with these settings, I noticed that both 8139too and 8139cp were loading, but loading just 8139cp alone failed since my chipset isn't new enough so I blacklisted it.
Debugging state with ethtool
After an hour struggling with why my system still didn't work I started throwing in the ethtool query command all over the place to see what the deal was:
ifup
I found that (at least with my 8139too driver on Debian 3.1/Sarge) the install line was working when I'd modprobe 8139too, but ifup also resets the WOL setting, so I added an up line to /etc/network/interfaces under eth0:
I kept the ethtool command in /etc/modprobe.d/local.conf in case I boot and ifup isn't executed before shutting down.
PM-Utils Conflicts
The pm-utils package contains scripts that are run on suspend, hibernate and on resume of the system. There is one script, /usr/lib/pmutils/power.d/disable_wol, which sets the configuration for interfaces to only wake on 'Magic Packet' (g), regardless of the settings you may have configured in /etc/network/interfaces (or one of the files under /etc/network/interfaces.d, or manually using ethtool or in some other way). Look for lines in the file similar to the following:
Obviously, if you have set an interface to Wake on LAN in the event of a unicast packet or 'Magic Packet' (ug), then suspend using pm-suspend, for example, this script will set the interface to 'Magic Packet' only (g) as part of the suspension process.
You can detect the problem, once you know what you're looking for, by noticing through ethtool after a resume that the 'Wake-on' settings for interfaces have been set to 'g'.
A simple fix (that will not interfere with package updates) is to add a file with the same name, disable_wol to the local configuration directory, /etc/pm/power.d/. This overrides the script in /usr/lib/pm-utils/power.d/disable_wol.
This is my (somewhat verbose, and functionally trivial) /etc/pm/power.d/disable_wol:
Conclusion
Wake On LAN works on Debian and opens some new options up to me.
I can log into my gateway and boot my desktop, grab what I need and then power it back off remotely. I'm using DHCP with MAC-to-IP mappings so I can look in that file on my gateway system to know the MAC address of the system I wish to wake up. If I didn't have that I could keep a text file.
My next feat is to have non-essential systems power-off (not just halt) on a power outage to extend the battery runtime for the essential systems and then use WOL to power the other systems back on after power is restored and the battery has hit some specific charge level. I think some settings with halt or APM or ACPI are not right on those systems. See OffAndOnAgain.
External Links
Using Wake-On-LAN WOL/PME to power up your computer remotely
http://xlife.zuavra.net/index.php/60/ethtool(8)
etherwake(8)
wakeonlan(1)
pm-suspend(8)
CategoryNetwork | CategorySystemAdministration
Getting Wake-On-Lan to work with a Shuttle SK41G and Mandrake Linux 9.1 (1)
https://packages.debian.org/search?keywords=pm-utils (2)
http://ahh.sourceforge.net/wol/faq.html (3)
This post shows the steps required to set up Wake-on-LAN (WOL) on a 15-year-oldcomputer running CentOS 7. I can imagine that different hardware configurationsmight need less or different steps.
First of all, make sure that your network interface card supports WOL. In thefollowing, I will assume that the NIC is called enp1s4. Run
If the output contains the g option, your card supports waking up on theMagicPacket.
You can manually enable WOL by running sudo ethtool -s enp1s4 wol g. However,with my setup,the option was reset every time I rebooted. From what I read online, it waspossible to append a line with ETHTOOL_OPTS to/etc/sysconfig/network-scripts/ifcfg-enp1s4 to make the option persistent.Unfortunately, nowadays, it seems like this method does not work anymore.
The only method I found that worked on my computer is the one from Zivo NiXBLog.The idea is to create a service which enables WOL and configure the service to beexecuted once the NIC is ready.
Here are the steps.
Create the file /etc/udev/rules.d/99-wakeonlan and add the following line.
This adds a udev rule for the network interface card. When the card becomesonline, a new service called wakeonlan is executed.
Then, create the file /usr/lib/systemd/systemd-wakeonlan, add
and make the file executable.
Finally, we need to create the service/usr/lib/systemd/system/wakeonlan.service with the following content.
and enable it.
These steps deviate from the ones in the linked document. The sourcedisabled WOL again when the service is stopped. With my setup, service wasstopped every time I shut down the computer, which defied the propose of WOL.The service described above does nothing when the service is stopped.
With my old mainboard, I had to enable the Resume On PME# option. The namingof the option depends on the mainboard manufacturer.
Shutdown the computer and log in at another computer in the same link-localnetwork. On Ubuntu, you can send the magic packet using the wakeonlan tool
On another CentOS 7 machine, you can use ether-wake from the net-tools package.