coturn / coturn

coturn TURN server project

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Alias IP Setup and External Address

Tabarane opened this issue · comments

Network Setup and Coturn Configuration Issue

Current Setup

Video Back End Server:

  • Actual IP: 172.17.198.25
  • Alias IP for VLAN: 10.9.147.71
  • Port Mirror APN: 172.17.172.179

Coturn Server Address:

  • Actual IP: 172.17.198.22
  • Alias IP for VLAN: 10.9.147.72
  • Port Mirror APN: 172.17.172.159

Clients

  1. First Client Machine (From Port Mirror Network)

    • IP: 10.250.200.91
    • Connection Path: Backend via 172.17.172.179
    • Coturn Config: EXTERNALIP=172.17.172.179/172.17.198.25
    • Status: Video works perfectly
  2. Second Client Machine (From VLAN Network)

    • IP: 10.2.22.241
    • Connection Path: Backend via 10.9.147.71
    • Coturn Config: EXTERNALIP=10.9.147.71/172.17.198.25
    • Status: Video works perfectly

Coturn Configuration

# STUN APN WAN to SRV LAN
external-ip=172.17.172.159/172.17.198.22
external-ip=10.9.147.72/172.17.198.22
# WWAN
#external-ip=172.17.172.159/10.250.200.130 

# Backend VLAN Map
external-ip=10.9.147.71/172.17.198.25

# Backend PortMirror Map
#external-ip=172.17.172.179/172.17.198.25

listening-ip=0.0.0.0

Issue

When both EXTERNALIP addresses are configured in Coturn, neither client setup works. The goal is to have both client types operational simultaneously. The custom WebRTC service can only use one STUN address or switch to another if the first one is down.

Seeking Solution

Looking for a solution or confirmation if this setup is feasible with the current network and Coturn configuration.