testRTC offers firewall profiles to check TURN connectivity. Below are the details of each firewall profile configuration and the ports it keeps open.
Note that you can use .rtcSetNetwork() and .rtcSetNetworkProfile() to dynamically change the network configuration.
No Firewall
All ports are open
FW – HTTP and HTTPS Allowed
| Management ports | |
| Secured remote connection to the machine | TCP 22 |
| Agents’ management port | TCP 2376 |
| VNC connection for tests scripts’ debugging | TCP 5900-5904 |
| Activity ports | |
| DNS outbound | TCP and UDP 53 |
| Browsing and WebRTC communication traffic | HTTPS: TCP 443 |
| HTTP: TCP 80 |
FW – HTTPS Allowed
| Management ports | |
| Secured remote connection to the machine | TCP 22 |
| Agents’ management port | TCP 2376 |
| VNC connection for tests scripts’ debugging | TCP 5900-5904 |
| Activity ports | |
| DNS outbound | TCP and UDP 53 |
| Browsing and WebRTC communication traffic | HTTPS: TCP 443 |
FW – Baseline
In this profile, only ports that are required for the agent operation are open.
| Management ports | |
| Secured remote connection to the machine | TCP 22 |
| Agents’ management port | TCP 2376 |
| VNC connection for tests scripts’ debugging | TCP 5900-5904 |
| Activity ports | |
| DNS outbound | TCP and UDP 53 |
Network profiles
| Profile | Bandwidth | Latency | Packet loss | |
| No throttling | No limitation | 0 | 0% | |
| Call Drop | 50 Kbps | 500ms | 20% | |
| DSL | 8 Mbps | 40ms | 0.5% | |
| Very Bad Network | 1 Mbps | 500ms | 10% | |
| Wifi | 30 Mbps | 40ms | 0.2% | |
| Wifi High packet loss | 30 Mbps | 40ms | 5% | |
| Regular 2.5G | 150 Kbps | 200ms | 3% | |
| Regular 3G | 750 Kbps | 250ms | 1.5% | |
| Poor 3G | 400 Kbps | 350ms | 5% | |
| Regular 4G | 4 Mbps | 0 | 2% | |
| Poor 4G | 4 Mbps | 350ms | 5% | |
| Unstable 4G | 4 Mbps | 500ms | 10% | |
| High Latency 4G | 4 Mbps | 600ms | 0.2% | |
| High Packet Loss 4G | 4 Mbps | 5ms | 20% | |
| 50% Packet Loss | 40 Mbps | 10ms | 50% |