feross / feross/simple-peer

Clients behind Non-symmetrical NAT failed to connect with each other. STUN servers worked only for clients within same network

Open
#872 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
7.8k
Forks
983
PR merge metrics
No merged PRs in 30d

Description

**What version of this package are you using?**
Latest from NPM

**What happened?**
Connection with video stream failed. All similar issues answers suggest that TURN server is required to solve it BUT accordingly to RFC this ONLY should be required to connect clients when at least one of clients is behind symmetric NAT.

NAT was tested with that [tool](https://tomchen.github.io/symmetric-nat-test/) [repo](https://github.com/tomchen/symmetric-nat-test)

**What did you expect to happen?**
Connection to be created.

**Are you willing to submit a pull request to fix this bug?**
I have no idea why it doesn't work, unfortunately :(

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.