check if STUN is working

[Tomo Tibi]

How to check if my network is ok for STUN.

Using RFC5766 3.2.3.8

I'm trying to connect my computer behind NAT to android mobilephone which is connected to mobile data (to test STUN functionality) for webRTC

I set "stun only" on my rfc5766 server, set IceServer parameter for webrtc peer connection object to {url:'stun:myRFC5766.com:3478'}

Logging on my chrome browser (running on computer behind NAT) shows that public ip address was found 

ICECandidate:{"sdpMLineIndex":1,"sdpMid":"data","candidate":"a=candidate:2158047068 1 udp 1686052607 myPublicIP 58210 typ srflx raddr 192.168.1.3 rport 58210 generation 0\r\n"}

Changing iceServer parameter to {url:'turn:myRFC5766.com:3478', "credential": "youhavetoberealistic", "username":"ninefingers"}

and disabling "stun only" on rfc5766, all works ok. TURN is working.

I'm wondering maybe my computer network is too restricted for STUN how can I test?

Also google public STUN servers also seem that aren't working for me. As I also tested with them.

Please help.

Thx.

[Oleg Moskalenko]

What you are experiencing is exactly the STUN connectivity test. Your browsers can connect with TURN but they cannot connect with STUN. That's the test that is enough for your purpose. Well, you have to be realistic.

If you want more information then search for the NAT types that cannot be traversed with STUN.

Oleg

--
You received this message because you are subscribed to the Google Groups "TURN Server (Open-Source project)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to turn-server-project-rfc57...@googlegroups.com.
To post to this group, send email to turn-server-project...@googlegroups.com.
Visit this group at http://groups.google.com/group/turn-server-project-rfc5766-turn-server.
For more options, visit https://groups.google.com/d/optout.

[Tomo Tibi]

You are correct, it seems that mobile internet provider is restrictive. I've tested connection between two computer both behind their NATs which connect to fixed line internet provider, and STUN works.

On Sunday, May 18, 2014 6:21:21 PM UTC+2, Oleg Moskalenko wrote:

What you are experiencing is exactly the STUN connectivity test. Your browsers can connect with TURN but they cannot connect with STUN. That's the test that is enough for your purpose. Well, you have to be realistic.

If you want more information then search for the NAT types that cannot be traversed with STUN.

Oleg

On May 18, 2014, at 5:46 AM, Tomo Tibi <crack...@gmail.com> wrote:

How to check if my network is ok for STUN.

Using RFC5766 3.2.3.8

I'm trying to connect my computer behind NAT to android mobilephone which is connected to mobile data (to test STUN functionality) for webRTC

I set "stun only" on my rfc5766 server, set IceServer parameter for webrtc peer connection object to {url:'stun:myRFC5766.com:3478'}

Logging on my chrome browser (running on computer behind NAT) shows that public ip address was found 

ICECandidate:{"sdpMLineIndex":1,"sdpMid":"data","candidate":"a=candidate:2158047068 1 udp 1686052607 myPublicIP 58210 typ srflx raddr 192.168.1.3 rport 58210 generation 0\r\n"}

Changing iceServer parameter to {url:'turn:myRFC5766.com:3478', "credential": "youhavetoberealistic", "username":"ninefingers"}

and disabling "stun only" on rfc5766, all works ok. TURN is working.

I'm wondering maybe my computer network is too restricted for STUN how can I test?

Also google public STUN servers also seem that aren't working for me. As I also tested with them.

Please help.

Thx.

--
You received this message because you are subscribed to the Google Groups "TURN Server (Open-Source project)" group.

To unsubscribe from this group and stop receiving emails from it, send an email to turn-server-project-rfc5766-turn-server+unsubscribe@googlegroups.com.
To post to this group, send email to turn-server-project-rfc5766-turn-...@googlegroups.com.