check_stun_auth: Cannot find credentials of user

2,999 views
Skip to first unread message

iuli bac

unread,
May 19, 2014, 9:03:05 AM5/19/14
to turn-server-project...@googlegroups.com
Hy there!
installed turnserver then >> sudo turnserver -a  -b turnuserdb.conf  -L 172.31.37.x -X 54.187.87.x -E 172.31.37.x -f  -r site.ro -v

in turnuserdb.conf :  iuli:password
And is not working? hmmm why?

67: handle_udp_packet: New UDP endpoint: local addr 172.31.37.x:3478, remote addr 213.2                                    33.92.66:15273
67: session 000000000000000001: user <>: incoming packet BINDING processed, success
67: session 000000000000000001: user <>: incoming packet BINDING processed, success
67: handle_udp_packet: New UDP endpoint: local addr 172.31.37.x:3478, remote addr 213.2                                    33.92.66:44984
67: session 000000000000000002: user <>: incoming packet message processed, error 401: Un                                    authorised
67: session 000000000000000001: user <>: incoming packet BINDING processed, success
67: session 000000000000000002: user <>: incoming packet message processed, error 401: Un                                    authorised
67: IPv4. tcp or tls connected to: 213.233.92.66:44983
67: session 000000000000000003: user <>: incoming packet message processed, error 401: Un                                    authorised
67: IPv4. Local relay addr: 172.31.37.x:56400
67: session 000000000000000002: new, username=<iuli>, lifetime=600
67: session 000000000000000002: user <iuli>: incoming packet ALLOCATE processed, success
67: session 000000000000000003: user <>: incoming packet message processed, error 401: Un                                    authorised
68: session 000000000000000002: user <iuli>: incoming packet ALLOCATE processed, success
68: IPv4. tcp or tls connected to: 213.233.92.66:38720
68: ERROR: check_stun_auth: user iuli credentials are incorrect
68: session 000000000000000003: user <iuli>: incoming packet message processed, error 401                                    : Unauthorised
68: ERROR: check_stun_auth: user iuli credentials are incorrect
68: session 000000000000000003: user <iuli>: incoming packet message processed, error 401                                    : Unauthorised
68: IPv4. tcp or tls connected to: 86.123.167.x:39903
68: session 000000000000000002: user <iuli>: incoming packet CREATE_PERMISSION processed,                                     success
68: session 000000000000000002: user <iuli>: incoming packet CREATE_PERMISSION processed,                                     success
68: session 000000000000000005: user <>: incoming packet message processed, error 401: Un                                    authorised
68: session 000000000000000002: user <iuli>: incoming packet CREATE_PERMISSION processed,                                     success
68: session 000000000000000005: user <>: incoming packet message processed, error 401: Un                                    authorised
69: ERROR: check_stun_auth: user iuli credentials are incorrect
69: session 000000000000000005: user <iuli>: incoming packet message processed, error 401                                    : Unauthorised
69: ERROR: check_stun_auth: user iuli credentials are incorrect
69: session 000000000000000005: user <iuli>: incoming packet message processed, error 401                                    : Unauthorised
69: ERROR: check_stun_auth: user iuli credentials are incorrect
69: session 000000000000000005: user <iuli>: incoming packet message processed, error 401                                    : Unauthorised
77: session 000000000000000001: user <>: incoming packet BINDING processed, success
77: session 000000000000000001: user <>: incoming packet BINDING processed, success
78: session 000000000000000004: TCP socket closed remotely 213.233.92.66:38720
78: session 000000000000000004: closed (2nd stage), user <>, local 172.31.37.x:3478, re                                    mote213.233.92.66:38720, reason: TCP connection closed by client (callback)
88: session 000000000000000001: user <>: incoming packet BINDING processed, success
88: session 000000000000000001: user <>: incoming packet BINDING processed, success
98: session 000000000000000001: user <>: incoming packet BINDING processed, success
98: session 000000000000000001: user <>: incoming packet BINDING processed, success
108: session 000000000000000001: user <>: incoming packet BINDING processed, success
108: session 000000000000000001: user <>: incoming packet BINDING processed, success
118: session 000000000000000001: user <>: incoming packet BINDING processed, success
119: session 000000000000000001: user <>: incoming packet BINDING processed, success
127: session 000000000000000001: closed (2nd stage), user <>, local 172.31.37.x:3478, remote 213.233.92.66:15273, reason: allocation watchdog determined stale session state
127: session 000000000000000003: closed (2nd stage), user <iuli>, local 172.31.37.x:3478, remote 213.233.92.66:44983, reason: allocation watchdog determined stale session state
128: session 000000000000000005: closed (2nd stage), user <iuli>, local 172.31.37.x:3478, remote 86.123.167.207:39903, reason: allocation watchdog determined stale session state
129: handle_udp_packet: New UDP endpoint: local addr 172.31.37.x:3478, remote addr 213.233.92.66:15273
129: session 000000000000000006: user <>: incoming packet BINDING processed, success
129: session 000000000000000006: user <>: incoming packet BINDING processed, success
139: session 000000000000000006: user <>: incoming packet BINDING processed, success

Oleg Moskalenko

unread,
May 19, 2014, 12:40:50 PM5/19/14
to turn-server-project...@googlegroups.com
One of your sessions was able to authenticate, correctly (the ***2 one). Why others were not successful - you have to check your client application operation.

iuli bac

unread,
May 20, 2014, 1:18:39 AM5/20/14
to turn-server-project...@googlegroups.com
I make this test to see where is the mistake

From another ec2> utils-client>> first with wrong password then with right one!
0: allocate sent
0: allocate response received:
0: allocate sent
0: allocate response received:
0: allocate sent
0: allocate response received:
0: allocate sent
0: allocate response received:
0: allocate sent
0: allocate response received:
0: allocate sent
0: allocate response received:
0: allocate sent
0: allocate response received:
0: allocate sent
0: allocate response received:
0: allocate sent
0: allocate response received:
0: allocate sent
0: allocate response received:
0: allocate sent
0: allocate response received:
0: allocate sent
0: allocate response received:
0: allocate sent
0: allocate response received:
0: allocate sent
0: allocate response received:
0: allocate sent
0: allocate response received:
0: allocate sent
0: allocate response received:
0: allocate sent
0: allocate response received:
0: allocate sent
0: allocate response received:
0: allocate sent
0: allocate response received:
0: allocate sent
0: allocate response received:
0: allocate sent
0: allocate response received:
0: allocate sent
0: allocate response received:
0: allocate sent
0: allocate response received:
0: allocate sent
0: allocate response received:
0: allocate sent
0: allocate response received:
0: allocate sent
0: allocate response received:
0: allocate sent
0: allocate response received:
0: allocate sent
0: allocate response received:
0: allocate sent
0: allocate response received:
0: allocate sent
0: allocate response received:
0: allocate sent
0: allocate response received:
0: allocate sent
0: allocate response received:
0: Cannot complete Allocation
0: ERROR: Cannot complete Allocation


