TURN traversal behavior

42 views
Skip to first unread message

Diaz Soho

unread,
Aug 6, 2019, 11:37:22 PM8/6/19
to TURN Server (Open-Source project)
Hi all,

I would like to confirm the function support by cotrun project. 
1. Does TURN server play the role "relay" for all NAT type?
2. Does TURN server support  Peer to Peer for Full Cone NAT, Restricted Cone NAT, Port Restricted Cone NAT? 
3. Can I user a close network to test coturn TURN server:
     PC-1 is under NAT-A
     PC-2 is under NAT-B
     PC-3 is play the role TURN server
then how I can do the verification testing about TURN server function by coturn code?
as my understand:
PC-1 is turn client
PC-2 is turn client
PC-3 is turn server
is there any doc I  can refer for configuration?



Message has been deleted

shakeeb

unread,
Aug 8, 2019, 3:48:39 AM8/8/19
to TURN Server (Open-Source project)
Hi Diaz Soho,

>>1. Does TURN server play the role "relay" for all NAT type?

Yes. The relay will work for all NAT type.
  
>>2. Does TURN server support  Peer to Peer for Full Cone NAT, Restricted Cone NAT, Port Restricted Cone NAT? 

Yes. TURN server help to make Peer to Peer for Full Cone NAT, Restricted Cone NAT, Port Restricted Cone NAT. 
TURN server only helps to create the hole, detects the server reflexive address. The rest of the work is done by the client.
    
>>3. Can I user a close network to test coturn TURN server:
Yes. You can use a closed network.  

>> is there any doc I  can refer for configuration?
I have not found any.  I have some suggestion about how you can do this.
 
1. create two networks with NAT.  

  a. PC1<----network x ----->NAT-A<----network z ----->   
  b. PC2<----network y ----->NAT-B<----network z ----->   

2. put turn server on network z. 

3. use  turnutils_natdiscovery, turnutils_peer turnutils_stunclient turnutils_uclient for testing.

4. use ip address for turn server, don't use dns name.  

5. verify that you can ping turnserver from PC-1 and PC-2.

Thanks,
Shakeeb
Reply all
Reply to author
Forward
0 new messages