Configure a NAS for Wake-on-LAN and Energy Saving
A network-attached storage (NAS) system can centralise files, run a media server, host backups and provide remote access. Keeping it powered continuously is convenient, but a multi-bay unit with several drives consumes meaningful electricity. Wake-on-LAN (WoL) offers a middle path: leave the machine in a low-power state, then start it with a targeted network packet when needed.
WoL operates at the Ethernet interface. A specially formatted magic packet contains the target network card’s MAC address and is normally broadcast within the local subnet. The sleeping network interface detects it and starts the computer. Because the packet addresses hardware rather than a user account, it can wake a NAS before its operating system is running.
The saving depends on what happens after wake-up. A booted NAS with disks spinning, indexing and background applications running uses much more power than a standby NIC. WoL is most useful when the NAS has entered a supported soft shutdown and is awakened only for a backup, media session or remote visit. It cannot reduce power used by services that must remain continuously available.
Australian networks add practical wrinkles, particularly for homes using NBN services in Sydney, Melbourne, Brisbane or regional areas. The NAS setup guidance provides useful background on current equipment, while this method focuses on dependable wake-up behaviour. A magic packet normally stays on one LAN; reaching a NAS from another city requires a VPN, a compatible router feature or a controlled relay service.
Wake-on-LAN Compared with Common Power States
WoL balances idle electricity against availability. Full power-off has the lowest idle demand, but it cannot respond to a magic packet until mains power returns and the hardware has a separate restoration path. Comparing the complete 24-hour profile gives a better result than judging peak wattage alone.
| Power mode | Typical energy use | How access resumes | Best suited to | Main limitation |
|---|---|---|---|---|
| Always running | Highest during normal use | Immediately | Surveillance, continuous backups and always-on media | Persistent idle consumption |
| Soft shutdown armed for WoL | Very low | Magic packet starts the NAS | Backups, media sessions and remote visits | Boot delay and model-dependent support |
| Suspend or hibernate | Model-dependent | Platform-dependent | Short absences on supported models | Inconsistent NAS and network-wake support |
| Manual power-off | Lowest | Physical button or AC restoration | Long absences when physical access is possible | No WoL while disconnected |
For most occasional-use homes, soft shutdown followed by WoL provides the strongest balance: the NAS is unavailable while idle, yet a local user can start it within seconds or minutes. Always-on operation suits continuous surveillance, synchronised backups or a media server that must answer instantly. Measure consumption with a metering smart plug rather than a general estimate.
Prepare the Network and Hardware
Begin with a wired Ethernet path from the router to the NAS. WoL uses a local broadcast, so the sender must reach the NAS subnet; sharing a Wi-Fi name is insufficient if guest Wi-Fi or a separate NBN VLAN isolates clients. Record the physical port in use because multi-interface models may expose a different MAC address on each port.
Give the NAS a DHCP reservation or static address. A reservation preserves its current IP and prevents another device from taking it, giving scripts and relay tools a stable destination. The NAS and sender need matching subnet settings. Client isolation, VLANs or guest networks can block the broadcast before it reaches the target.
Collect these details first:
- MAC address of the wired port intended for WoL
- DHCP reservation or static IP address
- Router subnet and the sender computer’s local IP
- NAS model, firmware version and administrator access
- Backup of the current NAS configuration
Check for current firmware and back up the configuration before major changes. Some settings survive upgrades while others revert. A normal restart may reveal every firmware option, and a complete power removal can show which wake features remain available after reconnection.
Enable Wake in Firmware and NAS Software
The first layer is the NAS BIOS or UEFI. Enable Wake on LAN, PME, PCI/PCIe Wake or a similar option before saving. ErP compliance, Deep Sleep and some Power Off modes deliberately remove standby power, so they may disable WoL. Use the manual for the exact model and firmware rather than copying a generic screenshot.
The second layer is the Ethernet driver. Enable Wake on Magic Packet, Wake on Shutdown or PCIe Wake as applicable. Energy Efficient Ethernet, Green Ethernet and driver power-saving modes can sometimes block magic packets on newer adapters; disable those only while troubleshooting. Confirm that the recorded MAC belongs to the selected port.
The third layer is the NAS software. On supported QNAP systems, Wake on LAN is generally under hardware or network settings in QTS or QuTS hero; on supported Synology systems, it is usually under Control Panel’s Hardware & Power area in DSM. Labels vary by generation, so check the model documentation. Separately enable automatic restart after AC power returns if supported.
Create and Deliver the Magic Packet
A standard magic packet repeats the target MAC address 16 times and surrounds it with six FF bytes, representing an Ethernet broadcast. Repetition provides redundancy; it does not make the packet internet-routable. “Wake on LAN” tools construct this payload, and some NAS utilities can save target profiles.
Test from a wired or wireless client on the same LAN. Send to the subnet broadcast address, such as 192.168.1.255 or 192.168.0.255, matching the router’s private range. UDP ports 9 and 7 are conventional, although the receiving interface normally detects the packet regardless of port.
Remote wake-up needs a path back to the local broadcast. A router VPN is often cleanest because traffic arrives on the home LAN. Some routers provide a WoL command or directed broadcast function. A third-party relay should be used only after checking what network details it stores. Never expose the NAS administration interface directly to the internet.
Test the Wake Path and Reduce Idle Use
Treat the configuration as a repeatable test:
- Confirm the target MAC and reserved IP
- Place the sender on the same LAN and subnet
- Send a magic packet, then watch for link activity
- Wait for DSM or QTS, volumes and services to start
- Repeat after shutdown and through the remote access path
After hardware wakes, allow time for QTS or DSM, RAID volumes, indexing and services such as media servers or backup jobs to become ready. A network response does not guarantee every application is online. Record the delay from packet to useful access; that is the benefit being traded against hours of idle operation.
For the best energy result, shut the NAS down on a schedule when continuous access is unnecessary, then use WoL for planned work. Disable unused applications, avoid constant container or virtual-machine workloads, and choose a sensible disk spin-down period. Hibernation may save more on some platforms, but support is inconsistent. Compare standby draw with a working day using a metering smart plug.
Handle Outages and Australian Network Conditions
Power reliability matters in Australian cities. Storms and summer heat can interrupt mains power in Sydney, Melbourne, Brisbane and many regional towns. A NAS that returns after an outage may be more useful than one requiring a physical button press. Enable automatic restart after AC restoration, while recognising that WoL cannot operate while the wall supply is absent.
NBN access varies by premises: FTTP, FTTN and FTTC networks all appear in Australian cities. The NBN equipment may create separate wired and wireless networks or VLANs, so confirm that the router passes local broadcasts into the LAN. State-based time-of-use electricity tariffs also make evening shutdown schedules financially attractive for some households.
Use Australian legal and market expectations carefully. Retailers must not make misleading energy-saving claims under the Australian Consumer Law, so compare measured consumption rather than marketing language. A third-party remote relay also raises privacy questions. Australian providers handling personal information generally fall under the Privacy Act 1988 and Australian Privacy Principles, so check the relay’s retention policy, breach process and data location before trusting it.
Make the Setup Routine
A reliable setup should be treated as a small operating routine. Record the NAS model, wired MAC address, reserved IP, router access method and exact WoL tool in use. Keep a copy of the configuration, and re-test after firmware updates, router replacement or a change to network VLANs.
Configure one test path now: reserve the NAS IP, enable the three wake layers, send a packet from the LAN, then repeat it through the remote route. Compare the smart-plug reading with a scheduled shutdown plan. Keep WoL available for planned access, but switch the NAS off when continuous availability would waste energy without a purpose.