1: start_mclient: msz=2, tot_send_msgs=0, tot_recv_msgs=0, tot_send_bytes ~ 0, tot_recv_bytes ~ 0
2: start_mclient: msz=2, tot_send_msgs=0, tot_recv_msgs=0, tot_send_bytes ~ 0, tot_recv_bytes ~ 0
3: start_mclient: msz=2, tot_send_msgs=49, tot_recv_msgs=0, tot_send_bytes ~ 4900, tot_recv_bytes ~ 0
4: start_mclient: msz=2, tot_send_msgs=150, tot_recv_msgs=0, tot_send_bytes ~ 15000, tot_recv_bytes ~ 0
5: start_mclient: msz=2, tot_send_msgs=241, tot_recv_msgs=0, tot_send_bytes ~ 24100, tot_recv_bytes ~ 0
6: start_mclient: msz=2, tot_send_msgs=341, tot_recv_msgs=0, tot_send_bytes ~ 34100, tot_recv_bytes ~ 0
7: start_mclient: msz=2, tot_send_msgs=442, tot_recv_msgs=0, tot_send_bytes ~ 44200, tot_recv_bytes ~ 0
8: start_mclient: msz=2, tot_send_msgs=545, tot_recv_msgs=0, tot_send_bytes ~ 54500, tot_recv_bytes ~ 0
9: start_mclient: msz=2, tot_send_msgs=645, tot_recv_msgs=0, tot_send_bytes ~ 64500, tot_recv_bytes ~ 0
10: start_mclient: msz=2, tot_send_msgs=748, tot_recv_msgs=0, tot_send_bytes ~ 74800, tot_recv_bytes ~ 0
11: start_mclient: msz=2, tot_send_msgs=849, tot_recv_msgs=0, tot_send_bytes ~ 84900, tot_recv_bytes ~ 0
12: start_mclient: msz=2, tot_send_msgs=949, tot_recv_msgs=0, tot_send_bytes ~ 94900, tot_recv_bytes ~ 0
13: start_mclient: msz=2, tot_send_msgs=1050, tot_recv_msgs=0, tot_send_bytes ~ 105000, tot_recv_bytes ~ 0
14: start_mclient: msz=2, tot_send_msgs=1141, tot_recv_msgs=0, tot_send_bytes ~ 114100, tot_recv_bytes ~ 0
15: start_mclient: msz=2, tot_send_msgs=1241, tot_recv_msgs=0, tot_send_bytes ~ 124100, tot_recv_bytes ~ 0
16: start_mclient: msz=2, tot_send_msgs=1342, tot_recv_msgs=0, tot_send_bytes ~ 134200, tot_recv_bytes ~ 0
17: start_mclient: msz=2, tot_send_msgs=1443, tot_recv_msgs=0, tot_send_bytes ~ 144300, tot_recv_bytes ~ 0
18: start_mclient: msz=2, tot_send_msgs=1543, tot_recv_msgs=0, tot_send_bytes ~ 154300, tot_recv_bytes ~ 0
19: start_mclient: msz=2, tot_send_msgs=1644, tot_recv_msgs=0, tot_send_bytes ~ 164400, tot_recv_bytes ~ 0
20: start_mclient: msz=2, tot_send_msgs=1745, tot_recv_msgs=0, tot_send_bytes ~ 174500, tot_recv_bytes ~ 0
21: start_mclient: msz=2, tot_send_msgs=1845, tot_recv_msgs=0, tot_send_bytes ~ 184500, tot_recv_bytes ~ 0
22: start_mclient: msz=2, tot_send_msgs=1946, tot_recv_msgs=0, tot_send_bytes ~ 194600, tot_recv_bytes ~ 0
23: start_mclient: msz=2, tot_send_msgs=2000, tot_recv_msgs=0, tot_send_bytes ~ 200000, tot_recv_bytes ~ 0
24: start_mclient: msz=2, tot_send_msgs=2000, tot_recv_msgs=0, tot_send_bytes ~ 200000, tot_recv_bytes ~ 0
25: start_mclient: msz=2, tot_send_msgs=2000, tot_recv_msgs=0, tot_send_bytes ~ 200000, tot_recv_bytes ~ 0
26: start_mclient: msz=2, tot_send_msgs=2000, tot_recv_msgs=0, tot_send_bytes ~ 200000, tot_recv_bytes ~ 0
27: start_mclient: msz=2, tot_send_msgs=2000, tot_recv_msgs=0, tot_send_bytes ~ 200000, tot_recv_bytes ~ 0
27: done, connection 0xb71f2008 closed.
27: done, connection 0xb87db468 closed.
27: start_mclient: tot_send_msgs=2000, tot_recv_msgs=0
27: start_mclient: tot_send_bytes ~ 200000, tot_recv_bytes ~ 0
27: Total transmit time is 27
27: Total lost packets 2000 (100.000000%), total send dropped 0 (0.000000%)
27: Average round trip delay 0.000000 ms; min = 4294967295 ms, max = 0 ms
27: Average jitter -nan ms; min = 4294967295 ms, max = 0 ms


on the turnserver get this!
........................................................................
84: ERROR: check_stun_auth: user iuli credentials are incorrect
84: session 000000000000000001: user <iuli>: incoming packet message processed, error 401: Unauthorised
84: ERROR: check_stun_auth: user iuli credentials are incorrect
84: session 000000000000000001: user <iuli>: incoming packet message processed, error 401: Unauthorised
84: ERROR: check_stun_auth: user iuli credentials are incorrect
84: session 000000000000000001: user <iuli>: incoming packet message processed, error 401: Unauthorised
84: ERROR: check_stun_auth: user iuli credentials are incorrect
84: session 000000000000000001: user <iuli>: incoming packet message processed, error 401: Unauthorised
84: ERROR: check_stun_auth: user iuli credentials are incorrect
84: session 000000000000000001: user <iuli>: incoming packet message processed, error 401: Unauthorised
84: ERROR: check_stun_auth: user iuli credentials are incorrect
84: session 000000000000000001: user <iuli>: incoming packet message processed, error 401: Unauthorised
84: ERROR: check_stun_auth: user iuli credentials are incorrect
84: session 000000000000000001: user <iuli>: incoming packet message processed, error 401: Unauthorised
84: ERROR: check_stun_auth: user iuli credentials are incorrect
84: session 000000000000000001: user <iuli>: incoming packet message processed, error 401: Unauthorised
84: ERROR: check_stun_auth: user iuli credentials are incorrect
84: session 000000000000000001: user <iuli>: incoming packet message processed, error 401: Unauthorised
84: session 000000000000000001: TCP socket closed remotely 54.187.70.x:36714
84: session 000000000000000001: closed (2nd stage), user <iuli>, local 172.31.37.x:3478, remote 54.187.70.x:36714, reason: TCP connection closed by client (callback)
105: IPv4. tcp or tls connected to: 54.187.70.x:36715
105: session 000000000000000002: user <>: incoming packet message processed, error 401: Unauthorised
105: IPv4. Local relay addr: 172.31.37.x:51232
105: IPv4. Local reserved relay addr: 172.31.37.x:51233
105: session 000000000000000002: new, username=<iuli>, lifetime=800
105: session 000000000000000002: user <iuli>: incoming packet ALLOCATE processed, success
105: session 000000000000000002: refreshed, username=<iuli>, lifetime=600
105: session 000000000000000002: user <iuli>: incoming packet REFRESH processed, success
105: IPv4. tcp or tls connected to: 54.187.70.x:36716
105: IPv4. tcp or tls connected to: 54.187.70.x:36717
105: session 000000000000000003: user <>: incoming packet message processed, error 401: Unauthorised
105: IPv4. Local relay addr (RTCP): 172.31.37.x:51233
105: session 000000000000000003: new, username=<iuli>, lifetime=800
105: session 000000000000000003: user <iuli>: incoming packet ALLOCATE processed, success
105: session 000000000000000003: refreshed, username=<iuli>, lifetime=600
105: session 000000000000000003: user <iuli>: incoming packet REFRESH processed, success
105: session 000000000000000004: user <>: incoming packet message processed, error 401: Unauthorised
105: IPv4. Local relay addr: 172.31.37.x:65220
105: IPv4. Local reserved relay addr: 172.31.37.x:65221
105: session 000000000000000004: new, username=<iuli>, lifetime=800
105: session 000000000000000004: user <iuli>: incoming packet ALLOCATE processed, success
105: session 000000000000000004: refreshed, username=<iuli>, lifetime=600
105: session 000000000000000004: user <iuli>: incoming packet REFRESH processed, success
105: session 000000000000000003: user <iuli>: incoming packet CHANNEL_BIND processed, success
105: session 000000000000000003: user <iuli>: incoming packet CHANNEL_BIND processed, success
105: session 000000000000000003: user <iuli>: incoming packet CHANNEL_BIND processed, success
105: session 000000000000000003: user <iuli>: incoming packet CHANNEL_BIND processed, success
105: session 000000000000000004: user <iuli>: incoming packet CHANNEL_BIND processed, success
105: session 000000000000000002: TCP socket closed remotely 54.187.70.x:36715
105: session 000000000000000002: closed (2nd stage), user <iuli>, local 172.31.37.x:3478, remote 54.187.70.x:36715, reason: TCP connection closed by client (callback)
105: session 000000000000000002: delete: username=<iuli>
105: session 000000000000000003: refreshed, username=<iuli>, lifetime=600
105: session 000000000000000003: user <iuli>: incoming packet REFRESH processed, success
105: session 000000000000000003: user <iuli>: incoming packet CREATE_PERMISSION processed, success
105: session 000000000000000003: user <iuli>: incoming packet CHANNEL_BIND processed, success
105: session 000000000000000004: refreshed, username=<iuli>, lifetime=600
105: session 000000000000000004: user <iuli>: incoming packet REFRESH processed, success
105: session 000000000000000004: user <iuli>: incoming packet CREATE_PERMISSION processed, success
105: session 000000000000000004: user <iuli>: incoming packet CHANNEL_BIND processed, success
132: session 000000000000000004: TCP socket closed remotely 54.187.70.x:36717
132: session 000000000000000004: closed (2nd stage), user <iuli>, local 172.31.37.x:3478, remote 54.187.70.x:36717, reason: TCP connection closed by client (callback)
132: session 000000000000000004: delete: username=<iuli>
133: session 000000000000000003: TCP socket closed remotely 54.187.70.x:36716
133: session 000000000000000003: closed (2nd stage), user <iuli>, local 172.31.37.x:3478, remote 54.187.70.x:36716, reason: TCP connection closed by client (callback)
133: session 000000000000000003: delete: username=<iuli>
.....................................................................................



iuli bac

unread,
May 20, 2014, 6:08:41 AM5/20/14
to turn-server-project...@googlegroups.com
Thanks for the tip! Right. 
I checked the settings in: turnserver, WebRTC server, browsers; 
Somewhere  iuli user is sent to turnserver. Even when I completely offset this username. Since posting the above that the server is doing its job correctly. Not enough appropriate information to him. So now with these settings work! 
Thanks a lot.
271: session 000000000000000007: user <>: incoming packet BINDING processed, success
271: session 000000000000000007: user <>: incoming packet BINDING processed, success
281: session 000000000000000001: usage: username=<cucu>, rp=946, rb=216186, sp=1102, sb=420836
281: session 000000000000000007: user <>: incoming packet BINDING processed, success
282: session 000000000000000007: user <>: incoming packet BINDING processed, success
292: session 000000000000000007: user <>: incoming packet BINDING processed, success
292: session 000000000000000007: user <>: incoming packet BINDING processed, success
292: session 000000000000000001: usage: username=<cucu>, rp=933, rb=240633, sp=1115, sb=449792
302: session 000000000000000007: user <>: incoming packet BINDING processed, success
302: session 000000000000000007: user <>: incoming packet BINDING processed, success
302: session 000000000000000007: user <>: incoming packet BINDING processed, success
304: session 000000000000000001: usage: username=<cucu>, rp=1006, rb=195483, sp=1042, sb=307956
312: session 000000000000000007: user <>: incoming packet BINDING processed, success
312: session 000000000000000007: user <>: incoming packet BINDING processed, success
313: session 000000000000000007: user <>: incoming packet BINDING processed, success
316: session 000000000000000001: usage: username=<cucu>, rp=1025, rb=165952, sp=1023, sb=193484
323: session 000000000000000007: user <>: incoming packet BINDING processed, success
323: session 000000000000000007: user <>: incoming packet BINDING processed, success
329: session 000000000000000001: user <cucu>: incoming packet CHANNEL_BIND processed, success
329: session 000000000000000001: usage: username=<cucu>, rp=995, rb=163830, sp=1053, sb=242184
329: session 000000000000000001: user <cucu>: incoming packet CHANNEL_BIND processed, success
331: session 000000000000000007: closed (2nd stage), user <>, local 172.31.37.175:3478, remote 213.233.92.66:6484, reason: allocation watchdog determined stale session state
{
      'url': 'turn:54.187.87.x:3478?transport=tcp',
      'username': 'cucu',
      'credential': 'cucupassword'
    }

the user is in turnuserdb.conf database and turnserver.conf is in default state, and pass on run from command line settings.
And please tell me why is necessary realm? Do not understand yet.
thank you!

Message has been deleted

Marcus Hellner

unread,
May 20, 2014, 5:29:27 PM5/20/14
to turn-server-project...@googlegroups.com
I have the same issue. So the connection looks good but i get always a black remote screen.
Can you explain what you have done to solve your problem.

Greets

Marcus

iuli bac

unread,
May 21, 2014, 12:58:45 AM5/21/14
to turn-server-project...@googlegroups.com

Try local first in intranet. Should work ok. 
Then install turnserver. Turnserver check with turnu_utils. When it works ok move on. 
After that, put the settings in WebRTC solution. If you do not want to get complicate with the turnserver, can use xirsys. I was notified, they  already have their servers easyrtc integration for ice. 
Just make your account and follow their documentation. 
Regards

Message has been deleted

Marcus Hellner

unread,
May 21, 2014, 2:49:48 AM5/21/14
to turn-server-project...@googlegroups.com
Hey,

The following I have tested:

Local intranet is working fine.
Turnserver on Ubuntu 12.04 lts installed.
Checking with turn-utils --> there I get 100% of packet loss. Is this normal?

I get the same output from turn server like you with the packet loss.

Regards

Marcus

Oleg Moskalenko

