NAT Traversal problem!

[k.geo...@cst-bg.net]

Hi PeerJS team,
Firs i want to tell you GREAT WORK.I have been using peerjs and its works perfectly on local network. I want it to test it how good is behind NAT but there is no positive resaults. It cant pass the NAT.

Greetings,
Kostadin

[roe...@gmail.com]

First I have to agree with the GREAT WORK comment :)

I just found out today a problem that's sounds similar to yours.

I'll post logs tomorrow if you think it's relevant. 

This issue only happens when I try to open a peer connection in an "Enterprise" like networks (big company offices, McDonald, universities etc...). Which makes me suspect NAT as well, although I have to admit this area is not my strong side.

The problem I'm having is when I create a new Peer() and send a POST command to the server under https://www.***.com/peerjs/%%%% , it receives an error and the process stops.

My peer server listens on port 9000. 

Do you think these problems are related?

[Kostadin Georgiev]

I found a description in PeerJS page which clearly say that: Peers behind symmetric NAT can't be connected without signaling server and the PeerJS server haven't this option.

A very low percentage of users are behind symmetric NATs. When two symmetric NAT users try to connect to each other, NAT traversal is impossible and no connection can be made. A workaround is to proxy through what is known as a TURN server. The PeerServer cloud service does not provide a TURN server. You'll have to find your own. You can pass a TURN server into the Peer object options. This will allow your PeerJS app to work seamlessly for this situation

[Eric Zhang]

@roe...@gmail.com, @Kostadin

Hmm if a connection is failing at that step then something is going on other than symmetric NAT.

When the symmetric NAT is the problem, you'll see all the steps complete but not data connection open event will fire.

@roeeyud, can you send me some console output or the network panel logs on that failed POST request?

On Tue, Sep 10, 2013 at 5:30 AM, Kostadin Georgiev <k.geo...@cst-bg.net> wrote:

I found a description in PeerJS page which clearly say that: Peers behind symmetric NAT can't be connected without signaling server and the PeerJS server haven't this option.

A very low percentage of users are behind symmetric NATs. When two symmetric NAT users try to connect to each other, NAT traversal is impossible and no connection can be made. A workaround is to proxy through what is known as a TURN server. The PeerServer cloud service does not provide a TURN server. You'll have to find your own. You can pass a TURN server into the Peer object options. This will allow your PeerJS app to work seamlessly for this situation

--
510-691-3951
http://ericzhang.com

[roe...@gmail.com]

Attached are a few of the errors I saw on the network panel.

These logs are all from the same session.

I would post more from this session but I'm not sure if the user just retried to establish connection a few times because the messages seem to repeat themselves.

Thanks! 

[roe...@gmail.com]

hey Eric did you get a chance to check the logs I've sent you?

[roe...@gmail.com]

Hey Eric your comment about using port 80 worked!!!! Thanks again!