![]() ![]() So my question is, is there a way I can circumvent this problem, and be able to turn on my pc remotely even after a it's been in shutdown for a while? I thought step 3 would fix the ARP table flushing, but apparently it didn't (I thought DHCP configs and ARP table were the same thing?). I tested it on 4G and it properly delivers the packet.Īs I said above, everything works fine until remote PC stays turned off for a while. Lastly, I have downloaded an app on my phone ( this one) that sends a magic packet with my remote PC MAC address.Then, in the DHCP config, I mapped my remote PC MAC address to its own IP.Since the router doesn't allow broadcasting, I cannot bind the port to 192.168.1.255 (it says "invalid ip"), and hence I bound it to the IP address of my remote machine. I forwarded port 7 on my router listening to UDP packets.Setup a DDNS service, allowed WoL in BIOS, allowed NIC to WoL on magic packets, disabled fast startup on windows 10 etc.I understood that this is due to the ARP table flushing, and I thought I had addressed this problem by mapping my remote PC IP address to its own MAC address in the DHCP config of its router. I have followed several guides to enable it and it seemed to be working, at first, except that after my remote PC has been turned off for a while, it doesn't work anymore. I setup a system where I can turn on my home computer remotely using Wake on LAN / WAN. My knowledge of networks didn't go beyond what an IP address is until 3 days ago, and a lot of this is still very alien to me. Recap of the possible solutions at the bottom -įirst of all I apologize if I write something that makes no sense.
0 Comments
Leave a Reply. |