#REMOTE WAKE UP OF DESKTOP COMPUTER FOR FREE#
#REMOTE WAKE UP OF DESKTOP COMPUTER PRO#
#REMOTE WAKE UP OF DESKTOP COMPUTER PASSWORD#
#REMOTE WAKE UP OF DESKTOP COMPUTER OFFLINE#

This tool basically boardcast to all devices under the same network and wakes up the device that matches the mac addressĤ. To send the wake up our desktop, we need the mac address of our desktop network card. Now we need something to send the magic packet, I use wakeonlan but there are many alternatives. Supports Wake-on: g Wake-on: g Link detected: yesģ. Sudo ethtool eth0 Settings for eth0: Supported ports: Supported link modes: 10baseT/Half 10baseT/Full. g indicates wake on Magic Packet is enabled Verify WOL is enabled for our network interface eth0.Enable WOL with ethtool in the OS level, sudo ethtool -s eth0 wol.This feature is usually disabled by default, we need to enable it in our BIOS.

Luckily, there is a feature called Wakeup On LAN that’s supported by most motherboards.

#REMOTE WAKE UP OF DESKTOP COMPUTER OFFLINE#

The router sees the device is offline and stop forwarding anything to that local ip. But the problem is that we can’t ssh back to it after it goes to sleep.

I set my desktop to suspend after 15mins of idle to save electricity. Before we restart sshd and apply the changes, we need to create a ssh key pair and copy our public key to user’s authorized_keys: ssh-copy-id Now restart sshd on desktop and test ssh again, this time it should not prompt for password. PermitRootLogin no PasswordAuthentication noĥ.

#REMOTE WAKE UP OF DESKTOP COMPUTER PASSWORD#

To disable password authentication, in /etc/ssh/sshd_config, change the following lines to no In my setup I disabled password authentication and root login, so that the only way to ssh into my desktop is through public key authentication. Internet is a dangerous place and we don’t want our machine compromised. Test ssh, ssh Tighten up the security.We need to add a port forwarding rule so that it forwards source port 22 to destination, our desktop’s ip, 192.168.0.10and destination port 22. All routers should have this functionality and this can be setup on the router admin web ui. In our case we need to tell our router to forward all traffic heading to port 22 of our desktop. So we need to explicitly tell our router to forward all incoming traffic of a port to a specific local ip and port, this is called Port Forwarding. Now that we have the public ip, can we ssh to our desktop remotely? Well, not yet, our home devices all share the same public ip, this is called Network Address Translation (NAT).Find the temporary public ip assigned by the ISP, dig +short let’s say 1.2.3.4 is our public ip.In order to access the desktop from external network, we need to: Verify sshd service is running and find the ssh port (default is 22).Find the ip of destination machine: run ifconfig and you want to find the interface with your local ip, something like 192.168.0.10.In the rest of this post I will walk through how I set up my desktop for SSH and WOL(Wakeup On LAN).

#REMOTE WAKE UP OF DESKTOP COMPUTER FOR FREE#

SSH into my desktop remotely, and continue my workloads, for free (well, plus the electricity cost).

Run the algorithms on the cloud, cheapest computation optimized instance costs $0.085/hour on AWS.

#REMOTE WAKE UP OF DESKTOP COMPUTER PRO#

Run the algorithms on my Macbook pro and thus starting a fire somewhere.

If I’m away from home and still wants to work on this project, my options would be: These workloads, depends on the model and hyper parameters, could take a while to finish. Recently I had to run some Q-learning algorithms on my home desktop (running on Ubuntu 18).

Remote wake up of desktop computer