How to set up remote Wake on LAN for your NAS

Remote Wake on LAN lets a powered-off NAS boot when its Ethernet network card receives a magic packet containing its MAC address. The packet is normally broadcast inside the local network, so distance is not the main obstacle: the command must reach the router at your home and then the NAS’s broadcast domain. The NAS itself does not need a public IP address.

This guide covers QNAP and Synology systems, the router path that makes remote access practical, and a repeatable test routine. The aim is to recover a NAS from anywhere without exposing its management interface or shared folders directly to the internet.

Understand what the NAS must support

Wake-on-LAN depends on cooperation between the NAS firmware, motherboard and Ethernet adapter. A correctly configured system can usually start from a normal shutdown, but support varies by model and power state. Some models also disable WOL from deep sleep. Check the NAS manual and confirm that its wired interface is marked for WOL or “Wake on LAN” rather than assuming every Ethernet port behaves the same way.

In the BIOS or UEFI, look for Wake on LAN, PCI-E Wake or Resume by PCI-E Device. “Restore on AC Power Loss” is a separate function that starts the machine when electricity returns; it does not respond to a magic packet. Likewise, a UPS can keep the NAS available during a blackout, although WOL still requires the network card to have standby power and a booted operating system is not yet available.

Use Ethernet for the NAS whenever possible. Most NAS Wi-Fi adapters cannot receive a magic packet while the machine is off, and a guest network may isolate its clients behind another VLAN. Homes in Sydney, Melbourne, Brisbane and Perth often have an NBN connection plus an ISP gateway and a separate router, so identify which device owns the home subnet and where firewall rules for UDP 7 or 9 may apply. NBN access may be FTTP, FTTN, HFC or fixed wireless, but none of those technologies has to relay the magic packet across the internet.

Prepare a QNAP NAS for remote startup

Sign in to QTS with an administrator account and update the firmware before changing low-level settings. Depending on the model and QTS release, Wake-on-LAN appears under Network & File Switch, Control Panel > Hardware & Power, or a similarly named power page. Enable it for the wired interface, apply the setting, and perform a full shutdown; leave time for the NAS and switch to settle before testing.

In QTS, open the network interface panel and record the physical Ethernet MAC address, not a virtual adapter or container address. Give that address a DHCP reservation in your router so the NAS keeps the same IP after a reboot. This is essential when a router’s online-device page needs to select the correct target.

Test from a computer on the same LAN with a manufacturer-compatible Wake-on-LAN utility. If the local test fails, recheck the interface selection, BIOS option and QTS setting, then confirm that the cable, switch port and VLAN configuration are suitable. An Australian authorised reseller can also confirm support for the exact chassis and firmware combination, since similar QNAP ranges can use different motherboards and adapters.

Prepare a Synology NAS for remote startup

In DSM 7, install current updates, open Control Panel > Hardware & Power, and select Wake on LAN where the option is provided. Enable it, save the change and shut the NAS down completely before the first test. Some older models omit this control; check Synology’s model-specific compatibility information before spending time on later network settings.

Record the wired MAC address from the DSM network-interface page, then reserve that address in the router. DSM may show several virtual interfaces created by VMs or containers, but the magic packet must target the NAS’s physical network card. Keep QuickConnect available for managed access after startup if desired, but do not treat it as a substitute for confirming the WoL and LAN routing path.

After the NAS wakes, verify that Drive packages, DSM services and any applications you rely on start automatically. A successful power-on can still leave a headless NAS inaccessible if its file services or authentication system waits for manual action. Test from both the local LAN and the intended remote route, because a local success narrows any fault to the remote access path while a local failure points back to the NAS configuration.

Build a secure route back to the LAN

The most dependable remote method is an outbound VPN to the home router or a supported subnet gateway. A phone or laptop starts the VPN, joins the home network, then sends the magic packet or asks a router WOL relay to send it. This avoids inbound port forwarding and works with dynamic addresses or the carrier-grade NAT commonly seen on Australian broadband services.

Confirm that the VPN client is permitted to reach the NAS subnet and to transmit its broadcast domain. Some VPN clients use a separate address pool, while services such as Tailscale or ZeroTier may route unicast traffic but not broadcast packets by default. Configure the appropriate LAN route, directed-broadcast support or a documented WoL relay; merely installing a VPN is not enough.

Do not publish DSM, QTS, SMB or other administration ports to the internet merely to make WOL seem to work. Forwarding UDP 9 is unreliable across ordinary NAT because routers commonly drop directed broadcasts. If the router offers authenticated remote administration or a WOL service, use it with multi-factor authentication and restrict access where possible. Remote wake should be one controlled part of NAS recovery rather than an open door to the data itself.

The same discipline applies to lifts and stage-control equipment. This stage systems overview offers a useful parallel for documenting recovery routes, controlling operators and rehearsing access before it is urgently needed.

Recommended settings for a reliable remote wake

Use this checklist after configuring the NAS and before relying on it from another location:

• Connect the NAS with Ethernet, place the cable on the main network, and keep it away from guest Wi-Fi and isolated VLANs.
• Record the wired MAC address inside QTS or DSM, label it clearly and reserve the same IP address in the router.
• Update QTS, DSM and the NAS firmware, then confirm that Wake on LAN remains enabled after each significant update.
• Set a PCI-E wake option in BIOS or UEFI where available, and verify that the system supports WOL from a full shutdown.
• Install a router VPN or another supported LAN access method, protect it with strong credentials, and avoid exposing file-sharing or administration ports.
• Configure Drive packages, services and applications to start automatically so the NAS becomes useful immediately after power returns.
• Test from mobile data at least periodically and after a router, firmware or cabling change; use a UPS rated for Australian 230 V mains and suitable Type I connections where outages are a concern.

Keep a short recovery note with the NAS serial number, MAC address, reserved IP, VPN instructions and physical location. Exclude the password from that note or store it in a password manager. A local wake proves that the packet reaches the NAS; a remote wake proves the VPN, router and firewall path as well.

Set up the full chain now and verify it after a normal shutdown. Once this workflow is proven, your QNAP or Synology system can be started securely from a hotel, office or mobile connection without relying on an exposed public IP address.