2
I've got a Debian server, which I would like to wake up remotely using a tool like wakeonlan
.
I have assigned the server a static internal IP 192.168.0.14
and set up the appropriate port forwarding in the router (which otherwise has a very limited admin interface).
When I am logged in to the same network, I can wake the server using the subnet IP, but I cannot wake the server using the public IP of the router.
What I do not understand: When the server is running and I listen on the server with netcat nc -ulv -p 9
, I can see the packet coming in in both cases (both when sending to the subnet IP and when sending to the public IP of the router).
If the packet arrives in both cases, why does the machine wake up only in one of them?
thanks, I now also found this answer with some more details
– leopold.talirz – 2017-06-15T22:38:26.457