![]() On a internet nat router its hard to say. On a non nat router you could send it to the broadcast of the subnet and with the direct broadcast feature the router would do it. So first your router must have this feature and then it must have a way to send this packet to all ports on the lan. It was not long before this feature was removed or turned off by default. ![]() What you used to do was for example ping 192.168.0.255 with a spoofed source address and all the lan machines would then send replys to the spoofed source doing a denial of service. Even if it has it most the time you disable this because it allows someone to do denial of service attacks against all the machine at the same time. To make it work remotely the router needs a very special feature called directed broadcast. Also the mac table in the switch/router also has likely timed out since the pc is not sending any packets when it is asleep it only listens. If the machine has been offline for a very long time the ARP entry has timed out and since the PC is offline it will not respond to a ARP. The reason it will work in a lan is the tool is likely just sending the packet to the broadcast address and not even bothering with the IP address. Still because it sometime works it appears there are vendors that accept IP packets sent directly to the machine mac address rather than packets set to the broadcast address. So the whole concept of sending WOL to a IP is flawed since WOL does not use IP. The machine does not have a IP it only has a mac address since the OS is not running and even when it does run it could be assigned a different ip address. It technically should not work to set it directly to the ip address of the machine. WOL is a very special packet the is sent via a broadcast and contains the machine mac address. My router is a TP-Link TL-WR1043ND with latest firmware. Any ideas about what's happening? My configurations are below. So it seems the ddns or routing must be the issue. If I send the packets from a computer *on my network* straight to another computer (like 192.168.0.103), the computer wakes up, all the time. They stop responding to my packets after a while unless I wake them manually for a bit. This describes the behavior of all of my computers. I woke it up manually, tested and saw that it was receiving the packets, put it back to sleep, and successfully woke it from my app. In the morning, I sent a packet the exact same way and it didn't wake up. I then used an app to send a packet and it woke up. ![]() I've configured a dynamic dns and set port forwarding, but it seems to work sometimes and other times not. I want to be able to turn on my three home computers over the internet so that I can access them remotely if I need to.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |