Does RadioPro Link require a static public IP address or port forwarding?

Last updated:

A provisioned RadioPro Link connection normally does not require a static public IP address or an inbound port-forwarding rule at the Gateway site. Clients use CTI's assigned endpoint rather than the internet provider's current public address.

Link normally avoids inbound port forwarding at the Gateway site; strict networks can still need an allow rule.
Link normally avoids inbound port forwarding at the Gateway site; strict networks can still need an allow rule. Open full-size diagram

This addresses a common Starlink/cellular problem: the site router may itself be behind the provider's CGNAT. A port-forwarding rule on that router cannot by itself create an inbound path through the provider's shared address.

Keep public and local addressing separate
SettingWith RadioPro Link
Remote client destinationThe provisioned Link endpoint and connection settings.
Gateway's local LAN addressStill needs valid local settings, using DHCP or a suitable static configuration.
Restricted network policyIT may need to allow the provisioned service traffic.

The Link announcement describes typical Starlink/default-router setups without router changes, while recognizing that strict networks can require an allow rule. Obtain the assigned destination and port requirements from CTI; do not open an entire port range or expose all Gateway management services.

Confirm Link provisioning and compatible versions before removing an existing remote-access arrangement. A direct local connection and a Link connection use different paths and may use different address entries.

Documentation

Back to RadioPro Link