On the host machine (RPI4), CPU usage is minimal when the host machine is idle. To start with, I opened a terminal remotely on the RPI4, and ran top. Connecting to my RPI4 was straightforward. My friends already have TeamViewer running on their Windows machines. Choose a password, connect the device to your TeamViewer account, accept the license agreement, associate your RPI4 with your TeamViewer account (you can connect via the TeamViewer ID instead), grant easy access, and assign your account. There’s a few more jumps to clear before the software is ready to use. Point your web browser to the download site and grab a package (.deb) for TeamViewer Host for Raspberry Pi (it’s somewhat tucked away on the right hand side of the page). Unsurprisingly, TeamViewer isn’t present in the Raspbian repositories.
This means that the software is designed to receive connections and act as a server. For the RPI4 (and earlier versions) TeamViewer is only available for the RPI4 in a host edition. But you can use the software free of charge to access private computers. It’s proprietary software, so you won’t find the source code available. TeamViewer offers remote access to a wide variety of operating systems including Linux distributions. Popular ones such as VNC Viewer (realvnc), Remmina, TigerVNC, TightVNC, Vinagre are all present.īut the host Windows machines only had TeamViewer installed, and I never force ‘alien’ software on my (dinosaur) mates. There’s lots of VNC clients available in the Raspbian repositories. The obvious focus is VNC related software. In the realm of remote desktop software, there’s lots of choices for the Raspberry Pi. So what better time to access my RPI4 remotely and continue my Pi adventures. Reliant on Windows machines with only an Android phone as solace for an entire week wasn’t a tempting prospect. No one is perfect! And the week before this trip, my Linux laptop gave up the ghost. For the past week, I’ve been travelling around the country, staying with a few friends. While readers’ suggestions were focused on the RPI4 acting as a client, my more immediate concern was to use the RPI4 as a host rather than a client.
0 kommentar(er)
