Build a Wake-on-LAN magic packet — and see why a browser cannot send it.
The target's subnet broadcast, e.g. 192.168.1.255. A broadcast does not cross a router.
9 is conventional; 7 also works.
102-byte magic packet for 00:1a:2b:3c:4d:5e
A magic packet is six bytes of 0xFF followed by the target MAC repeated exactly sixteen times — 102 bytes in total. The repetition is what makes it recognisable to a network card that is otherwise asleep and doing no protocol processing at all, which is also why the UDP port barely matters: the card matches on the payload pattern rather than on the port. This page builds the packet and cannot send it, because browsers have no access to raw UDP. Send it with wakeonlan, a router's built-in function, or PowerShell — and note it must reach the target's broadcast domain, since a broadcast does not cross a router by default.
What this cannot tell you
Take this with you
Wake-on-LAN Packet Builder on RunTheTests — free browser-based sysadmin tools, no sign-up.