Wake Up Your NAS From Anywhere With a Magic Packet
Picture this: you're at a mate's place in Brisbane for the long weekend, your media library sits quietly in a cupboard back home in Adelaide, and you suddenly remember you need a file. The NAS is in standby, the lights are off, but with the right trigger it can spin back up before you finish your coffee. That is exactly what Wake-on-LAN is designed for, and Australian conditions actually suit the technology quite well once you understand how the packets travel.
A network-attached storage box spends most of its life idle. Hard drives spin down, the CPU idles, and the unit consumes a fraction of the power it would under load. Energy prices in Australia have climbed over the last few years, particularly in New South Wales and South Australia where peak rates are noticeable on quarterly bills, so leaving a NAS switched off until it is needed makes financial sense for plenty of households. Wake-on-LAN, sometimes shortened to WOL, is a small network message that tells the motherboard to power the system back on. When the box boots, shares reappear, snapshots run, and any scheduled backup tasks carry on as if nothing happened.
The catch is that a magic packet only works on a local network by design. To send one from across the country, or from a caravan park in Cairns, you need a few extra pieces in place: a way to reach your router from the outside, a relay that knows the target device's MAC address, and a NAS whose network interface still listens while the rest of the box is asleep. The NBN rollout has complicated this for some Australian homes, particularly those placed behind carrier-grade NAT, but workable routes exist through most routers sold by Aussie retailers like Mwave, Centre Com, or Scorptec.
What follows is a step-by-step walk-through aimed at home users running Synology or QNAP gear on typical Australian broadband. It covers the network plumbing, the firmware toggles, the apps that fire the packet from a phone, and a few habits worth keeping so the setup survives a Telstra outage or a summer storm rolling in off the coast.
How a Magic Packet Reaches a Sleeping Drive Bay
A Wake-on-LAN packet is a very small broadcast frame. It contains six bytes of 255s followed by the target machine's MAC address repeated sixteen times. When the network interface on the receiving motherboard sees its address buried inside that pattern, even if the rest of the computer is in a soft-off state, it tells the power supply to wake the system. This is why the technology works without any operating system running and why it survives across reboots, BIOS updates, and even most reinstalls.
For the magic packet to arrive, three things must line up. First, the network interface must stay powered, which usually means the ethernet port, not Wi-Fi, since most Wi-Fi chips drop power completely when the host shuts down. Second, the cable must still be plugged into a switch or router that is itself awake. Third, the packet must reach the broadcast domain where the target sits. On a typical suburban NBN connection the router stays on 24/7, so the first two conditions are easy. The third is where remote wake-up gets interesting.
Australian homes usually run FTTN, FTTC, HFC, or FTTP depending on the postcode, and each of these terminates at a router supplied or chosen by the resident. Most modern routers, including the popular TP-Link, Netgear, and Asus models stocked by JB Hi-Fi and Officeworks, retain enough smarts to forward a packet arriving on the WAN side to the correct internal address. The NAS itself only needs to listen passively, which keeps its idle draw in the 5 to 10 watt range. A simple math exercise shows that powering down a 30-watt NAS for sixteen hours a day saves roughly 175 kilowatt-hours a year, more than the cost of a small UPS that keeps the broadband modem alive during a blackout.
Sorting Out Your NBN Connection First
Before touching the NAS, the network outside the front door needs a rethink. Many Australian ISPs issue residential customers a dynamic IP that changes every few days, and a growing number of them, including Telstra and TPG in some exchange areas, place customers behind carrier-grade NAT. CGNAT means there is no public address to forward a packet to at all, which makes conventional Wake-on-LAN impossible without a workaround.
The cleanest fix is a static IP, which most ISPs sell as a small monthly add-on. Aussie Broadband, Superloop, and Internode still hand them out without much fuss, while the bigger carriers often bundle them into business plans. Where a static address is genuinely unavailable, dynamic DNS services bridge the gap by attaching a hostname to whatever IP the router is given each night. Combined with a tiny port-forward rule on the router, the hostname stays pointed at the right place within a minute or two of any IP change.
For households stuck behind CGNAT, a small Virtual Private Server hosted in Sydney or Melbourne can act as a relay. The phone app connects to the VPS over an outbound tunnel, and the VPS sends the magic packet down a WireGuard link into the home. It is a slightly more involved setup, but for someone running remote backups from a Perth office to a NAS in a rural property near Albany, it is well worth the effort. Tools like Tailscale, ZeroTier, or a self-hosted WireGuard handle this elegantly and avoid poking holes in the router entirely.
Choosing a NAS That Listens While It Sleeps
Not every model handles remote wake-up gracefully. Entry-level units sometimes omit WOL support on certain NICs, while higher-end gear offers per-port toggles and scheduled wake windows. The table below compares a few common Synology and QNAP boxes against the features that matter for remote power-on.
| Feature | Synology DS223 | Synology DS923+ | QNAP TS-264 | QNAP TVS-h874 |
|---|---|---|---|---|
| 2.5GbE ports | 1 | 2 | 2 | 2 |
| WOL toggle in DSM/QTS | Yes | Yes | Yes | Yes |
| Schedules wake events | Limited | Yes | Yes | Yes |
| Idle power draw | ~7 W | ~12 W | ~10 W | ~25 W |
| Supports WoL on both ports | No | Yes | Yes | Yes |
| Bundled VPN server | Yes | Yes | Yes | Yes |
Mid-range four-bay units tend to strike the best balance. They offer a second ethernet port that can be configured for failover, they run cool enough to sit in a living-room cupboard without complaint, and the operating systems expose the relevant toggles in plain settings panels rather than hidden command-line flags. Two-bay units work too, but expect to lose some flexibility around wake schedules and dual-port configurations.
Flipping the Right Switches Inside DSM and QTS
On Synology's DSM, the path is straightforward. Open Control Panel, choose Network, and edit the relevant interface. Tick Enable Wake on LAN under the advanced section and confirm the MAC address matches what is printed on the box. The setting persists across reboots, which is the whole point. Synology's Scheduled Power settings also support timed wake events, although the official documentation clarifies that the WOL trigger still has to come from outside the box. Inside the NAS, scheduled power on works through the regular power-on timer found under Hardware and Power.
QNAP's QTS and the newer QuTS hero follow a similar pattern. The switch lives in Network and Virtual Switch, then the specific adapter. Both vendors allow the magic packet to be sent to the broadcast address, which means a phone on the same subnet can wake the NAS even if the target IP has changed. Saving a permanent ARP entry on the router, often called a DHCP reservation, keeps that broadcast predictable and prevents the IP from drifting after a firmware update.
A useful habit is to test the local wake first. From a laptop connected to the same network, fire a packet using a free tool such as Depicus or Wake On Lan for Android. If the lights come on within a few seconds, the firmware side is fine. If nothing happens, walk back through the BIOS or UEFI of the NAS. Some brands ship with WOL switched off at the firmware level, requiring a quick keyboard hookup with a monitor to flip it on.
Sending the Packet From a Phone, Browser, or Smart Speaker
Once the NAS is listening locally, the next step is firing the packet from outside. A handful of apps make this painless, and several are free.
- Wake On Lan for Android, simple interface, supports multiple profiles
- Mocha WOL for iOS, retains a small list of MAC addresses for quick firing
- Depicus online wake-up page, useful from a borrowed device without installing anything
- Synology's DDNS hostname, lets any device send the packet through a remembered address
- Home Assistant running on a Raspberry Pi, perfect for combining WOL with home automation routines
For those who prefer not to install apps, most routers expose their own WOL page. The Asus RT-AX86U sold at JB Hi-Fi, for example, has a built-in WOL tool under Network Tools. A simple URL bookmarked on the phone's home screen takes care of the rest. From a Google Home or Alexa routine, integration is possible through a small HTTPS call to the router, though this requires a static address or DDNS hostname on the outside.
Riding Out Aussie Heat, Storms, and Blackouts
Remote wake-up is only useful if the broadband link stays alive. Australian summers push air-conditioners hard, and storm season in Queensland, Victoria, and parts of New South Wales regularly knocks power out for hours. A small uninterruptible power supply keeps the modem and router running long enough for the magic packet to arrive and for the NAS to boot through a clean shutdown rather than a sudden cut.
Synology and QNAP both integrate with USB-connected UPS units and gracefully power themselves off when the battery runs low. The magic packet then becomes a recovery tool as well. After power returns, a scheduled task can boot the NAS at, say, 7 a.m. AEST, ready for the morning backup run from a workstation that lives in a home office in Geelong or Hobart. Pairing the schedule with a simple ping check through the router ensures the box does not boot prematurely while the link is still down.
Dust and heat matter too. NAS units tucked inside a hallway cupboard in Perth can reach uncomfortable temperatures during a 40-degree day. Quiet case fans, a thermometer with a smart plug, and a rule that powers the unit down if the cupboard exceeds 38 degrees all extend drive life. Wake-on-LAN becomes a routine that runs only when conditions are sensible, not just on demand.
Hardening the Setup With Sensible Security
A magic packet that reaches the wrong device is a real risk. Locking the path down keeps the friendly wake-up friendly. Several habits are worth adopting.
- Stick to a VPN tunnel rather than opening a raw port on the router
- Reserve a fixed internal IP for the NAS through DHCP so the relay knows where to send the packet
- Enable two-factor authentication on the DSM or QTS login page
- Restrict the WOL sender to a short allow-list of MAC addresses where supported
- Keep the router firmware current and replace the default admin password
For a small business customer running backups from a regional office in Bunbury or Cairns, the same principles apply with a slightly heavier touch. A site-to-site VPN with certificate-based authentication, a separate management VLAN for the NAS, and a documented change window for firmware updates will satisfy most compliance checklists without spoiling the convenience of pulling files from a quiet box that wakes up only when it is needed.
Wake-on-LAN through a NAS is one of those small skills that pays back every time the lights flicker, the in-laws visit, or a long weekend demands a file from a folder that should have been left switched off in the first place. Browse the rest of WhichNAS for deeper dives into QNAP and Synology firmware features, RAID layouts, and the kind of Australian-friendly backup strategies that keep data safe no matter what the weather brings.