Firewall settings for CloudXR Server workstations
These instructions apply to the firewall of a dedicated workstation acting as a CloudXR server. They define the ports and protocols that must be open locally to enable communication with Innoactive Portal client application on the headset.
If you are instead configuring the corporate network firewall (for cloud or on-premises environments), refer to this article.
If you need help to optimize local streaming you can find further information (configuring antivirus and router channels) in this dedicated how to article.
Innoactive Spatial Runtime (CloudXR 6)
Component | Description | Direction | Protocol | Port |
|---|---|---|---|---|
Innoactive Spatial Runtime | Runtime Listener | Inbound | TCP | 42084 |
VRED / App Plugin | Plugin → Spatial Runtime | Outbound | TCP | 42084 |
CloudXrService | CloudXR RTSP | Inbound | TCP | 48010 |
CloudXrService | CloudXR Control | Inbound | TCP | 48322 |
CloudXrService | CloudXR Video | Inbound | UDP | 47998 |
CloudXrService | CloudXR Control | Inbound | UDP | 47999 |
CloudXrService | CloudXR Audio | Inbound | UDP | 48000 |
CloudXrService | CloudXR Microphone | Inbound | UDP | 48002 |
CloudXrService | CloudXR Video | Inbound | UDP | 48005 |
CloudXrService | CloudXR Video | Inbound | UDP | 48008 |
CloudXrService | CloudXR Video | Inbound | UDP | 48012 |
NvStreamManager | No external network communication (IPC only) | — | — | — |
Previous Versions
Description | Direction* | Protocol | Port |
|---|---|---|---|
CloudXR Control | Inbound | UDP | 47999 |
CloudXR Audio | Inbound | UDP | 48000 |
CloudXR Video | Inbound | UDP | 47998, 48005, 48008, 48012, 47995, 48001 |
CloudXR Microphone | Inbound | UDP | 48002 |
CloudXR RTSP | Inbound | TCP | 48010 |
CloudXR Control | Outbound | UDP | 49006 |
CloudXR Audio | Outbound | UDP | 49003 |
CloudXR Video | Outbound | UDP | 49005, 50000–55000 |
CloudXR Microphone | Outbound | UDP | 49004 |
CloudXR RTSP | Outbound | TCP | 49007 |
* All directions are from the dedicated workstation/server perspective.
Whitelist all IPs that could be used by your HMD, so either allow all IP addresses on those ports or limit to the IP range that the HMDs will use.