Skip to content
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

Issue with TURN and symmetric NAT behavior. #285

Open
mkm85 opened this issue Jan 3, 2025 · 1 comment
Open

Issue with TURN and symmetric NAT behavior. #285

mkm85 opened this issue Jan 3, 2025 · 1 comment

Comments

@mkm85
Copy link

mkm85 commented Jan 3, 2025

I have discovered an issue when running the TURN test while the machine performing the test is behind symmetric NAT (wifi teethering from my phone) https://github.com/paullouisageneau/libjuice/blob/master/test/turn.c

I originally discovered the problem using LibDataChannel with libjuice but it can be reproduced with just libjuice.

It seems like libjuice wrongly filters out a packet coming from the TURN server because the port number does not match, because of the symmetric NAT.

I've tried to fix the filtering issue, but then the rendezvous still fails as the ip:port tupple is not added to the list of candidates and the rendezvous still fails.

@paullouisageneau
Copy link
Owner

Thank you for reporting. Could you please clarify two things:

  • What port number does not match exactly? NATs translate the source address of outgoing packets and the destination address of corresponding incoming packets, so packets sent from the TURN server to an agent (i.e. incoming packets) can't have the source address changed.
  • libjuice does not filter by port number. What have you fixed exactly?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants