TCP/UDP connection using turnutils_uclient to turnserver, shows invalid informations
2,187 views
Skip to first unread message
Sprogrammer
Dec 19, 2013, 5:38:35 AM12/19/13
to turn-server-project...@googlegroups.com
1) When TCP Client close the connection with Turn server then the PS command via telnet shows correctly
2) When UDP Client close the connection with Turn server then the PS command via telnet DO not shows correctly
For example:
Client test:
$ turnutils_uclient -v -t -n 1000 -m 2 -l 170 -e 82.x -g -u root -w root 82.x # OK - TCP WebRTC: http://apprtc/?r=id&ts=root@ip:port&transport=tcp&tp=root
$ turnutils_uclient -v -n 1000 -m 2 -l 170 -e 82.x -g -u root -w root 82.x # FAIL - UDP WebRTC: http://apprtc/?r=id&ts=root@ip:port&transport=udp&tp=root
Server test:
$ egrep -v '^(;|#|//|$)' /etc/turnserver/turnserver.conf
user=root:root
realm=teleportel.com
no-tls
no-dtls
no-stdout-log
syslog$ service turnserver restart
Stopping turnserver: [ OK ]
Starting turnserver: 0:
RFC 3489/5389/5766/5780/6062/6156 STUN/TURN Server
Version Citrix-3.1.2.3 'Arch Lector'
0:
==== Show them the instruments, Practical Frost: ====
0: TLS supported
0: DTLS supported
0: Redis supported
0: PostgreSQL supported
0: MySQL supported
0: OpenSSL version: fresh enough
0: TURN Network Engine version: 2.5
=====================================================
[ OK ]# telnet localhost 5766
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
TURN Server
rfc5766-turn-server
Citrix-3.1.2.3 'Arch Lector'
Type '?' for help
> ps
1) id=130000000000000001, user <root>:
expiring in 306 secs
client protocol UDP, relay protocol UDP
client addr 82.x.x.x:42225, server addr 192.168.1.12:3478
relay addr 192.168.1.12:55818
fingerprints enforced: ON
mobile: OFF
SHA256 only: OFF
usage: rp=3, rb=292, sp=2, sb=248
2) id=130000000000000002, user <root>:
expiring in 306 secs
client protocol UDP, relay protocol UDP
client addr 82.x.x.x:40469, server addr 192.168.1.12:3478
relay addr 192.168.1.12:55819
fingerprints enforced: ON
mobile: OFF
SHA256 only: OFF
usage: rp=10, rb=1120, sp=9, sb=840
peers:
82.x.x.2:3481
82.x.x.2:3480
3) id=130000000000000003, user <root>:
expiring in 306 secs
client protocol UDP, relay protocol UDP
client addr 82.x.x.x:37907, server addr 192.168.1.12:3478
relay addr 192.168.1.12:58806
fingerprints enforced: ON
mobile: OFF
SHA256 only: OFF
usage: rp=7, rb=752, sp=6, sb=600
peers:
82.x.x.2:3481
Total sessions: 3
> NOOOOOOOOOOOOOOOOOOOOOOOOOO - client type again ps
> psit shows again that Total sessions: 3
Even, the turnutils_uclient is killed with -9 and sockets are closed too. With TCP connection it shows correctly.
Thank you
Best regards
/Sham
Oleg Moskalenko
Dec 19, 2013, 5:47:45 AM12/19/13
to Sprogrammer, turn-server-project...@googlegroups.com
That's a correct behavior. Because in udp turn the server does not know whether the client disconnected. The client session will expire with time.
Sent from my iPhone
Sent from my iPhone
--
You received this message because you are subscribed to the Google Groups "TURN Server project rfc5766-turn-server" 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/groups/opt_out.
Shamun Toha Md
Dec 19, 2013, 5:57:10 AM12/19/13
to Oleg Moskalenko, turn-server-project...@googlegroups.com
Thank you!!!
Can it be a security whole? For example as following scenario (if some advanced user asks me for the following are we still safe?):
> PC1: (BANK/Government users for example):
8:05.00 AM:
turnutils_uclient -v -n 1000 -m 2 -l 170 -e 82.x -g -u root -w root 82.x # FAIL - UDP WebRTC: http://apprtc/?r=id&ts=root@ip:port&transport=udp&tp=root
8:10:00 AM:
killed session
spy-ware/exploit: Key logger hacked those information to PC2
> PC2: of a DoS attackers similar to SIP attacks, for webRTC and turnserver
Got the information's from PC1. He can continue ?
8.10:30 AM:
turnutils_uclient -v -n 1000 -m 2 -l 170 -e 82.x -g -u root -w root 82.x # FAIL - UDP WebRTC: http://apprtc/?r=id&ts=root@ip:port&transport=udp&tp=root
continues.... ?
Best regards
/Sham
Oleg Moskalenko
Dec 19, 2013, 6:14:30 AM12/19/13
to Shamun Toha Md, turn-server-project...@googlegroups.com
That is not a security hole because the session is tied to the client IP address and port. Other destination will not be able to reuse the session.
Sent from my iPhone
Sent from my iPhone
Shamun Toha Md
Dec 19, 2013, 6:16:05 AM12/19/13
to Oleg Moskalenko, turn-server-project...@googlegroups.com
Excellent. Thank you very much.
reg
/sham
Shamun Toha Md
Dec 19, 2013, 7:04:59 AM12/19/13
to Oleg Moskalenko, turn-server-project...@googlegroups.com
FYI Test results:
2) Google Chrome - FAIL webRTC when mentioned to use transport protocol = TCP or UDP, it always connecting to turn-server as UDP only, but when Google Chrome version above 31 is used then it seems like TCP was used correctly.
Here is turn server log when TCP is used by Google Chrome webRTC:
When Google Chrome version 31 is used from a Windows PC, it seems the TCP transport was
working. but when Google Chrome is used in less then version 31, then the TCP
transport seems to be broken in Google Chrome/Google Canary/Google Chromium.
### Here is a Successfull Google Chrome WebRTC - Turn server successfull trace in
turn server with TCP protocol. In this trace one peer is using Google Chrome version less then 31 and another is above version 31
> ps
1) id=000000000000000008, user <root>:
expiring in 566 secs
client protocol TCP, relay protocol UDP
client addr 82.x.x.x:38123, server addr 192.168.1.12:3478
relay addr 192.168.1.12:53322
fingerprints enforced: OFF
mobile: OFF
SHA256 only: OFF
usage: rp=5, rb=440, sp=4, sb=372
peers:
192.168.1.15
82.x.x.3
192.168.1.12
2) id=003000000000000008, user <root>:
expiring in 566 secs
client protocol TCP, relay protocol UDP
client addr 82.x.x.x:38121, server addr 192.168.1.12:3478
relay addr 192.168.1.12:64966
fingerprints enforced: OFF
mobile: OFF
SHA256 only: OFF
usage: rp=5, rb=440, sp=4, sb=372
peers:
192.168.1.15
82.x.x.3
192.168.1.12
3) id=002000000000000006, user <root>:
expiring in 566 secs
client protocol TCP, relay protocol UDP
client addr 82.x.x.x:38110, server addr 192.168.1.12:3478
relay addr 192.168.1.12:50701
fingerprints enforced: OFF
mobile: OFF
SHA256 only: OFF
usage: rp=5, rb=440, sp=4, sb=372
peers:
192.168.1.15
82.x.x.3
192.168.1.12
4) id=001000000000000007, user <root>:
expiring in 566 secs
client protocol TCP, relay protocol UDP
client addr 82.x.x.x:38122, server addr 192.168.1.12:3478
relay addr 192.168.1.12:56686
fingerprints enforced: OFF
mobile: OFF
SHA256 only: OFF
usage: rp=5, rb=440, sp=4, sb=372
peers:
192.168.1.15
82.x.x.3
192.168.1.12
5) id=000000000000000006, user <root>:
expiring in 566 secs
client protocol TCP, relay protocol UDP
client addr 82.x.x.x:38114, server addr 192.168.1.12:3478
relay addr 192.168.1.12:65500
fingerprints enforced: OFF
mobile: OFF
SHA256 only: OFF
usage: rp=5, rb=440, sp=4, sb=372
peers:
192.168.1.15
82.x.x.3
192.168.1.12
6) id=001000000000000005, user <root>:
expiring in 566 secs
client protocol TCP, relay protocol UDP
client addr 82.x.x.x:38115, server addr 192.168.1.12:3478
relay addr 192.168.1.12:57968
fingerprints enforced: OFF
mobile: OFF
SHA256 only: OFF
usage: rp=5, rb=440, sp=4, sb=372
peers:
192.168.1.15
82.x.x.3
192.168.1.12
7) id=003000000000000005, user <root>:
expiring in 566 secs
client protocol TCP, relay protocol UDP
client addr 82.x.x.x:38111, server addr 192.168.1.12:3478
relay addr 192.168.1.12:53456
fingerprints enforced: OFF
mobile: OFF
SHA256 only: OFF
usage: rp=5, rb=440, sp=4, sb=372
peers:
192.168.1.15
82.x.x.3
192.168.1.12
8) id=002000000000000008, user <root>:
expiring in 566 secs
client protocol TCP, relay protocol UDP
client addr 82.x.x.x:38116, server addr 192.168.1.12:3478
relay addr 192.168.1.12:64598
fingerprints enforced: OFF
mobile: OFF
SHA256 only: OFF
usage: rp=5, rb=440, sp=4, sb=372
peers:
192.168.1.15
82.x.x.3
192.168.1.12
9) id=003000000000000007, user <root>:
expiring in 566 secs
client protocol TCP, relay protocol UDP
client addr 82.x.x.x:38117, server addr 192.168.1.12:3478
relay addr 192.168.1.12:53273
fingerprints enforced: OFF
mobile: OFF
SHA256 only: OFF
usage: rp=5, rb=440, sp=4, sb=372
peers:
192.168.1.15
82.x.x.3
192.168.1.12
10) id=000000000000000007, user <root>:
expiring in 566 secs
client protocol TCP, relay protocol UDP
client addr 82.x.x.x:38118, server addr 192.168.1.12:3478
relay addr 192.168.1.12:51289
fingerprints enforced: OFF
mobile: OFF
SHA256 only: OFF
usage: rp=5, rb=440, sp=4, sb=372
peers:
192.168.1.15
82.x.x.3
192.168.1.12
11) id=002000000000000007, user <root>:
expiring in 566 secs
client protocol TCP, relay protocol UDP
client addr 82.x.x.x:38112, server addr 192.168.1.12:3478
relay addr 192.168.1.12:53758
fingerprints enforced: OFF
mobile: OFF
SHA256 only: OFF
usage: rp=5, rb=440, sp=4, sb=372
peers:
192.168.1.15
82.x.x.3
192.168.1.12
12) id=002000000000000010, user <root>:
expiring in 566 secs
client protocol TCP, relay protocol UDP
client addr 82.x.x.x:38125, server addr 192.168.1.12:3478
relay addr 192.168.1.12:50649
fingerprints enforced: OFF
mobile: OFF
SHA256 only: OFF
usage: rp=5, rb=440, sp=4, sb=372
peers:
192.168.1.15
82.x.x.3
192.168.1.12
13) id=003000000000000006, user <root>:
expiring in 566 secs
client protocol TCP, relay protocol UDP
client addr 82.x.x.x:38113, server addr 192.168.1.12:3478
relay addr 192.168.1.12:61337
fingerprints enforced: OFF
mobile: OFF
SHA256 only: OFF
usage: rp=5, rb=440, sp=4, sb=372
peers:
192.168.1.15
82.x.x.3
192.168.1.12
14) id=001000000000000006, user <root>:
expiring in 566 secs
client protocol TCP, relay protocol UDP
client addr 82.x.x.x:38119, server addr 192.168.1.12:3478
relay addr 192.168.1.12:65251
fingerprints enforced: OFF
mobile: OFF
SHA256 only: OFF
usage: rp=5, rb=440, sp=4, sb=372
peers:
192.168.1.15
82.x.x.3
192.168.1.12
15) id=003000000000000009, user <root>:
expiring in 566 secs
client protocol TCP, relay protocol UDP
client addr 82.x.x.x:38124, server addr 192.168.1.12:3478
relay addr 192.168.1.12:52259
fingerprints enforced: OFF
mobile: OFF
SHA256 only: OFF
usage: rp=5, rb=440, sp=4, sb=372
peers:
192.168.1.15
82.x.x.3
192.168.1.12
16) id=002000000000000009, user <root>:
expiring in 566 secs
client protocol TCP, relay protocol UDP
client addr 82.x.x.x:38120, server addr 192.168.1.12:3478
relay addr 192.168.1.12:62289
fingerprints enforced: OFF
mobile: OFF
SHA256 only: OFF
usage: rp=5, rb=440, sp=4, sb=372
peers:
192.168.1.15
82.x.x.3
192.168.1.12
17) id=001000000000000009, user <root>:
expiring in 566 secs
client protocol TCP, relay protocol UDP
client addr 82.x.x.3:50950, server addr 192.168.1.12:3478
relay addr 192.168.1.12:62970
fingerprints enforced: OFF
mobile: OFF
SHA256 only: OFF
usage: rp=299, rb=39160, sp=182, sb=27620
peers:
5.5.13.1
5.5.15.1
5.5.2.1
5.5.5.1
5.5.6.1
5.5.11.1
5.5.9.1
192.168.1.17
5.5.8.1
5.5.10.1
5.5.14.1
5.5.0.1
5.5.3.1
5.5.4.1
5.5.1.1
5.5.12.1
5.5.7.1
18) id=001000000000000008, user <root>:
expiring in 566 secs
client protocol TCP, relay protocol UDP
client addr 82.x.x.x:38126, server addr 192.168.1.12:3478
relay addr 192.168.1.12:54868
fingerprints enforced: OFF
mobile: OFF
SHA256 only: OFF
usage: rp=5, rb=440, sp=4, sb=372
peers:
192.168.1.15
82.x.x.3
192.168.1.12
Total sessions: 18
Thank you
Reg
/Sham
Shamun Toha Md
Dec 19, 2013, 7:07:29 AM12/19/13
to Oleg Moskalenko, turn-server-project...@googlegroups.com
Here in telenet CLI command i think its confusing to use the ps command. Because see my above logs, its saying Total Session: 18 but actually 2 Google chrome was used only.
So while having Peer1 , Peer 2 using turnserver. How can we identify that only 2 users are connected real-time alive? where Total session: 18 is valid for other case i think.
thanks
reg
/sham
Oleg Moskalenko
Dec 19, 2013, 7:11:48 AM12/19/13
to Shamun Toha Md, turn-server-project...@googlegroups.com
If you would be using real users then you would see different users in the output. You could then run command pu and see separate users. But now you are using the same user root for everything and there is no way to separate them, except that you can check the "client addr" info.
Shamun Toha Md
Dec 19, 2013, 7:21:07 AM12/19/13
to Oleg Moskalenko, turn-server-project...@googlegroups.com
YES - i understand. Thank you very much.
> even having telnet as it is for CLI. Is there still a way we can dump those to a log file?
and use our own external parser to the RAW logs, and real-time find out how many real-Browser or real-Peers are connected
how many actual concurrent users are connected to the turn-server (for some firewall workouts)
> this information is not URGENT, but i wanted to use it in statistics and Firewall/Fail2Ban (in case some DoS attackers to play)
Sprogrammer
Dec 19, 2013, 8:05:26 AM12/19/13
to turn-server-project...@googlegroups.com, Shamun Toha Md
OK - Thank you. I am using one single username/password as root:root for A to Z sessions to allow (that is ok for me).
But i was not clear why still its saying Total session: 18.
See below 18 sessions, 2 PC connected
1) turnserver sees 18 session for 1 session or 3 session
> pu
user: <root>, 18 sessions
Total sessions: 18
> ps
1) id=000000000000000015, user <root>:
expiring in 569 secs
client protocol TCP, relay protocol UDP
client addr 8.8.8.PC1.MyLaptop.GoogleChrome.Linux:38349, server addr 192.168.1.12:3478
relay addr 192.168.1.12:61499
fingerprints enforced: OFF
mobile: OFF
SHA256 only: OFF
usage: rp=7, rb=736, sp=4, sb=372
peers:
192.168.1.15
8.8.8.PC2.WindowsPC.GoogleChrome.Version31
192.168.1.12
2) id=002000000000000018, user <root>:
expiring in 569 secs
client protocol TCP, relay protocol UDP
client addr 8.8.8.PC1.MyLaptop.GoogleChrome.Linux:38351, server addr 192.168.1.12:3478
relay addr 192.168.1.12:54889
fingerprints enforced: OFF
mobile: OFF
SHA256 only: OFF
usage: rp=7, rb=736, sp=4, sb=372
peers:
192.168.1.15
8.8.8.PC2.WindowsPC.GoogleChrome.Version31
192.168.1.12
3) id=001000000000000018, user <root>:
expiring in 569 secs
client protocol TCP, relay protocol UDP
client addr 8.8.8.PC1.MyLaptop.GoogleChrome.Linux:38357, server addr 192.168.1.12:3478
relay addr 192.168.1.12:61867
fingerprints enforced: OFF
mobile: OFF
SHA256 only: OFF
usage: rp=7, rb=736, sp=4, sb=372
peers:
192.168.1.15
8.8.8.PC2.WindowsPC.GoogleChrome.Version31
192.168.1.12
4) id=001000000000000016, user <root>:
expiring in 569 secs
client protocol TCP, relay protocol UDP
client addr 8.8.8.PC1.MyLaptop.GoogleChrome.Linux:38348, server addr 192.168.1.12:3478
relay addr 192.168.1.12:63757
fingerprints enforced: OFF
mobile: OFF
SHA256 only: OFF
usage: rp=7, rb=736, sp=4, sb=372
peers:
192.168.1.15
8.8.8.PC2.WindowsPC.GoogleChrome.Version31
192.168.1.12
5) id=002000000000000017, user <root>:
expiring in 569 secs
client protocol TCP, relay protocol UDP
client addr 8.8.8.PC1.MyLaptop.GoogleChrome.Linux:38347, server addr 192.168.1.12:3478
relay addr 192.168.1.12:56431
fingerprints enforced: OFF
mobile: OFF
SHA256 only: OFF
usage: rp=7, rb=736, sp=4, sb=372
peers:
192.168.1.15
8.8.8.PC2.WindowsPC.GoogleChrome.Version31
192.168.1.12
6) id=001000000000000014, user <root>:
expiring in 569 secs
client protocol TCP, relay protocol UDP
client addr 8.8.8.PC2.WindowsPC.GoogleChrome.Version31:51002, server addr 192.168.1.12:3478
relay addr 192.168.1.12:62038
fingerprints enforced: OFF
mobile: OFF
SHA256 only: OFF
usage: rp=472, rb=54192, sp=410, sb=40572
peers:
5.5.13.1
5.5.15.1
5.5.2.1
5.5.6.1
5.5.5.1
5.5.11.1
5.5.9.1
192.168.1.17
5.5.8.1
8.8.8.PC1.MyLaptop.GoogleChrome.Linux
5.5.10.1
5.5.14.1
5.5.0.1
5.5.3.1
5.5.4.1
192.168.1.12
5.5.1.1
5.5.12.1
5.5.7.1
7) id=003000000000000014, user <root>:
expiring in 569 secs
client protocol TCP, relay protocol UDP
client addr 8.8.8.PC1.MyLaptop.GoogleChrome.Linux:38342, server addr 192.168.1.12:3478
relay addr 192.168.1.12:61883
fingerprints enforced: OFF
mobile: OFF
SHA256 only: OFF
usage: rp=7, rb=736, sp=4, sb=372
peers:
192.168.1.15
8.8.8.PC2.WindowsPC.GoogleChrome.Version31
192.168.1.12
8) id=003000000000000017, user <root>:
expiring in 569 secs
client protocol TCP, relay protocol UDP
client addr 8.8.8.PC1.MyLaptop.GoogleChrome.Linux:38355, server addr 192.168.1.12:3478
relay addr 192.168.1.12:49854
fingerprints enforced: OFF
mobile: OFF
SHA256 only: OFF
usage: rp=7, rb=736, sp=4, sb=372
peers:
192.168.1.15
8.8.8.PC2.WindowsPC.GoogleChrome.Version31
192.168.1.12
9) id=003000000000000016, user <root>:
expiring in 569 secs
client protocol TCP, relay protocol UDP
client addr 8.8.8.PC1.MyLaptop.GoogleChrome.Linux:38350, server addr 192.168.1.12:3478
relay addr 192.168.1.12:51086
fingerprints enforced: OFF
mobile: OFF
SHA256 only: OFF
usage: rp=7, rb=736, sp=4, sb=372
peers:
192.168.1.15
8.8.8.PC2.WindowsPC.GoogleChrome.Version31
192.168.1.12
10) id=000000000000000016, user <root>:
expiring in 569 secs
client protocol TCP, relay protocol UDP
client addr 8.8.8.PC1.MyLaptop.GoogleChrome.Linux:38352, server addr 192.168.1.12:3478
relay addr 192.168.1.12:57335
fingerprints enforced: OFF
mobile: OFF
SHA256 only: OFF
usage: rp=7, rb=736, sp=4, sb=372
peers:
192.168.1.15
8.8.8.PC2.WindowsPC.GoogleChrome.Version31
192.168.1.12
11) id=000000000000000013, user <root>:
expiring in 569 secs
client protocol TCP, relay protocol UDP
client addr 8.8.8.PC1.MyLaptop.GoogleChrome.Linux:38341, server addr 192.168.1.12:3478
relay addr 192.168.1.12:51733
fingerprints enforced: OFF
mobile: OFF
SHA256 only: OFF
usage: rp=7, rb=736, sp=4, sb=372
peers:
192.168.1.15
8.8.8.PC2.WindowsPC.GoogleChrome.Version31
192.168.1.12
12) id=002000000000000019, user <root>:
expiring in 569 secs
client protocol TCP, relay protocol UDP
client addr 8.8.8.PC1.MyLaptop.GoogleChrome.Linux:38354, server addr 192.168.1.12:3478
relay addr 192.168.1.12:51253
fingerprints enforced: OFF
mobile: OFF
SHA256 only: OFF
usage: rp=7, rb=736, sp=4, sb=372
peers:
192.168.1.15
8.8.8.PC2.WindowsPC.GoogleChrome.Version31
192.168.1.12
13) id=001000000000000017, user <root>:
expiring in 569 secs
client protocol TCP, relay protocol UDP
client addr 8.8.8.PC1.MyLaptop.GoogleChrome.Linux:38353, server addr 192.168.1.12:3478
relay addr 192.168.1.12:50224
fingerprints enforced: OFF
mobile: OFF
SHA256 only: OFF
usage: rp=7, rb=736, sp=4, sb=372
peers:
192.168.1.15
8.8.8.PC2.WindowsPC.GoogleChrome.Version31
192.168.1.12
14) id=003000000000000015, user <root>:
expiring in 569 secs
client protocol TCP, relay protocol UDP
client addr 8.8.8.PC1.MyLaptop.GoogleChrome.Linux:38346, server addr 192.168.1.12:3478
relay addr 192.168.1.12:59612
fingerprints enforced: OFF
mobile: OFF
SHA256 only: OFF
usage: rp=7, rb=736, sp=4, sb=372
peers:
192.168.1.15
8.8.8.PC2.WindowsPC.GoogleChrome.Version31
192.168.1.12
15) id=001000000000000015, user <root>:
expiring in 569 secs
client protocol TCP, relay protocol UDP
client addr 8.8.8.PC1.MyLaptop.GoogleChrome.Linux:38344, server addr 192.168.1.12:3478
relay addr 192.168.1.12:62909
fingerprints enforced: OFF
mobile: OFF
SHA256 only: OFF
usage: rp=7, rb=736, sp=4, sb=372
peers:
192.168.1.15
8.8.8.PC2.WindowsPC.GoogleChrome.Version31
192.168.1.12
16) id=000000000000000014, user <root>:
expiring in 569 secs
client protocol TCP, relay protocol UDP
client addr 8.8.8.PC1.MyLaptop.GoogleChrome.Linux:38345, server addr 192.168.1.12:3478
relay addr 192.168.1.12:52593
fingerprints enforced: OFF
mobile: OFF
SHA256 only: OFF
usage: rp=7, rb=736, sp=4, sb=372
peers:
192.168.1.15
8.8.8.PC2.WindowsPC.GoogleChrome.Version31
192.168.1.12
17) id=000000000000000017, user <root>:
expiring in 569 secs
client protocol TCP, relay protocol UDP
client addr 8.8.8.PC1.MyLaptop.GoogleChrome.Linux:38356, server addr 192.168.1.12:3478
relay addr 192.168.1.12:52695
fingerprints enforced: OFF
mobile: OFF
SHA256 only: OFF
usage: rp=7, rb=736, sp=4, sb=372
peers:
192.168.1.15
8.8.8.PC2.WindowsPC.GoogleChrome.Version31
192.168.1.12
18) id=002000000000000016, user <root>:
expiring in 569 secs
client protocol TCP, relay protocol UDP
client addr 8.8.8.PC1.MyLaptop.GoogleChrome.Linux:38343, server addr 192.168.1.12:3478
relay addr 192.168.1.12:58846
fingerprints enforced: OFF
mobile: OFF
SHA256 only: OFF
usage: rp=7, rb=736, sp=4, sb=372
peers:
192.168.1.15
8.8.8.PC2.WindowsPC.GoogleChrome.Version31
192.168.1.12
Total sessions: 18
2) Total network interface in this single session is:
PC 2 (windows) = 2 interface one for ethernet and one for local lan
PC 1 (laptop) = 19 interface (1 ethernet, 1 wifi, 1 local areay lan, 16 interface for VPN)
Total: 21 sessions, but turnserver saying 18 session why? and how is this calculated by interface or by packets that arrived from Google Chrome to turn-server?
sun@sun-M14xR2:~/Downloads$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether d4:be:d9:55:91:4a brd ff:ff:ff:ff:ff:ff
inet 192.168.1.17/24 brd 192.168.1.255 scope global eth0
inet6 fe80::d6be:d9ff:fe55:914a/64 scope link
valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN qlen 1000
link/ether 68:5d:43:f1:88:f8 brd ff:ff:ff:ff:ff:ff
4: as0t0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 200
link/none
inet 5.5.0.1/24 brd 5.5.0.255 scope global as0t0
5: as0t1: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 200
link/none
inet 5.5.1.1/24 brd 5.5.1.255 scope global as0t1
6: as0t2: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 200
link/none
inet 5.5.2.1/24 brd 5.5.2.255 scope global as0t2
7: as0t3: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 200
link/none
inet 5.5.3.1/24 brd 5.5.3.255 scope global as0t3
8: as0t4: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 200
link/none
inet 5.5.4.1/24 brd 5.5.4.255 scope global as0t4
9: as0t5: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 200
link/none
inet 5.5.5.1/24 brd 5.5.5.255 scope global as0t5
10: as0t6: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 200
link/none
inet 5.5.6.1/24 brd 5.5.6.255 scope global as0t6
11: as0t7: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 200
link/none
inet 5.5.7.1/24 brd 5.5.7.255 scope global as0t7
12: as0t8: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 200
link/none
inet 5.5.8.1/24 brd 5.5.8.255 scope global as0t8
13: as0t9: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 200
link/none
inet 5.5.9.1/24 brd 5.5.9.255 scope global as0t9
14: as0t10: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 200
link/none
inet 5.5.10.1/24 brd 5.5.10.255 scope global as0t10
15: as0t11: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 200
link/none
inet 5.5.11.1/24 brd 5.5.11.255 scope global as0t11
16: as0t12: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 200
link/none
inet 5.5.12.1/24 brd 5.5.12.255 scope global as0t12
17: as0t13: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 200
link/none
inet 5.5.13.1/24 brd 5.5.13.255 scope global as0t13
18: as0t14: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 200
link/none
inet 5.5.14.1/24 brd 5.5.14.255 scope global as0t14
19: as0t15: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 200
link/none
inet 5.5.15.1/24 brd 5.5.15.255 scope global as0t15
How does this session understand that Total session is: 18? not 21??
Oleg Moskalenko
Dec 19, 2013, 8:26:51 AM12/19/13
to Shamun Toha Md, turn-server-project...@googlegroups.com
I ll add a dump command
Sent from my iPhone
Sent from my iPhone
Oleg Moskalenko
Dec 19, 2013, 8:28:29 AM12/19/13
to Sprogrammer, turn-server-project...@googlegroups.com, Shamun Toha Md
There are 18 turn tcp client connections so it is saying 18 sessions.
Sent from my iPhone
Sent from my iPhone
--
Sprogrammer
Dec 19, 2013, 8:37:31 AM12/19/13
to turn-server-project...@googlegroups.com, Shamun Toha Md
OK - thank you. Then its WebRTC Turn implementation issue, not related to turn-server.
Turn-server is doing excellent job. I can now see that sometimes WebRTC implementation is causing a confusion.
I also tested with PjSIP, cSipSimple, JsSIP, Sip... all works perfectly. This, Server version is very stable/reliable.
-> WebRTC need to check if a PC is using VPN, Wifi interface that it should count it as 21 not 18
Thank you
Best regards
/Sham
Reply all
Reply to author
Forward
Message has been deleted
0 new messages