Wake-On-LAN demystified: magic packets, MAC repeats, and the limits of network wake-ups

April 15, 2026
Dynamic image of a wakeboarder creating a splash on a lake in a city park setting.
Photo by Alix Lee on Pexels

What the post covers

A recent Hacker News-linked blog post on xaner.dev takes a clear run at Wake-On-LAN (WOL), the humble trick admins use to power up machines remotely. It has been reported that the author focuses on the technical implementation of how WOL actually wakes a machine and plans a follow-up showing how to enable it in BIOS and operating systems. Practical use cases are familiar: after-hours backups, power-saving fleets, or sleepy rendering rigs that only need to be alive when crunching.

The magic behind the Magic Packet

At the heart of WOL is the so‑called Magic Packet: a specific byte pattern that a network interface watches for even when the host is asleep. The packet begins with six 0xFF bytes as a sync stream, followed by the target MAC address repeated 16 times with no separators — that repetition is the IEEE-ish trick that tells the NIC, “this one’s for me.” Some Magic Packet variants also include a password field; allegedly not every BIOS honours that extra protection. The blog even shows a Wireshark capture and raw hex dump so you can see the sequence with your own eyes.

How it’s sent — and where it breaks down

Sending the packet is simple: you don’t need the full TCP/IP stack on the receiving side, so most tools just blast the payload in a UDP datagram to the broadcast address (255.255.255.255 for IPv4) — ports 7 and 9 are common targets. IPv6, of course, uses multicast instead of broadcast. But there are hard limits: WOL typically won’t cross VLANs or different networks, you must already know the target’s MAC address, and it generally requires a wired Ethernet connection (Wi‑Fi NICs usually sleep too deep). And no, you don’t get a receipt — there’s no guaranteed acknowledgement that the machine woke.

Takeaway

Not a magic wand — more a very useful tap. It has been reported that the author also provides a Golang implementation example and will follow up with configuration steps, which should be handy for sysadmins and tinkerers. If you’ve ever wanted to flip machines on from afar without shelling out for remote management cards or cloud instances, WOL remains a lean, low-tech tool — with a few annoying caveats.

Sources: xaner.dev, Hacker News