unread,
May 21, 2014, 3:38:49 AM5/21/14
to turn-server-project...@googlegroups.com
You will get the 100% packet loss if you are using turnutils_uclient without option -y and if you are not using the turnutils_peer program that emulates the TURN "peer".

You have to use either of two tions:

1) turnutils_uclient with -y
2) turnutils_uclient AND turnutils_peer

See the examples in the examples/scripts directory.

Marcus Hellner

unread,
May 21, 2014, 4:09:52 AM5/21/14
to turn-server-project...@googlegroups.com
I have tested it now with the -y option. Thats the output:

dadmin@tkturn:/usr/share/rfc5766-turn-server/examples/scripts/basic$ sudo turnutils_uclient -y -v -t -n 1000 -m 2 -e 87.234.239.x -g -u dadmin -w password 87.234.239.x
0: IPv4. Connected from: 192.168.7.20:48823
0: IPv4. Connected to: 87.234.239.x:3478

I have testet it with the example/scripts tests and there it is working so could it be that the firewall is blocking someting?

First i want to thank all of the participants for the help.

Regards

Marcus



--
You received this message because you are subscribed to a topic in the Google Groups "TURN Server (Open-Source project)" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/turn-server-project-rfc5766-turn-server/PPhAMU1hACk/unsubscribe.
To unsubscribe from this group and all its topics, 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.

iuli bac

unread,
May 21, 2014, 4:17:21 AM5/21/14
to turn-server-project...@googlegroups.com
iptables -L -v   what show?
netstat -nao what show?
lsof -i what show?
on turnserver with -v option what show?
 

Marcus Hellner

unread,
May 21, 2014, 4:21:56 AM5/21/14
to turn-server-project...@googlegroups.com
Attached you will find my config files
my_conf.rar

Marcus Hellner

unread,
May 21, 2014, 4:37:52 AM5/21/14
to turn-server-project...@googlegroups.com
dadmin@tkturn:/var/tmp$ sudo iptables -L -v
[sudo] password for dadmin:
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination




dadmin@tkturn:/var/tmp$ sudo netstat -nao
Aktive Internetverbindungen (Server und stehende Verbindungen)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       Timer
tcp        0      0 127.0.0.1:3306          0.0.0.0:*               LISTEN      aus (0.00/0/0)
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      aus (0.00/0/0)
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      aus (0.00/0/0)
tcp        0    336 192.168.7.20:22         10.1.7.200:53611        VERBUNDEN   ein (0,20/0/0)
tcp        0      0 192.168.7.20:22         10.1.7.200:51927        VERBUNDEN   keepalive (6889,15/0/0)
tcp        0      0 192.168.7.20:22         10.1.7.200:52895        VERBUNDEN   keepalive (2924,22/0/0)
tcp        0      0 192.168.7.20:22         10.1.7.200:53242        VERBUNDEN   keepalive (4038,33/0/0)
tcp6       0      0 :::22                   :::*                    LISTEN      aus (0.00/0/0)
Aktive Sockets in der UNIX-Domäne (Server und stehende Verbindungen)
Proto RefCnt Flags       Type       State         I-Node   Pfad
unix  2      [ ACC ]     STREAM     HÖRT         9232     /var/run/acpid.socket
unix  2      [ ACC ]     STREAM     HÖRT         8466     /var/run/dbus/system_bus_socket
unix  2      [ ACC ]     STREAM     HÖRT         6464     @/com/ubuntu/upstart
unix  2      [ ACC ]     STREAM     HÖRT         9344     /var/run/mysqld/mysqld.sock
unix  2      [ ACC ]     SEQPAKET   HÖRT         6567     /run/udev/control
unix  8      [ ]         DGRAM                    7099     /dev/log
unix  3      [ ]         STREAM     VERBUNDEN     14095
unix  3      [ ]         STREAM     VERBUNDEN     8481
unix  3      [ ]         STREAM     VERBUNDEN     7885     @/com/ubuntu/upstart
unix  3      [ ]         STREAM     VERBUNDEN     6978
unix  3      [ ]         STREAM     VERBUNDEN     16436
unix  2      [ ]         DGRAM                    9231
unix  3      [ ]         STREAM     VERBUNDEN     16435
unix  3      [ ]         STREAM     VERBUNDEN     17100
unix  2      [ ]         DGRAM                    18189
unix  3      [ ]         STREAM     VERBUNDEN     8587     /var/run/dbus/system_bus_socket
unix  3      [ ]         STREAM     VERBUNDEN     6550
unix  3      [ ]         STREAM     VERBUNDEN     6979     @/com/ubuntu/upstart
unix  3      [ ]         STREAM     VERBUNDEN     8480
unix  3      [ ]         STREAM     VERBUNDEN     8490
unix  3      [ ]         STREAM     VERBUNDEN     14094
unix  3      [ ]         STREAM     VERBUNDEN     8491     /var/run/dbus/system_bus_socket
unix  2      [ ]         DGRAM                    16078
unix  3      [ ]         DGRAM                    7940
unix  3      [ ]         STREAM     VERBUNDEN     17099
unix  3      [ ]         STREAM     VERBUNDEN     16657
unix  3      [ ]         STREAM     VERBUNDEN     9293
unix  2      [ ]         DGRAM                    17964
unix  2      [ ]         DGRAM                    18192
unix  2      [ ]         DGRAM                    15623
unix  3      [ ]         DGRAM                    7939
unix  2      [ ]         DGRAM                    16579
unix  3      [ ]         STREAM     VERBUNDEN     16656




dadmin@tkturn:/var/tmp$ sudo lsof -i
COMMAND  PID     USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
sshd     839     root    3u  IPv4   7123      0t0  TCP *:ssh (LISTEN)
sshd     839     root    4u  IPv6   7125      0t0  TCP *:ssh (LISTEN)
mysqld  1067    mysql   10u  IPv4   9343      0t0  TCP localhost:mysql (LISTEN)
apache2 1099     root    3u  IPv4   9302      0t0  TCP *:http (LISTEN)
apache2 1157 www-data    3u  IPv4   9302      0t0  TCP *:http (LISTEN)
apache2 1158 www-data    3u  IPv4   9302      0t0  TCP *:http (LISTEN)
apache2 1159 www-data    3u  IPv4   9302      0t0  TCP *:http (LISTEN)
apache2 1160 www-data    3u  IPv4   9302      0t0  TCP *:http (LISTEN)
apache2 1161 www-data    3u  IPv4   9302      0t0  TCP *:http (LISTEN)
sshd    3539     root    3u  IPv4  13975      0t0  TCP 192.168.7.20:ssh->10.1.7.200:51927 (ESTABLISHED)
sshd    3697   dadmin    3u  IPv4  13975      0t0  TCP 192.168.7.20:ssh->10.1.7.200:51927 (ESTABLISHED)
sshd    4003     root    3u  IPv4  14254      0t0  TCP 192.168.7.20:ssh->10.1.7.200:52895 (ESTABLISHED)
sshd    4131   dadmin    3u  IPv4  14254      0t0  TCP 192.168.7.20:ssh->10.1.7.200:52895 (ESTABLISHED)
sshd    4305     root    3u  IPv4  16556      0t0  TCP 192.168.7.20:ssh->10.1.7.200:53242 (ESTABLISHED)
sshd    4456   dadmin    3u  IPv4  16556      0t0  TCP 192.168.7.20:ssh->10.1.7.200:53242 (ESTABLISHED)
sshd    4736     root    3u  IPv4  16971      0t0  TCP 192.168.7.20:ssh->10.1.7.200:53611 (ESTABLISHED)
sshd    4864   dadmin    3u  IPv4  16971      0t0  TCP 192.168.7.20:ssh->10.1.7.200:53611 (ESTABLISHED)



