by Priya Nakamura Updated Apr 23, 2026
Wake on LAN (WoL) is a networking standard that lets you power on a computer remotely by sending a special network signal — no physical button press required. Our Wake-on-LAN Magic Packet Generator builds the packet from any MAC address with a hex dump. Whether you're accessing a home server from the road or booting a work PC before you arrive at the office, Wake on LAN makes it possible with nothing more than a magic packet and the right configuration. Understanding how it works puts you in control of your hardware from anywhere on the planet.
In this guide you'll learn exactly what Wake on LAN is, how the magic packet works under the hood, and how to set it up step by step on your own network. Because WoL depends heavily on your router's configuration — including port forwarding and a properly assigned static IP address — we'll cover those dependencies so everything clicks into place the first time.
Wake on LAN is an industry-standard networking protocol, originally developed by AMD and IBM in 1996 and later standardized as part of the ATX specification. At its core, WoL relies on the fact that a modern network interface card (NIC) continues to draw a small amount of standby power even when the computer is fully shut down or in sleep mode. This trickle of power — typically supplied by the PSU's 5V standby rail — keeps the NIC alert and listening on the local network segment for a specific trigger signal.
That trigger is called a magic packet. It's a broadcast frame containing a specific byte sequence: six bytes of all 255 (0xFF), followed by the target computer's 48-bit MAC address repeated sixteen times consecutively. The entire payload is 102 bytes. Because the packet is sent to the broadcast address (255.255.255.255 or the subnet's directed broadcast), every device on the local network segment receives it — but only the NIC whose MAC address matches the embedded sequence acts on it by signaling the motherboard to power on.
The magic packet is typically sent over UDP, most commonly on port 9 (the "discard" port) or port 7, though technically it can be delivered on any UDP port since the NIC firmware only inspects the raw payload, not the port number. Because UDP is connectionless and stateless, the sleeping PC doesn't need to maintain any session or respond — the NIC hardware itself intercepts the packet before the OS even loads. This hardware-level interception is what makes Wake on LAN fundamentally different from any software-based remote wake solution.
For Wake on LAN to work across the internet rather than just your local LAN, you need to bridge the gap between the public internet and your home network. Routers don't forward broadcast packets by default, so you either configure your router to forward a directed broadcast to your subnet, or you use a small always-on device (like a Raspberry Pi or NAS) on your local network to receive a regular unicast packet and re-broadcast the magic packet internally. This distinction between local WoL and remote WoL over the internet is the single most common source of confusion for first-time users.
Follow these five steps in order and you'll have a working Wake on LAN setup on your home or office network.
ethtool -s eth0 wol g (replacing eth0 with your interface name) to enable magic packet wake, and add this command to a startup script so it persists across reboots.ipconfig /all — look for the "Physical Address" line under your Ethernet adapter. On Linux or macOS, run ip link or ifconfig. Write down the 12-character hexadecimal address (e.g., A1:B2:C3:D4:E5:F6). You can also use our MAC Lookup Tool to verify the address resolves to your NIC manufacturer.Not all remote wake solutions work the same way. Here's how the main approaches compare so you can pick the right one for your setup.
| Method | Works Remotely | Hardware Required | Difficulty |
|---|---|---|---|
| Wake on LAN (local) | No (LAN only) | WoL-capable NIC | Easy |
| Wake on WAN (port forwarding) | Yes | WoL NIC + router config | Moderate |
| WoL via relay device (Raspberry Pi / NAS) | Yes | Always-on device on LAN | Moderate |
| Intel AMT / vPro Remote Management | Yes | vPro-compatible CPU & motherboard | Advanced |
| Smart power switch / IP-controlled PDU | Yes | Smart PDU or smart plug | Easy (costly) |
Rather than configuring a static IP directly on your PC's network adapter (which can cause conflicts if you move the machine to another network), assign the static address as a DHCP reservation in your router's admin panel. Your router will always hand out the same IP to your PC's MAC address automatically, and your PC's network settings stay on "Obtain IP automatically" — the best of both worlds.
Wake on LAN failures are frustrating because the sleeping PC can't tell you what went wrong. The most common culprit is the BIOS setting being disabled or reset after a firmware update — always double-check BIOS first before digging deeper. The second most common issue is fast startup (also called hybrid shutdown) on Windows 10 and 11, which puts the system into a hibernation-like state that can prevent WoL from functioning correctly; disabling fast startup in Power Options usually resolves this immediately.
For remote WoL failures specifically, verify that your router's port forwarding rule is active and pointing to the correct local IP. Use our Port Checker Tool to confirm UDP port 9 is open and reachable from outside your network. Keep in mind that some ISPs block inbound UDP traffic or place customers behind carrier-grade NAT (CGNAT), which makes standard port forwarding impossible — in this case a VPN or relay service is required. Also check that your PC's MAC address in your WoL app exactly matches the physical address of the wired Ethernet adapter, not a Wi-Fi adapter (WoL over Wi-Fi is unreliable and often unsupported at the hardware level).
Power state matters too. Wake on LAN works from S5 (soft off) and S3 (sleep/suspend) states on most motherboards, but support for waking from S4 (hibernate) varies by hardware. If your PC is fully hibernating and WoL isn't working, try configuring it to sleep (S3) instead. Additionally, some modern motherboards have separate "WoL from S5" settings that must be enabled independently of the standard WoL option.
Pro Tip: Before troubleshooting remote WoL across the internet, first confirm local WoL works perfectly by sending a magic packet from another device on the same Wi-Fi or wired network. Use a free tool like our Ping Test to verify basic network connectivity, then progress to remote testing only after local WoL is confirmed working.
Wake on LAN was originally designed for local area networks, but it can work over the internet with the right router configuration. You need to set up port forwarding on your router to relay the magic packet to your PC's local IP, and your router must support forwarding UDP broadcast packets. An alternative is to use a VPN into your home network, which makes the remote connection behave like a local one.
Yes, in almost all cases Wake on LAN requires a wired Ethernet connection. The NIC must remain powered in standby, and while the Wi-Fi 802.11 standard does define a "Wake on Wireless LAN" (WoWLAN) feature, it is far less reliable and requires specific driver and hardware support. For guaranteed WoL functionality, always use a wired Ethernet connection to your router or switch.
The power draw is minimal — typically between 0.5 and 2 watts — because only the NIC's standby circuitry remains active. Over a month this amounts to less than 1.5 kWh, which costs only a few cents on most electricity tariffs. It's a negligible overhead compared to the convenience of being able to remotely power on your machine.
On Windows, open Command Prompt and run ipconfig /all — the "Physical Address" field under your Ethernet adapter is your MAC address. On macOS, go to System Settings → Network → your Ethernet adapter → Details. On Linux, run ip link show or cat /sys/class/net/eth0/address in a terminal. Make sure you're recording the address for the wired Ethernet adapter, not Wi-Fi.
Standard NAT (used by home routers) is workable with Wake on LAN as long as you configure port forwarding correctly. Carrier-Grade NAT (CGNAT), however, is a shared NAT layer imposed by your ISP that prevents inbound port forwarding entirely — you don't have a unique public IP. In that case, the best solution is a VPN with a fixed endpoint (such as Tailscale or WireGuard) that lets your remote device tunnel into your home network without needing an open inbound port.
Wake on LAN by itself has no authentication — anyone who knows your MAC address and can send a UDP packet to your broadcast address can wake your machine. On a local network this is generally low-risk, but if you've forwarded the WoL port publicly, it's worth pairing the setup with a VPN or firewall rule so only trusted IPs can reach that port. Waking your PC doesn't grant remote access on its own; an attacker would still need separate credentials to log in once it's powered on. Check our Wi-Fi security settings guide for broader network hardening tips.
For authoritative networking standards and specifications, refer to the Internet Assigned Numbers Authority (IANA) or IETF RFC documents.
 |
 |
 |
 |
About Priya Nakamura
Priya Nakamura is a telecommunications engineer and networking educator with a Master degree in Computer Networks and a background in ISP infrastructure design and management. Her experience spans both the technical architecture of broadband networks and the practical challenges home users face when configuring routers, managing wireless coverage, and understanding connectivity standards. At RouterHax, she covers WiFi standards and protocols, networking concepts, IP addressing, and network configuration guides.
Search
Popular Tools
Browse Guides
Promotion for FREE Gifts. Moreover, Free Items here. Disable Ad Blocker to get them all.
Once done, hit any button as below
|
|
|
|
