Best practice is to install remote.it on a device that will be available at all times. This is ideal in an AWS environment to have a since EC2 instance act as the gateway into the VPC.
This is typically done when the targeted resource is not compatible with Remote.It and it cannot be installed (e.g. a printer, hosted resources)
You will need:
- A Remote.It Account
- Desktop App installed on a laptop or desktop computer (used for configuration)
- A device on the destination LAN with remoteit installed
- The LAN address and port of the service that you want to make available via jump
In order for jump service to be configured properly, the target service will need to have one of the following:
- A static IP address
- OR - An equivalent to a static IP address, e.g. "DHCP Reservation" through your router, so it always appears on the same LAN IP address.
- OR - An MDNS or "Bonjour" address, such as raspberrypi.local, which is unique for all devices on your LAN. Note: If you use the avahi-daemon on a Raspberry Pi, and you have more than one running on the same LAN, their MDNS names will be indexed, e.g. raspberrypi-1.local, raspberrypi-2.local, which may not work properly as the assignment is not predictable. You can assign the hostname of the Raspberry Pi using the latest version of the Raspberry Pi Imager found at https://www.raspberrypi.com/software/
It is recommended that you do not setup up a jump service target on a PC or laptop that will either sleep/hibernate or be removed from the LAN.
For this reason, this is usually setup using a Raspberry Pi or some other inexpensive computer/travel router that can be on at all times when setting up at a home or office network. In AWS or other cloud network, a standard instance will do.
Setup via Desktop
If you haven't already setup your desktop and the target device, please follow these directions before proceeding.
Open the desktop app and select the device on the device list which will act as the host.
Add the Service. Click + to add the service
Set up your service. Enter your service details and save.
Connect. Use the address provided by Remote.It in your client software. (e.g. Azure Data Studio for this case). If you leave it added to your network, the address will remain the same and you can connect on demand without needing to return to the Desktop App. Just go directly to your client app.