1. Command to start Turnserver:
sudo turnserver -a -b turnuser.conf -X 87.234.239.x -E 192.168.7.20 -L 192.168.7.20 -f -r 192.168.7.20 -v

2. Test Turnserver:
sudo turnutils_uclient -v -t -n 1000 -m 2 -e 87.234.239.x -g -u dadmin -w dadmin01 87.234.239.x


to 1.:

dadmin@tkturn:/$ sudo turnserver -a -b turnuser.conf -X 87.234.239.x -E 192.168.7.20 -L 192.1.7.20 -f -r 192.168.7.20 -v
0: log file opened: /var/log/turn_5128_2014-05-21.log
0:
RFC 3489/5389/5766/5780/6062/6156 STUN/TURN Server
Version Citrix-3.2.3.8 'Marshal West'
0:
Max number of open files/sockets allowed for this process: 4096
0:
Due to the open files/sockets limitation,
max supported number of TURN Sessions possible is: 2000 (approximately)
0:

==== Show him the instruments, Practical Frost: ====

0: TLS supported
0: DTLS supported
0: Redis supported
0: PostgreSQL supported
0: MySQL supported
0: OpenSSL compile-time version 0x1000103f: fresh enough
0: Default Net Engine version: 2 (UDP thread per network endpoint)

=====================================================

0: Config file found: //etc/turnserver.conf
0: Listener address to use: 192.168.7.20
0: Relay address to use: 192.168.7.20
0: log file opened: /var/tmp/turn_2014-05-21.log
0: ERROR: -X : Wrong address format: 87.234.239.x
0: Config file found: //etc/turnserver.conf
0: WARNING: Cannot find userdb file: turnuser.conf: going without flat file user database.
0:
CONFIGURATION ALERT: you did not specify any user account, (-u option)
        but you did specified a long-term credentials mechanism option (-a option).
        The TURN Server will be inaccessible.
                Check your configuration.
0: WARNING: cannot find certificate file: turn_server_cert.pem (1)
0: WARNING: cannot start TLS and DTLS listeners because certificate file is not set properly
0: WARNING: cannot find private key file: turn_server_pkey.pem (1)
0: WARNING: cannot start TLS and DTLS listeners because private key file is not set properly
0: pid file created: /var/run/turnserver.pid
0: IO method (main listener thread): epoll (with changelist)
0: WARNING: I cannot support STUN CHANGE_REQUEST functionality because only one IP address is provided
0: Wait for relay ports initialization...
0:   relay 192.168.7.20 initialization...
0:   relay 192.168.7.20 initialization done
0: Relay ports initialization done
0: IO method (general relay thread): epoll (with changelist)
0: turn server id=0 created
0: IO method (udp listener/relay thread): epoll (with changelist)
0: IO method (general relay thread): epoll (with changelist)
0: turn server id=1 created
0: turn server id=128 created
0: IPv4. UDP listener opened on: 192.168.7.20:3478
0: IPv4. TCP listener opened on : 192.168.7.20:3478
0: IO method (cli thread): epoll (with changelist)
0: IPv4. CLI listener opened on : 127.0.0.1:5766
0: IO method (auth thread): epoll (with changelist)
16: IPv4. tcp or tls connected to: 87.234.239.x:48829
16: session 001000000000000001: user <>: incoming packet message processed, error 401: Unauthorised
16: ERROR: check_stun_auth: Cannot find credentials of user <dadmin>
16: session 001000000000000001: user <dadmin>: incoming packet message processed, error 401: Unauthorised
16: ERROR: check_stun_auth: Cannot find credentials of user <dadmin>
16: session 001000000000000001: user <dadmin>: incoming packet message processed, error 401: Unauthorised
16: ERROR: check_stun_auth: Cannot find credentials of user <dadmin>
16: session 001000000000000001: user <dadmin>: incoming packet message processed, error 401: Unauthorised
16: ERROR: check_stun_auth: Cannot find credentials of user <dadmin>
16: session 001000000000000001: user <dadmin>: incoming packet message processed, error 401: Unauthorised
16: ERROR: check_stun_auth: Cannot find credentials of user <dadmin>
16: session 001000000000000001: user <dadmin>: incoming packet message processed, error 401: Unauthorised
16: ERROR: check_stun_auth: Cannot find credentials of user <dadmin>
16: session 001000000000000001: user <dadmin>: incoming packet message processed, error 401: Unauthorised
16: ERROR: check_stun_auth: Cannot find credentials of user <dadmin>
16: session 001000000000000001: user <dadmin>: incoming packet message processed, error 401: Unauthorised
16: ERROR: check_stun_auth: Cannot find credentials of user <dadmin>
16: session 001000000000000001: user <dadmin>: incoming packet message processed, error 401: Unauthorised
16: ERROR: check_stun_auth: Cannot find credentials of user <dadmin>
16: session 001000000000000001: user <dadmin>: incoming packet message processed, error 401: Unauthorised
16: ERROR: check_stun_auth: Cannot find credentials of user <dadmin>
16: session 001000000000000001: user <dadmin>: incoming packet message processed, error 401: Unauthorised
16: ERROR: check_stun_auth: Cannot find credentials of user <dadmin>
16: session 001000000000000001: user <dadmin>: incoming packet message processed, error 401: Unauthorised
16: ERROR: check_stun_auth: Cannot find credentials of user <dadmin>
16: session 001000000000000001: user <dadmin>: incoming packet message processed, error 401: Unauthorised
16: ERROR: check_stun_auth: Cannot find credentials of user <dadmin>
16: session 001000000000000001: user <dadmin>: incoming packet message processed, error 401: Unauthorised
16: ERROR: check_stun_auth: Cannot find credentials of user <dadmin>
16: session 001000000000000001: user <dadmin>: incoming packet message processed, error 401: Unauthorised
16: ERROR: check_stun_auth: Cannot find credentials of user <dadmin>
16: session 001000000000000001: user <dadmin>: incoming packet message processed, error 401: Unauthorised
16: ERROR: check_stun_auth: Cannot find credentials of user <dadmin>
16: session 001000000000000001: user <dadmin>: incoming packet message processed, error 401: Unauthorised
16: ERROR: check_stun_auth: Cannot find credentials of user <dadmin>
16: session 001000000000000001: user <dadmin>: incoming packet message processed, error 401: Unauthorised
16: ERROR: check_stun_auth: Cannot find credentials of user <dadmin>
16: session 001000000000000001: user <dadmin>: incoming packet message processed, error 401: Unauthorised
16: ERROR: check_stun_auth: Cannot find credentials of user <dadmin>
16: session 001000000000000001: user <dadmin>: incoming packet message processed, error 401: Unauthorised
16: ERROR: check_stun_auth: Cannot find credentials of user <dadmin>
16: session 001000000000000001: user <dadmin>: incoming packet message processed, error 401: Unauthorised
16: ERROR: check_stun_auth: Cannot find credentials of user <dadmin>
16: session 001000000000000001: user <dadmin>: incoming packet message processed, error 401: Unauthorised
16: ERROR: check_stun_auth: Cannot find credentials of user <dadmin>
16: session 001000000000000001: user <dadmin>: incoming packet message processed, error 401: Unauthorised
16: ERROR: check_stun_auth: Cannot find credentials of user <dadmin>
16: session 001000000000000001: user <dadmin>: incoming packet message processed, error 401: Unauthorised
16: ERROR: check_stun_auth: Cannot find credentials of user <dadmin>
16: session 001000000000000001: user <dadmin>: incoming packet message processed, error 401: Unauthorised
16: ERROR: check_stun_auth: Cannot find credentials of user <dadmin>
16: session 001000000000000001: user <dadmin>: incoming packet message processed, error 401: Unauthorised
16: ERROR: check_stun_auth: Cannot find credentials of user <dadmin>
16: session 001000000000000001: user <dadmin>: incoming packet message processed, error 401: Unauthorised
16: ERROR: check_stun_auth: Cannot find credentials of user <dadmin>
16: session 001000000000000001: user <dadmin>: incoming packet message processed, error 401: Unauthorised
16: ERROR: check_stun_auth: Cannot find credentials of user <dadmin>
16: session 001000000000000001: user <dadmin>: incoming packet message processed, error 401: Unauthorised
16: ERROR: check_stun_auth: Cannot find credentials of user <dadmin>
16: session 001000000000000001: user <dadmin>: incoming packet message processed, error 401: Unauthorised
16: ERROR: check_stun_auth: Cannot find credentials of user <dadmin>
16: session 001000000000000001: user <dadmin>: incoming packet message processed, error 401: Unauthorised
16: ERROR: check_stun_auth: Cannot find credentials of user <dadmin>
16: session 001000000000000001: user <dadmin>: incoming packet message processed, error 401: Unauthorised
16: session 001000000000000001: TCP socket closed remotely 87.234.239.x:48829
16: session 001000000000000001: closed (2nd stage), user <dadmin>, local 192.168.7.20:3478, remote 87.234.239.x:48829, reason: TCP connection closed by client (callback)





dadmin@tkturn:/usr/share/rfc5766-turn-server/examples/scripts/basic$ sudo turnutils_uclient -v -t -n 1000 -m 2 -e 87.234.239.x -g -u dadmin -w dadmin01 87.234.239.x
0: IPv4. Connected from: 192.168.7.20:48830




Its the first time that an authentication error is fired.

Hope it helps

Regards

Marcus




--

Marcus Hellner

unread,
May 21, 2014, 4:45:27 AM5/21/14
to turn-server-project...@googlegroups.com
2nd Test:

TurnServer:

dadmin@tkturn:/$ sudo turnserver -a -b turnuserdb.conf -X 87.234.239.205 -E 192.168.7.20 -L 192.168.7.20 -f -r 192.168.7.20 -v
0: log file opened: /var/log/turn_5198_2014-05-21.log
0:
RFC 3489/5389/5766/5780/6062/6156 STUN/TURN Server
Version Citrix-3.2.3.8 'Marshal West'
0:
Max number of open files/sockets allowed for this process: 4096
0:
Due to the open files/sockets limitation,
max supported number of TURN Sessions possible is: 2000 (approximately)
0:

==== Show him the instruments, Practical Frost: ====

0: TLS supported
0: DTLS supported
0: Redis supported
0: PostgreSQL supported
0: MySQL supported
0: OpenSSL compile-time version 0x1000103f: fresh enough
0: Default Net Engine version: 2 (UDP thread per network endpoint)

=====================================================

0: Config file found: //etc/turnserver.conf
0: Listener address to use: 192.168.7.20
0: Relay address to use: 192.168.7.20
0: log file opened: /var/tmp/turn_2014-05-21.log
0: Config file found: //etc/turnserver.conf
0: Config file found: //etc/turnuserdb.conf
0: WARNING: cannot find certificate file: turn_server_cert.pem (1)
0: WARNING: cannot start TLS and DTLS listeners because certificate file is not set properly
0: WARNING: cannot find private key file: turn_server_pkey.pem (1)
0: WARNING: cannot start TLS and DTLS listeners because private key file is not set properly
0: pid file created: /var/run/turnserver.pid
0: IO method (main listener thread): epoll (with changelist)
0: WARNING: I cannot support STUN CHANGE_REQUEST functionality because only one IP address is provided
0: Wait for relay ports initialization...
0:   relay 192.168.7.20 initialization...
0:   relay 192.168.7.20 initialization done
0: Relay ports initialization done
0: IO method (general relay thread): epoll (with changelist)
0: turn server id=0 created
0: IO method (udp listener/relay thread): epoll (with changelist)
0: turn server id=128 created
0: IO method (general relay thread): epoll (with changelist)
0: turn server id=1 created
0: IPv4. UDP listener opened on: 192.168.7.20:3478
0: IPv4. TCP listener opened on : 192.168.7.20:3478
0: IO method (cli thread): epoll (with changelist)
0: IO method (auth thread): epoll (with changelist)
0: IPv4. CLI listener opened on : 127.0.0.1:5766
6: IPv4. tcp or tls connected to: 87.234.239.205:48842
6: session 001000000000000001: user <>: incoming packet message processed, error 401: Unauthorised
6: IPv4. Local relay addr: 192.168.7.20:55858
6: IPv4. Local reserved relay addr: 192.168.7.20:55859
6: session 001000000000000001: new, username=<dadmin>, lifetime=800
6: session 001000000000000001: user <dadmin>: incoming packet ALLOCATE processed, success
6: session 001000000000000001: refreshed, username=<dadmin>, lifetime=600
6: session 001000000000000001: user <dadmin>: incoming packet REFRESH processed, success
6: IPv4. tcp or tls connected to: 87.234.239.205:48843
6: IPv4. tcp or tls connected to: 87.234.239.205:48844
6: IPv4. tcp or tls connected to: 87.234.239.205:48845
6: IPv4. tcp or tls connected to: 87.234.239.205:48846
6: session 000000000000000001: user <>: incoming packet message processed, error 401: Unauthorised
6: IPv4. Local relay addr (RTCP): 192.168.7.20:55859
6: session 000000000000000001: new, username=<dadmin>, lifetime=800
6: session 000000000000000001: user <dadmin>: incoming packet ALLOCATE processed, success
6: session 000000000000000001: refreshed, username=<dadmin>, lifetime=600
6: session 000000000000000001: user <dadmin>: incoming packet REFRESH processed, success
6: session 000000000000000002: user <>: incoming packet message processed, error 401: Unauthorised
6: IPv4. Local relay addr: 192.168.7.20:65354
6: IPv4. Local reserved relay addr: 192.168.7.20:65355
6: session 000000000000000002: new, username=<dadmin>, lifetime=800
6: session 000000000000000002: user <dadmin>: incoming packet ALLOCATE processed, success
6: session 000000000000000002: refreshed, username=<dadmin>, lifetime=600
6: session 000000000000000002: user <dadmin>: incoming packet REFRESH processed, success
6: session 001000000000000002: user <>: incoming packet message processed, error 401: Unauthorised
6: IPv4. Local relay addr (RTCP): 192.168.7.20:65355
6: session 001000000000000002: new, username=<dadmin>, lifetime=800
6: session 001000000000000002: user <dadmin>: incoming packet ALLOCATE processed, success
6: session 001000000000000002: refreshed, username=<dadmin>, lifetime=600
6: session 001000000000000002: user <dadmin>: incoming packet REFRESH processed, success
6: session 001000000000000003: user <>: incoming packet message processed, error 401: Unauthorised
6: IPv4. Local relay addr: 192.168.7.20:61660
6: IPv4. Local reserved relay addr: 192.168.7.20:61661
6: session 001000000000000003: new, username=<dadmin>, lifetime=800
6: session 001000000000000003: user <dadmin>: incoming packet ALLOCATE processed, success
6: session 001000000000000003: refreshed, username=<dadmin>, lifetime=600
6: session 001000000000000003: user <dadmin>: incoming packet REFRESH processed, success
6: session 000000000000000001: user <dadmin>: incoming packet CHANNEL_BIND processed, success
6: session 000000000000000002: user <dadmin>: incoming packet CHANNEL_BIND processed, success
6: session 001000000000000002: user <dadmin>: incoming packet CHANNEL_BIND processed, success
6: session 001000000000000003: user <dadmin>: incoming packet CHANNEL_BIND processed, success
6: session 001000000000000001: TCP socket closed remotely 87.234.239.205:48842
6: session 001000000000000001: closed (2nd stage), user <dadmin>, local 192.168.7.20:3478, remote 87.234.239.205:48842, reason: TCP connection closed by client (callback)
6: session 001000000000000001: delete: username=<dadmin>
6: session 000000000000000001: refreshed, username=<dadmin>, lifetime=600
6: session 000000000000000001: user <dadmin>: incoming packet REFRESH processed, success
6: session 000000000000000002: refreshed, username=<dadmin>, lifetime=600
6: session 000000000000000002: user <dadmin>: incoming packet REFRESH processed, success
6: session 001000000000000002: refreshed, username=<dadmin>, lifetime=600
6: session 001000000000000002: user <dadmin>: incoming packet REFRESH processed, success
6: session 001000000000000003: refreshed, username=<dadmin>, lifetime=600
6: session 001000000000000003: user <dadmin>: incoming packet REFRESH processed, success
6: session 000000000000000001: user <dadmin>: incoming packet CREATE_PERMISSION processed, success
6: session 000000000000000001: user <dadmin>: incoming packet CHANNEL_BIND processed, success
6: session 000000000000000002: user <dadmin>: incoming packet CREATE_PERMISSION processed, success
6: session 001000000000000002: user <dadmin>: incoming packet CREATE_PERMISSION processed, success
6: session 000000000000000002: user <dadmin>: incoming packet CHANNEL_BIND processed, success
6: session 001000000000000002: user <dadmin>: incoming packet CHANNEL_BIND processed, success
6: session 001000000000000003: user <dadmin>: incoming packet CREATE_PERMISSION processed, success
6: session 001000000000000003: user <dadmin>: incoming packet CHANNEL_BIND processed, success
32: session 001000000000000002: refreshed, username=<dadmin>, lifetime=0
32: session 001000000000000002: user <dadmin>: incoming packet REFRESH processed, success
32: session 001000000000000002: TCP socket closed remotely 87.234.239.205:48845
32: session 001000000000000002: closed (2nd stage), user <dadmin>, local 192.168.7.20:3478, remote 87.234.239.205:48845, reason: TCP connection closed by client (callback)
33: session 001000000000000003: refreshed, username=<dadmin>, lifetime=0
33: session 001000000000000003: user <dadmin>: incoming packet REFRESH processed, success
33: session 001000000000000003: TCP socket closed remotely 87.234.239.205:48846
33: session 001000000000000003: closed (2nd stage), user <dadmin>, local 192.168.7.20:3478, remote 87.234.239.205:48846, reason: TCP connection closed by client (callback)
35: session 000000000000000001: refreshed, username=<dadmin>, lifetime=0
35: session 000000000000000001: user <dadmin>: incoming packet REFRESH processed, success
35: session 000000000000000001: TCP socket closed remotely 87.234.239.205:48843
35: session 000000000000000001: closed (2nd stage), user <dadmin>, local 192.168.7.20:3478, remote 87.234.239.205:48843, reason: TCP connection closed by client (callback)
36: session 000000000000000002: refreshed, username=<dadmin>, lifetime=600
36: session 000000000000000002: user <dadmin>: incoming packet REFRESH processed, success
36: session 000000000000000002: user <dadmin>: incoming packet CREATE_PERMISSION processed, success
36: session 000000000000000002: user <dadmin>: incoming packet CHANNEL_BIND processed, success
36: session 000000000000000002: refreshed, username=<dadmin>, lifetime=0
36: session 000000000000000002: user <dadmin>: incoming packet REFRESH processed, success
36: session 000000000000000002: TCP socket closed remotely 87.234.239.205:48844
36: session 000000000000000002: closed (2nd stage), user <dadmin>, local 192.168.7.20:3478, remote 87.234.239.205:48844, reason: TCP connection closed by client (callback)


