Firewall requirements

For optimal performance, verify that the network where AirSync and the AirSync client operates has the firewall configured to allow the following connections:

Relay connection

Relay connections are used in scenarios where direct connections between devices are not possible due to network configurations.

With wildcards

• TCP 443 for *.myviewboard.cloud
• TCP 443 for *.myviewboard.com
• TCP 443 for *.viewsonic.com
• TCP 443 for *.airsync.net

Without wildcards

For firewalls that don't allow wildcards.

• TCP 443 for airsync.net, www.airsync.net, airsync.viewsonic.com
• TCP 443 for:
  • api.gateway.airsync.net
  • us-east-1.gateway.airsync.net
  • ap-northeast-1.gateway.airsync.net
• TCP 443 for appconfig.airsync.net
• TCP 443 for getice.myviewboard.cloud
• TCP 443 for store2.myviewboard.com (OTA)
• TCP 443 for store2.airsync.net (OTA)

Video/Audio (WebRTC)

• TCP 443 for turn.myviewboard.cloud
• TCP 3478 for turn.myviewboard.cloud
• UDP 3478 for turn.myviewboard.cloud (Optional)
• Local UDP ports 32768~61000

Local Connection (Direct connection)

Establish a network connection directly between devices within the LAN without relying on external servers or services.

• TCP 5001

Remote Screen

• TCP 7000

Video/Audio (WebRTC)

• Random UDP ports in the range of 32768~61000

Mirror

AirPlay, Google cast, and Miracast do not require access to the Internet.

• AirPlay, Google Cast
  • Does not work in different subnet/VLAN
  • Random UDP ports in the range of 32768~61000
    
     
• Miracast
  • Use Wi-Fi Direct (WiFi P2P). Does not require wireless AP.

Notes

Ephemeral port range on Android or Linux:

adb shell cat /proc/sys/net/ipv4/ip_local_port_range

Limit WebRTC port range in Chrome

Chrome policies (WebRtcUdpPortRange) can limit the range of local UDP ports used by WebRTC. Refer to setting UDP port ranges in the following page:

• https://groups.google.com/g/discuss-webrtc/c/S5yex8rNIjA