Networking

What is wake-on-LAN?

Wake-on-LAN (WoL) is a networking standard that allows a computer to be powered on or awakened from a low-power state by sending a specially crafted network message called a magic packet.

What Is Wake-on-LAN?

Wake-on-LAN (WoL) is an Ethernet networking standard that enables a computer in a sleep, hibernate, or powered-off state (soft off) to be remotely turned on or resumed by another device on the network. Instead of physically pressing a power button, an administrator or automated system sends a special network frame—known as a magic packet—to the target machine's network interface, triggering it to boot or wake.

WoL matters because it allows IT departments to manage machines that would otherwise need to be left running around the clock. This supports energy savings, remote administration, scheduled maintenance, and off-hours software deployment without requiring physical access to each device.

How Wake-on-LAN Works

The technology relies on the network interface card (NIC) remaining partially powered even when the rest of the computer is off. This standby power (often supplied via the motherboard from the PSU's +5V standby rail) keeps the NIC listening for incoming traffic.

The Magic Packet

The core of WoL is the magic packet. This is a broadcast frame containing a specific pattern:

  • 6 bytes of all 255 (FF FF FF FF FF FF) at the start.
  • Followed by the target machine's 48-bit MAC address repeated 16 times (96 bytes total).

When the listening NIC detects this pattern matching its own MAC address, it signals the motherboard to power on the system.

Delivery Methods

  1. Layer 2 broadcast: The magic packet is typically sent as a broadcast to the local subnet, often over UDP ports 7 or 9.
  2. Directed broadcast/subnet-directed: For waking machines on remote subnets, routers must be configured to forward directed broadcasts—often disabled by default for security reasons.
  3. WoL over the Internet: Requires port forwarding or a relay device, since MAC addresses are not routable across the internet.

Requirements and Configuration

Successfully using WoL requires coordination across hardware, firmware, and operating system settings:

  • NIC support: The network adapter must support WoL and be connected via a wired Ethernet link (traditional WoL does not work reliably over Wi-Fi, though WoWLAN exists).
  • BIOS/UEFI setting: Options like Wake on LAN, Power On by PCIe, or Resume by PCI-E Device must be enabled.
  • Operating system driver: In Windows, the adapter's power management properties must allow the device to wake the computer and respond to magic packets. In Linux, tools like ethtool configure this (e.g., ethtool -s eth0 wol g).
  • Power supply: Standby power must be available, so the PSU and power settings must not fully cut power to the NIC.
Note: Some fast-startup or deep-sleep power states (such as Windows Fast Startup or certain ACPI S5 states) can prevent WoL from functioning. Disabling Fast Startup often resolves WoL failures.

Common Use Cases

  • Remote administration: IT staff wake machines to apply patches, run backups, or perform maintenance during off-hours.
  • Energy conservation: Computers can sleep when idle and be woken only when needed, reducing power consumption.
  • Software deployment: Management platforms like Microsoft Endpoint Configuration Manager (SCCM) use WoL to push updates to sleeping endpoints.
  • Home media and file servers: Users wake a NAS or media PC remotely to access files without leaving it running constantly.
  • Remote desktop access: Wake a workstation before connecting via RDP, VPN, or remote desktop tools.

Security Considerations

Because WoL uses only a MAC address and no authentication in its basic form, it can pose security concerns:

  • Unauthenticated wake: Anyone on the local network who knows a target's MAC address can wake it. This is a minor risk but should be considered in high-security environments.
  • SecureOn: Some NICs support a password (SecureOn) appended to the magic packet to add basic authentication.
  • Directed broadcasts: Enabling subnet-directed broadcasts for cross-subnet WoL can open networks to smurf-style amplification attacks, so it should be used cautiously.
  • Segmentation: Restrict WoL traffic to management VLANs where possible.

Best Practices

  1. Document the MAC addresses of managed devices to simplify sending magic packets.
  2. Use wired Ethernet connections for reliable WoL functionality.
  3. Disable Fast Startup and verify NIC power management settings when troubleshooting.
  4. Test WoL after any firmware or driver updates, as they can reset power settings.
  5. For remote/internet wake, use a VPN or a management appliance rather than exposing broadcast forwarding directly.

Related Technologies

Wake-on-Wireless-LAN (WoWLAN) extends the concept to Wi-Fi adapters, though support is limited. Wake-on-Pattern and Wake-on-Ring are related power-management features that wake systems based on specific packet patterns or modem activity, respectively.

Real-World Example

Consider an enterprise that needs to install a critical security patch on 500 desktops overnight. Rather than requiring employees to leave computers on, the IT team schedules the deployment tool to send magic packets at 2 a.m., waking all machines, installing the patch, and letting them return to sleep—saving electricity while ensuring compliance.

Studying for CompTIA (Networking)?

ExamWizardz turns the official objectives into a guided study plan — with practice tests, real PBQs, and a readiness score. Join the waitlist to be first in when CompTIA A+ launches.