Wake on LAN Not Working? Router Settings to Check

Why Wake on LAN stops at the router

Wake on LAN, sometimes abbreviated as WoL, sends a specially formed packet called a magic packet to the target computer's MAC address. The network interface watches for that pattern while the machine sleeps, and when it sees the pattern it signals the computer to power on. This is why Wake on LAN depends so much on the path the packet takes: the adapter has to see it.

In a typical home network, the router is the delivery system. If the sender and the sleeping computer are on the same subnet, a local broadcast usually reaches the adapter without help. The router becomes the problem when the packet arrives on a different interface than the target computer, such as from the internet or from another VLAN. Standard routing does not forward broadcast traffic, so the magic packet stops at the router and the PC never wakes. That is the difference between LAN versus WAN traffic.

The right fix depends on where the packet starts. Sending a wake command from a phone on the same Wi-Fi network needs one check. Sending it from outside the home needs different settings. Work through the computer first, then the same-network router settings, then directed broadcast and remote options.

Check the target computer first

Before changing router settings, make sure the computer is willing to wake. Several layers matter: the computer firmware, the operating system, and the Ethernet adapter. The adapter driver usually has a power management option with a name such as wake on magic packet or wake on LAN. Some adapters use both a magic packet option and a pattern match option, so check that the right one is selected.

Use an Ethernet cable for the most reliable results. A Wi-Fi connection can work while the computer is awake, but many wireless adapters stop listening to broadcast frames during power save. The IEEE 802.11 standard defines the wireless LAN MAC and PHY behavior, and the Wi-Fi Alliance lists power-saving features such as target wake time as a way to improve device efficiency. Those features do not keep a receiver waiting for wake packets, so for Wake on LAN, wired Ethernet is the dependable path.

Confirm that the computer is plugged into power. A laptop that is fully unplugged cannot keep its network interface alive, and a system that lost power completely has nothing listening. Wake on LAN wakes a sleeping machine, it does not fix a machine that is shut down unless the firmware and adapter are configured to keep the Ethernet port powered.

Router settings for the same network

When both devices are on the same subnet, the router usually needs to allow the local broadcast to reach every host. Some routers and mesh systems apply client isolation, sometimes called AP isolation, which stops one client from talking to another. If the target computer is on a guest network, move it to the main network, because guest networks are isolated by design.

Look through the router's LAN settings for terms such as broadcast forwarding, multicast forwarding, or IGMP snooping. These options control how group-addressed traffic is treated. Wake on LAN apps often send to the subnet broadcast address, so the router must not filter that address. If the router has a firewall rule that drops broadcast frames on the local subnet, disable that rule for the LAN segment.

A stable local IP address also helps. Set a DHCP reservation that ties the computer's MAC address to a permanent address. The wake app stores that address, and the router always knows where to send the packet even after reboots.

Wake across subnets with directed broadcasts

A directed broadcast, also called a subnet broadcast, is a packet sent to the broadcast address of a specific remote subnet. Normal routers treat it like any other broadcast and drop it, because broadcasts are meant to stay inside one network segment. That is exactly what happens when Wake on LAN stops at the router: the packet targeted at the remote subnet never reaches it.

Some routers include a setting to allow directed broadcast forwarding. The option may be named directed broadcast, subnet broadcast, or broadcast forwarding, and it is usually in the advanced LAN, firewall, or WAN sections. When enabled, the router delivers the packet to every host on the destination subnet, which is what the sleeping PC needs.

Consumer routers do not always expose this setting. If yours does not, the alternatives are a static route to the target subnet, a VPN that places you on the subnet, or a wake app that sends a unicast packet through a mapped port. For separate VLANs, a router with layer 3 routing and directed broadcast support is the cleanest solution, and a look at the routing table confirms where the packet will travel.

Port forwarding and static routes for remote wake

For waking from the internet, the router needs to know which LAN device should receive the inbound packet. A common setup is port forwarding: choose a UDP port, forward it to the sleeping computer's local IP address, and tell the wake app to send to the home's public IP address on that port. This is the same pattern used for other inbound services.

A static route can help when you have multiple subnets or when the router lacks directed broadcast forwarding. A static route says to reach the target subnet, send the packet to a specific next-hop address. Combined with a DHCP reservation, it gives the router a stable path to the sleeping PC.

Because residential internet addresses can change, a router with DDNS support lets you use a hostname instead of a numeric address. The wake app looks up the hostname at send time, so the rule continues to work after the internet provider assigns a new address.

The safer remote option: a VPN

Opening a wake port to the internet is convenient, but it is also an exposed service. Security guidance from NIST and other organizations encourages you to limit the services reachable from the internet and to use secure remote access. A VPN does both: you authenticate first, and then send the magic packet as if you were on the home network.

Many routers include a VPN server, and the setup effort is comparable to port forwarding. Once the VPN is connected, the client appears to be on the home LAN, so directed broadcast settings matter less. For a remote wake setup you will use for years, a VPN is usually the more reliable and more secure choice, and it belongs in any router security basics plan.

What to pick for your use

Questions

Why does Wake on LAN fail when the computer is on Wi-Fi?

Wireless adapters and routers manage power differently, and the radio often stops listening while the device sleeps. Use the Ethernet port for the most reliable results, and enable wake on magic packet in the adapter settings.

What is a directed broadcast on a router?

It is a packet addressed to every host on a specific remote subnet. Most routers drop such packets unless you enable an option such as directed broadcast or broadcast forwarding.

Do I need a static IP address for Wake on LAN?

Not strictly, but a DHCP reservation helps. The wake app needs a stable local address, and port forwarding or a static route needs a stable target on the LAN.

Is Wake on LAN over the internet safe?

Exposing a wake port is risky because anyone who can reach it can try to power on the machine. A VPN is safer because it authenticates the remote user before any packet enters the LAN.

Can I wake a computer that was fully shut down?

That depends on the motherboard and adapter settings. Most setups support waking from sleep, and some support waking from a full shutdown when the firmware and network adapter are configured to keep standby power on the Ethernet port.

Do the latest Wi-Fi standards improve Wake on LAN over Wi-Fi?

Newer Wi-Fi generations add power-saving features such as target wake time, which improve device efficiency but do not keep a receiver waiting for wake packets. A wired connection remains the dependable path.

Which router settings commonly block Wake on LAN?

The usual blocks are client isolation, a firewall that drops inbound UDP packets, and missing directed broadcast forwarding. Check the guest network, LAN broadcast options, and port forwarding rules in that order.