PeerJS — True peer-to-peer data in the browser

Re:PeerJS — True peer-to-peer data in the browser by huhtenberg on Thursday February 14, 2013 @08:24AM (#5219296)

> Note that no peer-to-peer data goes through the server; The server acts only to broker connections.

Q1. Does this support connecting to a peer behind a NAT device?

Q2. Does this support connecting two peers each behind its own NAT?

Because a vast majority of real world cases will fall into either of these two categories.

[ Parent | on HN ]

Re:PeerJS — True peer-to-peer data in the browser by churreiro on Thursday February 14, 2013 @08:33AM (#5219339)

It is NAT reversal, even there are still many issues to be solved with the ICE. WebRTC team is working fast in this aspect...

BTW, consider that they are shipping first final version in march so NAT reversal is important. YEY!

[ Parent | on HN ]

Re:PeerJS — True peer-to-peer data in the browser by vr000m on Thursday February 14, 2013 @08:41AM (#5219374)

It uses SDP to exchange ICE candidates. At the moment the SDP tries to multiplex video/audio and SCTP (data channel).

[ Parent | on HN ]

Re:PeerJS — True peer-to-peer data in the browser by latitude on Thursday February 14, 2013 @08:56AM (#5219435)

Does WebRTC have any sort of extension mechanism whereby I can drop in my own version of NAT traversal logic?

Speaking from past experience, STUN and ICE are OK, but they got the whole process fundamentally wrong. They let the clients drive the traversal process. This is substantially inferior to letting a dedicated mediating server do that instead. I did that with one of my past projects and it helped with connecting peers in a large number of obscure scenarios.

[ Parent | on HN ]

Re:PeerJS — True peer-to-peer data in the browser by churreiro on Thursday February 14, 2013 @09:25AM (#5219537)

You should hack the Chromium webkit for this.

[ Parent | on HN ]

Re:PeerJS — True peer-to-peer data in the browser by vr000m on Friday February 15, 2013 @08:45AM (#5226082)

you can add one or more TURN server(s) into the mix, but apart from that there is no other way using just Javascript.

[ Parent | on HN ]

Re:PeerJS — True peer-to-peer data in the browser by ericz on Thursday February 14, 2013 @01:03PM (#5220792)

ICE/STUN (which is used by WebRTC and thus PeerJS) support NAT traversal in all cases but a pair of symmetric NATs, which means some single digit percentage of connections will not work. For those cases, WebRTC/PeerJS support using a TURN server which proxies the data, not ideal but it allows the library to work.

[ Parent | on HN ]

Re:PeerJS — True peer-to-peer data in the browser by vr000m on Friday February 15, 2013 @08:47AM (#5226088)

AFAIK, you will be/are able to add TURN server addresses to the mix. It is possible that chrome uses google's TURN servers by default.

[ Parent | on HN ]

Re:PeerJS — True peer-to-peer data in the browser by dalore on Thursday February 14, 2013 @08:29AM (#5219321)

Handles NAT traversals

[ Parent | on HN ]

Re:PeerJS — True peer-to-peer data in the browser by huhtenberg on Thursday February 14, 2013 @08:33AM (#5219337)

Any details?

[ Parent | on HN ]

Re:PeerJS — True peer-to-peer data in the browser by churreiro on Thursday February 14, 2013 @08:36AM (#5219353)

http://dev.w3.org/2011/webrtc/editor/webrtc.html#rtciceserve...

Specifications here

[ Parent | on HN ]