Add external-ip support for coturn (#1439)

Handles the case when users are running Coturn with peers in the same network, and these peers connect to the relay server via private IP addresses (e.g., Oracle cloud), which causes relay candidates to be allocated using private IP addresses. This causes issues with external peers who can't reach these private addresses.

Use the provided IP address with NETBIRD_TURN_EXTERNAL_IP or discover the address via https://jsonip.com API.

For quick-start guide with Zitadel, we only use the discover method with the external API
This commit is contained in:
Maycon Santos
2024-01-10 13:03:46 +01:00
committed by GitHub
parent 72a1e97304
commit c61cb00f40
7 changed files with 53 additions and 2 deletions

View File

@@ -132,6 +132,7 @@ tls-listening-port=5349
#external-ip=60.70.80.91/172.17.19.101
#external-ip=60.70.80.92/172.17.19.102
$TURN_EXTERNAL_IP_CONFIG
# Number of the relay threads to handle the established connections
# (in addition to authentication thread and the listener thread).