CloudXR Network Setup

NVIDIA CloudXR SDK has built-in resilience to handle typical networking conditions. However, here are some best practices to remember:

• Ideally, the server should be on a wired network.

  If the server is running in a home setting, it should have a direct connection to the router’s LAN (not WAN) port.
• There should only be one wireless network hop in the path.
• The client or the server can be on a wireless network but not both.
• Wi-Fi-enabled client devices need to be on the 5GHz band.

  We recommend using beam forming routers.

Warning

CloudXR does not support network connections with high levels of latency or packet drops. This might include solutions such as Powerline ethernet where not all hardware or electrical wiring is equal, or tunneled network services (VPN or similar).

CloudXR assumes that the client and server are connected over Ethernet and on the same Local Area Network by default and adjusts its Quality of Service settings accordingly.

Network configuration settings are controlled from the client, and can be changed via the Client Command-Line Options -nic and -nt options, or by modifying the values set in cxrConnectionDesc in the code, in order to customize QoS for the following varying network conditions:

Client Network interface:

• Ethernet (-nic ethernet)
• Wi-Fi 5GHz (-nic wifi5ghz)
• Wi-Fi 2.4Ghz (-nic wifi24ghz)
• Mobile LTE (-nic mobilelte)
• Mobile 5G (-nic mobile5g)

Network topology:

• LAN (-nt lan)
• WAN (-nt wan)

Congestion control: - | L4S (-l4s)

In a network environment that supports L4S CloudXR can be configured to adjust its Quality of Service algorithm to account for congestion markings.

These settings can be changed via the Client Command-Line Options (-l4s as noted above), or by modifying values set in the cxrConnectionDesc by the sample clients in order to customize QoS further for L4S.

Ports Required for Streaming

The CloudXR installer will attempt to open the ports that are associated with CloudXR in the Windows Firewall. If the connection cannot be established, turn Windows Firewall off temporarily and try again. Firewall and NAT issues are the top reasons for connectivity issues.

Here are the ports that are used by the client and server:

Server		Client
Control	47999	Control	49006
Audio	48000	Audio	49003
Video	47998, 48005	Video	49005, 50000-55000
Microphone	48002	Microphone	49004
RTSP	48010	RTSP	49007

Note

All ports needed are UDP, except RTSP, which is TCP.

The RTSP stream is used to establish the initial connection to the server. Once this is done the individual network streams transmit data over a UDP-based network stack that can run normal ‘lossy’ UDP packets, or can be configured to emulate TCP-like requirements such as in-order and guaranteed delivery.