-
Notifications
You must be signed in to change notification settings - Fork 159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connection failing to TCP candidate when listening on multiple interfaces using MultiTCPMux
and NAT1To1IPs
#583
Comments
This appears to be somewhat similar to #505 but the problem does not appear to be the same connection getting closed but more like any subsequent connection with the same address so simply ignoring duplicate candidates isn't helping. @cnderrauber Wondering if you have any clue on what could be causing this, whether a misconfiguration or else. |
Your config looks weird, is there a special reason to map the loopback ip to an external ip? I don't think it can work as the external traffic will only arrive to your private ip 172.x |
Indeed that's a bit weird but since it was working fine in the |
If your are trying to make tcp mux listening on a single port of all interfaces, you don't need a MultiTCPMux. I think it is designed for listening on multiple tcp ports. You can refer to the livekit for the correct usage in your case, also with correct nat mapping
|
That's likely the key misconception on my part. I implicitly thought I appreciate your help on this, thanks! |
Your environment.
I am hitting similar problems I had in #541 but this time with TCP candidates. It seems I cannot get the
NAT1To1IPs
mapping to work correctly when listening on multiple interfaces and usingMultiTCPMux
. Listening on a single interface works as expected.Server setup is very simple, standard EC2 with loopback and a private IP:
127.0.0.1
172.27.134.52
External IP is
54.196.153.204
Attaching logs of both attempts.
Single interface (working):
NAT mapping is:
[54.196.153.204/172.27.134.52]
.Multiple interfaces (not working, timing out):
NAT mapping is:
[54.196.153.204/127.0.0.1 172.27.134.52/172.27.134.52]
.The text was updated successfully, but these errors were encountered: