Re: [Turnserver-users] Testing TURN server

[Sebastien V. <se...@ji...>]

Hi Gary,

See inline.

Le 05/04/12 16:54, Gary Thomas a écrit :
> I'm trying to understand how to deploy (and test) the TURN server.
> What I'd like to have is something like this:
>
>     TURN Server                     NAT              Client
>     1.2.3.4                         2.3.4.5
>                                     192.128.12.1     192.168.12.50
>
> What I think I understand is that the client behind the NAT
> (IPv4 192.168.12.50) can solicit an address from the TURN server
> to expose 192.168.12.50:12334?

By allocating an address from TURN server, client will be reachable 
through TURN server address (1.2.3.4:<port allocated _from_ the server>).

>   In this way there will exist some
> address, e.g. 1.2.3.4:9876, which represents the client address?
>
> I tried testing like this:
>     % test_turn_client -t udp -s 1.2.3.4 -p 192.168.12.50 -w 12334 -u user -g pass -d domain.org

The -p and -w flags is the peer and port you want to communicate (you 
can imagine a peer address like 6.7.8.9 in the internet).

You can read the RFC 5766 to have a better understanding of the protocol 
and its goal.

Best regards,
--
Seb

> I can see from the server the requests, etc:
>     08:14:54.814395 [turnserver.c:5224]     TurnServer start
>     08:14:54.814487 [turnserver.c:5358]     Cannot drop privileges
>     08:14:54.814495 [turnserver.c:5361]     Run with uid_real=0 gid_real=0 uid_eff=0 gid_eff=0
>     08:15:16.106308 [turnserver.c:4504]     Received UDP on listening address
>     08:15:16.106350 [turnserver.c:3270]     No message integrity
>     08:15:16.264369 [turnserver.c:4504]     Received UDP on listening address
>     08:15:16.264456 [turnserver.c:3578]     OK basic validation are done, process the TURN message
>     08:15:16.264466 [turnserver.c:2942]     Process a TURN message
>     08:15:16.264473 [turnserver.c:2302]     Allocate request received!
>     08:15:16.264483 [turnserver.c:2536]     lifetime: 165 seconds
>     08:15:16.264517 [turnserver.c:2767]     Account gary, allocations used: 1
>     08:15:16.264545 [turnserver.c:2903]     Allocation successful, send success allocate response
>     08:15:16.419083 [turnserver.c:4504]     Received UDP on listening address
>     08:15:16.419131 [turnserver.c:3578]     OK basic validation are done, process the TURN message
>     08:15:16.419139 [turnserver.c:2942]     Process a TURN message
>     08:15:16.419149 [turnserver.c:1627]     CreatePermission request received
>     08:15:16.419172 [turnserver.c:1767]     Install permission for 192.168.12.50 12334
>     08:15:16.419203 [turnserver.c:1806]     CreatePermission successful, send success CreatePermission response
>     08:15:16.603429 [turnserver.c:4504]     Received UDP on listening address
>     08:15:16.603468 [turnserver.c:3578]     OK basic validation are done, process the TURN message
>     08:15:16.603475 [turnserver.c:2942]     Process a TURN message
>     08:15:16.603482 [turnserver.c:1413]     Send indication received!
>     08:15:16.603490 [turnserver.c:502]      Tokendown bucket available: 150000, tokens requested: 1024
>     08:15:16.603496 [turnserver.c:1535]     Will not set DF flag
>     08:15:16.603507 [turnserver.c:1566]     Send data to peer
>
> I watched the transaction via wireshark and I can see the STUN messages
> up to the point where the 'send indication' reply is sent.  Then nothing
> and my client gets nothing as well.
>
> I'm sure I just don't understand how to use this and I didn't find much
> help in the documentation or list archives.
>
> Any help greatly appreciated.
>
> Thanks
>