Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upNAT traversal #70
Closed
NAT traversal #70
Comments
This comment has been minimized.
This comment has been minimized.
|
As for the first peer connection I'm not sure, but there are plans to allow peers to introduce each other. |
This comment has been minimized.
This comment has been minimized.
|
There's no rule that says webrtc signaling must be done using a centralized web server. Once you've connected to any webrtc peer, they can introduce you to new peers. Peers themselves can act as the middle man (i.e. signaling server). :) Getting close to the point where I can publish the first implementation of this. Stay tuned. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi, I've been doing some research recently on building distributed internet resources, and am intrigued by webtorrent. You appear to have put together some good ideas, but I wonder how NAT traversal will be solved. From what I have found, until IPv6 is prevalent, it looks very difficult without some sort of signalling server (which would of course imply partial centralisation), such as STUN. Is there anything in your notes which shows a way round this? I see you've suggested NAT-PMP, but this appears to require opening a UDP connection, which of course the browser can't do.