If you use one device with multiple jump targets, it counts as one device. A device is an endpoint where remote.it is installed and not the number of services. Which will hopefully ease your concern.
Now that I understand it is a HikVision system, then I understand a bit more. HikVision uses multiple ports for connections.
If are not using Hik Connect, then we can support you. The Hik Connect app actually is using their cloud which is like a bridge between the site and the user’s Hik Connect app. This is problematic because the Hik Cloud cannot use the connection information from remote.it and requires a public IP and fixed ports. If we are not using Hik Connect then we can proceed with the following.
Setup up your services:
Install remote it onto a device on the site where the camera system is installed. You will need a device that will be on 24/7 (in this case your Ubiquiti router). This will act as your jumpbox. Then you will add a service for each camera/port needed. See this article on Jump Services. Network Services - Jump Box
The Hik system requires 4 ports. I do not recall them all, however you typically see them in your Hik System configurations.
Setup your connection(s) (This will be the person and each device using the the connections):
Install the Remote.It Desktop application remote.it Desktop Applications for Windows macOS Raspberry pi OS Linux Debian (You will not be able to do this on our web portal app.remote.it)
You will need to disable named connection for this to work:
Click on your avatar in the top left, and then Settings. On the page, toggle the Named Connections field.
For each site which would normally have a public IP address we are going to setup a unique localhost address (127,0.0.2, and so on.)
- For each service at the site, click on the service, click on Connection Configuration.
- Click on Local Network Sharing.
- On the second screen, Enable LAN Sharing.
- In the Bind IP Address field put in 127.0.0.2 (you will increment this for each new site. i.e. 127.0.0.3, etc). Click Save.
- If you are on a Mac, then you will need to allow your Mac to bind on the 127.0.0.2 IP address. Open Terminal and run the following command
sudo ifconfig lo0 alias 127.0.0.2
- Then back on the Connection Configuration page, override the Local Port to match the port for the service (for instance if the service is on port 443, set it to 443). Click the check box to save.
- Make your connection
Repeat this for all of the services you need for a single site. Then in your application once you make your connections you will use the IP address 127.0.0.2.
Then you can repeat for each new site where you need a remote.it connection for access only each site should have a new IP address such as 127.0.0.3, 127.0.0.4, etc. If you are using a Mac, you will need to add a binding for each new IP address using the command, for example
sudo ifconfig lo0 alias 127.0.0.3
I have had several customers use our system successfully for this type of set up on Starlink networks.
In the worst case scenario, you could also Remote Desktop to a windows computer on the LAN where the camera system is located and just use that computer to view the cameras on that system. You can do this with the iPad and on tablets. You just would need a Remote Desktop application on the iPad, Tablet or PC/Laptop that you will be using to connect to the system.