You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wonder if a structure like the one in the drawing will work, and if so, how? I've been working on it but I haven't reached a result. If the Turn Server has a public IP address, it works. But when it runs on a private network and accesses the internet via Nat Gateway, my WebRTC software does not work. There are no restrictions on Security Groups for testing.
I would appreciate it if you could help me figure out how to fix it.
The text was updated successfully, but these errors were encountered:
Hi @mrtux2024 - sorry but your diagram is not clear...
Maybe if you can configure your nat gateway to work in direct port mapping mode that can work.
Try to review if public/private IP mapping option of --external-ip which requires direct mapping (sorry I do not know enough about AWS NLB/NAT gateway to say if it is possible).
The idea is that NAT EXTERNAL_IP1 is mapped to internal private TURN_IP2 and traffic from client that comes to EXTERNAL_IP1:PORT1 goes to TURN_IP2:PORT1 (same port number). This should work.
I wonder if a structure like the one in the drawing will work, and if so, how? I've been working on it but I haven't reached a result. If the Turn Server has a public IP address, it works. But when it runs on a private network and accesses the internet via Nat Gateway, my WebRTC software does not work. There are no restrictions on Security Groups for testing.
I would appreciate it if you could help me figure out how to fix it.
The text was updated successfully, but these errors were encountered: