(Though the aforementioned wake-on-pattern can allow the TCP handshake itself to wake the system, at which point you no longer need to send a "magic packet" anymore, but again this may result in unwanted wakeups. TCP is never used for WoL "magic packets" since the target computer can't really establish a TCP connection when it's still asleep. the last address of your subnet) as the destination IP, but this usually doesn't work as the router just refuses to send packets to the broadcast IP address.įinally, you could try using "Wake on pattern" which will make the ARP query itself wake the system from sleep (on Windows – uncheck the "Only allow management stations to wake…" box) but this will likely result in the system waking up far more often than expected.
If you forward a specific port to a specific LAN IP address, the WOL packet will be forwarded only if the router/switch still has that IP in its lookup table. So you can try adding a port-forward rule with 192.168.1. The port number isnt important, but port 7 is usually used on the LAN (but dont forward port 7 on your router, choose a different port that isnt used by any well-known service). Though the MAC address in packet headers doesn't strictly need to be the computer's own address – when WoL is used locally, the packets are more commonly sent to the "broadcast" MAC address instead, which will reach the computer's network card all the same. (In other words, the feature that you don't have access to is literally the feature that would allow you to do this properly.) You probably can't use "Wake on magic packet" in this situation, as the router needs to know the destination MAC address somehow.
0 kommentar(er)
