Remote.it JumpBox behind StarLink

While this topic has been addressed, see Starlink Port Forwarding Starlink, Cellular, CGNAT, Dec 2022, a peculiarity in my proposed application leaves uncertainty about the JumpBox applicability.

I have many legacy HAI Omni controllers in service and customers considering moving to StarLink as their ISP. The Omni is/must be assigned a static LAN IP address, the router assigned a static WAN IP address and fort forwarding set up to route incoming tracffic destin for the Omni controller.

Assume the StarLink router is put in bridge mode and a 3rd party router is used to establish the network with the staticly addressed Omni controller and other devices and accomplish the port forwarding task.

The Omni controller never initiates network messaging, only responses to incoming messages. Message traffic is between a mobile or Windows application and the Omni direct, no server. I do not know the detailed nature of the messaging protocol or contents, but from the “remote” app standpoint, it directs Omni traffic to a WAN IP address (or URL) and a port number.

Can the JumpBox behind the StarLink router be reached with an “assigned” WAN IP address (or URL) and a port number and complete the connection through the 3rd party router to the Omni controller? And of course route the reply back to the originator?

Appreciate all y’all’s help

David//

Hello David,
The connection to the Omni Controller will be a jump connection and if you need to have a “static IP” or address to access it, then you would need to install the Remote.It Desktop or CLI on the computer or server that will be using the connection. This connection will look like a localhost connection to the initiating computer/server with a high port number.
In other words on the Starlink side, you would have a jump host (no port forwarding needed there). This article covers setting up a jumpbox using a raspberry pi, but you could also use a simple OpenWRT travel router too. The directions are the same, just choose OpenWRT when selecting the device type. Raspberry Pi Jumpbox
Then for making the connection to the omni controller, you would install the Remote.It Desktop or the Remote.It CLI on the initiating connector side. https://www.remote.it/download-list?products=desktop|cli#Download-Results These connections are not sharable or public so each computer/device needs to install the Remote.It Desktop or CLI and create their own connections.

Here is another post about a the same thing just with a different service. https://forum.remote.it/t/starlink-port-forwarding/645

Brenda,

  • Well thank you for the thoughtful response, much appreciated. Question - Is the Remote.It CLI (app) available on Mobile devices. Omni is a security/home automation device, and everyone accesses their’s with a mobile app.