Two-step WoL Setup

It doesn’t matter what operating system the computer eventually boots into (Windows, Mac, Ubuntu, or another Linux distribution), Wake-on-LAN can turn on any computer that receives the magic packet. The computer hardware must support Wake-on-LAN with a compatible BIOS and network interface card. Enabling Wake-on-LAN is done in two steps. The first sets up the motherboard by configuring Wake-on-LAN through BIOS before the operating system boots, and the second logs into the operating system and makes changes there. The first step with the BIOS is valid for every computer, but after following the BIOS setup, skip to your operating system instructions, whether it be for Windows, Mac, or Linux.

Step 1: BIOS Setup

The first thing you need to do to enable WoL is to set up BIOS correctly so that the software can listen for incoming wake up requests.

Step 2: Windows WoL Setup

Windows Wake-on-LAN is set up through Device Manager. There are a few different settings to enable here: Most BIOS screens have a help section off to the side that describes what each setting does when enabled. It’s possible that the name of the WoL option in your computer’s BIOS isn’t clear.

Step 2: macOS Wake-on-Demand Setup

Mac Wake-on-Demand should be enabled by default in version 10.6 or later. Otherwise, follow these steps:

Step 2: Linux WoL Setup

The steps for turning on Wake-on-LAN for Linux are most likely not the same for every Linux OS, but here’s how to do it in Ubuntu: See this Synology Router Manager help article if you need additional help setting up a Synology router with Wake-on-LAN. Look for the Supports Wake on value. If there’s a g there, then Wake-on-LAN can be enabled.

How to Use Wake-on-LAN

Now that the computer is set up to use Wake-on-LAN, you need a program that can send the magic packet required to instigate the startup. TeamViewer is one example of a free remote access tool that supports Wake-on-LAN. Since TeamViewer is made specifically for remote access, its WoL function is handy when you need into your computer while away but forgot to turn it on before you left. TeamViewer can use Wake-on-LAN in two ways. One is through the network’s public IP address, and the other is through another TeamViewer account on the same network (assuming the other computer is on). This lets you wake the computer without configuring router ports since the other local computer that has TeamViewer installed can relay the WoL request internally. Another great Wake-on-LAN tool is Depicus, and it works from a variety of places. You can use their WoL feature through their website without downloading anything, but they also have a GUI and command-line tool available for Windows (for free) and macOS, plus Wake-on-LAN mobile apps for Android and iOS. Other free Wake-on-LAN apps include Wake On LAN for Android and RemoteBoot WOL for iOS. WakeOnLan is another free WoL tool for macOS, and Windows users can opt for Wake On Lan Magic Packets or WakeMeOnLan. One Wake-on-LAN tool that runs on Ubuntu is called powerwake. Install it with the following command: Once installed, enter powerwake followed by the IP address or hostname that should be turned on, like this: or:

Wake-on-LAN Troubleshooting

If you followed the steps above, found that your hardware supports Wake-on-LAN without any issues, but it doesn’t work when you try to turn on the computer, you might need to enable it through your router. To do this, log into your router to make some changes. The magic packet that turns on the computer is normally sent as a UDP datagram over port 7 or 9. If this is the case with the program you use to send the packet, and you’re trying this from outside the network, open those ports on the router and forward requests to every IP address on the network. Forwarding WoL magic packets to a specific client IP address would be pointless since the powered down computer doesn’t have an active IP address. However, since a specific IP address is necessary when forwarding ports, make sure the ports are forwarded to the broadcast address so that it reaches every client computer. This address is in the format ..*.255. For example, if you determine your router’s IP address to be 192.168.1.1, then use the 192.168.1.255 address as the forwarding port. If it’s 192.168.2.1, use 192.168.2.255. The same is true for other addresses like 10.0.0.2, which would use the 10.0.0.255 IP address as the forwarding address. You might also consider subscribing to a dynamic DNS (DDNS) service like No-IP. That way, if the IP address tied to the WoL network changes, the DNS service updates to reflect that change and still lets you wake up the computer. The DDNS service is only helpful when turning your computer on from outside the network, like from your smartphone when you’re not home.

More Information on Wake-on-LAN

The standard magic packet used to wake a computer works below the Internet Protocol layer, so it’s usually unnecessary to specify IP address or DNS information. A MAC address is normally required, instead. However, this isn’t always the case, and sometimes a subnet mask is needed. The typical magic packet also does not return with a message indicating whether it successfully reached the client and turned on the computer. What normally happens is that you wait several minutes after the packet is sent, and then check whether the computer is on by doing whatever it is you wanted to do with the computer once it was powered on.

Wake on Wireless LAN (WoWLAN)

Most laptops do not support Wake-on-LAN for Wi-Fi, officially called Wake on Wireless LAN, or WoWLAN. The ones that do need to have BIOS support for Wake-on-LAN and need to use Intel Centrino Process Technology or newer. The reason most wireless network cards don’t support WoL over Wi-Fi is that the magic packet is sent to the network card when it’s in a low power state. A laptop (or wireless-only desktop) that isn’t authenticated with the network and is shut down has no way to listen for the magic packet, and won’t know if one is sent over the network. For most computers, Wake-on-LAN works over Wi-Fi only if the wireless device is the one sending the WoL request. In other words, it works if the laptop, tablet, phone, or other device is waking up a computer, but not the other way around.