Turn_utils:
dadmin@tkturn:/$ sudo turnutils_uclient -y -v -t -n 1000 -m 2 -e 87.234.239.205 -g -u dadmin -w dadmin01 87.234.239.205
0: IPv4. Connected from: 192.168.7.20:48842
0: IPv4. Connected to: 87.234.239.205:3478
0: allocate sent
0: allocate response received:
0: allocate sent
0: allocate response received:
0: success
0: IPv4. Received relay addr: 87.234.239.205:55858
0: clnet_allocate: rtv=1400254905813696330
0: refresh sent
0: refresh response received:
0: success
0: IPv4. Connected from: 192.168.7.20:48843
0: IPv4. Connected to: 87.234.239.205:3478
0: IPv4. Connected from: 192.168.7.20:48844
0: IPv4. Connected to: 87.234.239.205:3478
0: IPv4. Connected from: 192.168.7.20:48845
0: IPv4. Connected to: 87.234.239.205:3478
0: IPv4. Connected from: 192.168.7.20:48846
0: IPv4. Connected to: 87.234.239.205:3478
0: allocate sent
0: allocate response received:
0: allocate sent
0: allocate response received:
0: success
0: IPv4. Received relay addr: 87.234.239.205:55859
0: clnet_allocate: rtv=0
0: refresh sent
0: refresh response received:
0: success
0: allocate sent
0: allocate response received:
0: allocate sent
0: allocate response received:
0: success
0: IPv4. Received relay addr: 87.234.239.205:65354
0: clnet_allocate: rtv=4625820154503491804
0: refresh sent
0: refresh response received:
0: success
0: allocate sent
0: allocate response received:
0: allocate sent
0: allocate response received:
0: success
0: IPv4. Received relay addr: 87.234.239.205:65355
0: clnet_allocate: rtv=0
0: refresh sent
0: refresh response received:
0: success
0: allocate sent
0: allocate response received:
0: allocate sent
0: allocate response received:
0: success
0: IPv4. Received relay addr: 87.234.239.205:61660
0: clnet_allocate: rtv=9546712361902403413
0: refresh sent
0: refresh response received:
0: success
0: channel bind sent
0: cb response received:
0: success: 0x7293
0: channel bind sent
0: cb response received:
0: success: 0x6b41
0: channel bind sent
0: cb response received:
0: success: 0x5899
0: channel bind sent
0: cb response received:
0: success: 0x70d9
0: Total connect time is 0
1: start_mclient: msz=4, tot_send_msgs=0, tot_recv_msgs=0, tot_send_bytes ~ 0, tot_recv_bytes ~ 0
2: start_mclient: msz=4, tot_send_msgs=0, tot_recv_msgs=0, tot_send_bytes ~ 0, tot_recv_bytes ~ 0
3: start_mclient: msz=4, tot_send_msgs=66, tot_recv_msgs=0, tot_send_bytes ~ 6600, tot_recv_bytes ~ 0
4: start_mclient: msz=4, tot_send_msgs=167, tot_recv_msgs=0, tot_send_bytes ~ 16700, tot_recv_bytes ~ 0
5: start_mclient: msz=4, tot_send_msgs=270, tot_recv_msgs=0, tot_send_bytes ~ 27000, tot_recv_bytes ~ 0
6: start_mclient: msz=4, tot_send_msgs=432, tot_recv_msgs=0, tot_send_bytes ~ 43200, tot_recv_bytes ~ 0
7: start_mclient: msz=4, tot_send_msgs=632, tot_recv_msgs=0, tot_send_bytes ~ 63200, tot_recv_bytes ~ 0
8: start_mclient: msz=4, tot_send_msgs=832, tot_recv_msgs=0, tot_send_bytes ~ 83200, tot_recv_bytes ~ 0
9: start_mclient: msz=4, tot_send_msgs=1033, tot_recv_msgs=0, tot_send_bytes ~ 103300, tot_recv_bytes ~ 0
10: start_mclient: msz=4, tot_send_msgs=1233, tot_recv_msgs=0, tot_send_bytes ~ 123300, tot_recv_bytes ~ 0
11: start_mclient: msz=4, tot_send_msgs=1433, tot_recv_msgs=0, tot_send_bytes ~ 143300, tot_recv_bytes ~ 0
12: start_mclient: msz=4, tot_send_msgs=1633, tot_recv_msgs=0, tot_send_bytes ~ 163300, tot_recv_bytes ~ 0
13: start_mclient: msz=4, tot_send_msgs=1833, tot_recv_msgs=0, tot_send_bytes ~ 183300, tot_recv_bytes ~ 0
14: start_mclient: msz=4, tot_send_msgs=2034, tot_recv_msgs=0, tot_send_bytes ~ 203400, tot_recv_bytes ~ 0
15: start_mclient: msz=4, tot_send_msgs=2234, tot_recv_msgs=0, tot_send_bytes ~ 223400, tot_recv_bytes ~ 0
16: start_mclient: msz=4, tot_send_msgs=2434, tot_recv_msgs=0, tot_send_bytes ~ 243400, tot_recv_bytes ~ 0
17: start_mclient: msz=4, tot_send_msgs=2634, tot_recv_msgs=0, tot_send_bytes ~ 263400, tot_recv_bytes ~ 0
18: start_mclient: msz=4, tot_send_msgs=2834, tot_recv_msgs=0, tot_send_bytes ~ 283400, tot_recv_bytes ~ 0
19: start_mclient: msz=4, tot_send_msgs=3034, tot_recv_msgs=0, tot_send_bytes ~ 303400, tot_recv_bytes ~ 0
20: start_mclient: msz=4, tot_send_msgs=3234, tot_recv_msgs=0, tot_send_bytes ~ 323400, tot_recv_bytes ~ 0
21: start_mclient: msz=4, tot_send_msgs=3435, tot_recv_msgs=0, tot_send_bytes ~ 343500, tot_recv_bytes ~ 0
22: start_mclient: msz=4, tot_send_msgs=3633, tot_recv_msgs=0, tot_send_bytes ~ 363300, tot_recv_bytes ~ 0
23: start_mclient: msz=4, tot_send_msgs=3756, tot_recv_msgs=0, tot_send_bytes ~ 375600, tot_recv_bytes ~ 0
24: start_mclient: msz=4, tot_send_msgs=3857, tot_recv_msgs=0, tot_send_bytes ~ 385700, tot_recv_bytes ~ 0
25: start_mclient: msz=4, tot_send_msgs=3958, tot_recv_msgs=0, tot_send_bytes ~ 395800, tot_recv_bytes ~ 0
26: start_mclient: msz=4, tot_send_msgs=4000, tot_recv_msgs=0, tot_send_bytes ~ 400000, tot_recv_bytes ~ 0
27: start_mclient: msz=4, tot_send_msgs=4000, tot_recv_msgs=0, tot_send_bytes ~ 400000, tot_recv_bytes ~ 0
27: done, connection 0xb719c008 closed.
27: done, connection 0xb717b008 closed.
28: start_mclient: msz=2, tot_send_msgs=4000, tot_recv_msgs=0, tot_send_bytes ~ 400000, tot_recv_bytes ~ 0
29: start_mclient: msz=2, tot_send_msgs=4000, tot_recv_msgs=0, tot_send_bytes ~ 400000, tot_recv_bytes ~ 0
30: done, connection 0xb800f460 closed.
30: start_mclient: msz=1, tot_send_msgs=4000, tot_recv_msgs=0, tot_send_bytes ~ 400000, tot_recv_bytes ~ 0
30: done, connection 0xb71bd008 closed.
30: start_mclient: tot_send_msgs=4000, tot_recv_msgs=0
30: start_mclient: tot_send_bytes ~ 400000, tot_recv_bytes ~ 0
30: Total transmit time is 30
30: Total lost packets 4000 (100.000000%), total send dropped 0 (0.000000%)
30: Average round trip delay 0.000000 ms; min = 4294967295 ms, max = 0 ms
30: Average jitter -nan ms; min = 4294967295 ms, max = 0 ms


Oleg Moskalenko

unread,
May 21, 2014, 12:15:28 PM5/21/14
to turn-server-project...@googlegroups.com, marcus....@googlemail.com
As far as I can see, you are running your test client on the same system as your "NATed" TURN server. That may be a problem in your network topology. Try to figure out how the messages are flowing in your network and where is the barrier.

Oleg
<div
...

Marcus Hellner

unread,
May 22, 2014, 2:32:26 AM5/22/14
to turn-server-project...@googlegroups.com
Thank you...i will try that.
Thanks for the help

Cheers

Marcus

iuli bac

unread,
May 23, 2014, 1:00:13 AM5/23/14
to turn-server-project...@googlegroups.com
take attention to:

CONFIGURATION ALERT: you did not specify any user account, (-u option)
        but you did specified a long-term credentials mechanism option (-a option).
        The TURN Server will be inaccessible.
                Check your configuration.
Your iptables on that system looks ok, but need pre/post routing table to be shure that not something is happening there.
Is necessary to isolate the problem. Put turnsever accessible from public and try from another system with turn-utilities.
Reply all
Reply to author
Forward
0 new messages