Having got my Raspberry Pi up and running, I decided to see what else I could do with it. How easy would it be, for example, to administer the Pi remotely? If that worked then it could be set up to run with no monitor, keyboard or mouse, making for less clutter on the desktop.
It turned out that this is surprisingly easy by using Secure Shell (SSH). There are loads of articles on how to do this so rather than put the full details here, I’ll outline the steps and provide some links below.
- In most cases, when a computer joins a network it sends a request to the router for an IP address. The router uses DHCP to identify and issue the next free one. So each time you reboot the Pi can be assigned a new address. This makes connecting remotely challenging. So, the first step is to have your Pi use a static IP address on your home network. This will stay the same each time it connects. I’d suggest that you follow the steps here which are clear and work well.
- Keep a note of the static IP address that you chose.
- The next steps are summarised from those on the very useful AdaFruit site.
- Using the LX Terminal, and enter the following command: sudo raspi-config which will bring up the configuration screen that you will have seen at first startup. Click on the SSH option, then choose enable. The Pi may have to be rebooted.
- From another terminal window run the command ifconfig This will show your IP address and other network connection details.
- Now go to the client machine from which you want to use to connect to thePi and set up a client. For a Windows machine you might want to use a client such as Putty.
- Set up your client to connect to the Pi at the IP address you noted earlier. Log in with the user name Pi and your normal password.
- You can now run commands on the Pi from your other machine. Try typing “ls -l” or “cd ..” without the quotes.
Now that I have that working I intend to try getting the desktop environment accessible from another computer using VNC or similar.