Hello

A few days ago my TS server stopped to be accessible from the GTracker Servers and now it is at the state of 'SERVER DEAD' But, it works as usuall (for over the last 2 years) and me and my friends can use it all that time .

I've chescked the firewall rooles (the TS server works on my Centos 6 machine) and everything looks good -> there is a roole for incomming packets from the Internet to my server on Game Query Port (10011) and it is working well. Next I've checked the tcpdump output when I did several scans-on-demand from the Gametracker Web Interface . It looks quite well :

18:59:06.277167 IP (tos 0x0, ttl 53, id 1179, offset 0, flags [DF], proto TCP (6), length 60)
www5.gametracker.com.56056 > 149.156.229.19.10011: Flags [S], cksum 0xfa4e (correct), seq 3181307324, win 14600, options [mss 1380,sackOK,TS val 3086056070 ecr 0,nop,wscale 7], length 0
18:59:06.277229 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 60)
149.156.229.19.10011 > www5.gametracker.com.56056: Flags [S.], cksum 0xbbdb (correct), seq 3736125506, ack 3181307325, win 14480, options [mss 1460,sackOK,TS val 1592606889 ecr 3086056070,nop,wscale 7], length 0

So if Gametracker Server gets the response from my TSserver- as it looks like above - can You help me with understanding if it 's a good response or maybe there is an error code in it (or something I've missed ??? )

Thanks in advance
markooff

In adition - I send the whole output from the the tcpdump written headers (from the scan-on-demand of my TSserver) :

19:03:51.215341 IP (tos 0x0, ttl 53, id 5270, offset 0, flags [DF], proto TCP (6), length 60)
www5.gametracker.com.57499 > 149.156.229.19.10011: Flags [S], cksum 0x1665 (correct), seq 794949944, win 14600, options [mss 1380,sackOK,TS val 3086341002 ecr 0,nop,wscale 7], length 0
19:03:51.215422 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 60)
149.156.229.19.10011 > www5.gametracker.com.57499: Flags [S.], cksum 0xa29e (correct), seq 302737708, ack 794949945, win 14480, options [mss 1460,sackOK,TS val 1592891828 ecr 3086341002,nop,wscale 7], length 0
19:03:51.327869 IP (tos 0x0, ttl 53, id 5271, offset 0, flags [DF], proto TCP (6), length 52)
www5.gametracker.com.57499 > 149.156.229.19.10011: Flags [.], cksum 0x0918 (correct), seq 1, ack 1, win 115, options [nop,nop,TS val 3086341114 ecr 1592891828], length 0
19:03:51.334407 IP (tos 0x0, ttl 64, id 62217, offset 0, flags [DF], proto TCP (6), length 203)
149.156.229.19.10011 > www5.gametracker.com.57499: Flags [P.], cksum 0x3dcf (incorrect -> 0xbd18), seq 1:152, ack 1, win 114, options [nop,nop,TS val 1592891947 ecr 3086341114], length 151
19:03:51.448031 IP (tos 0x0, ttl 53, id 5272, offset 0, flags [DF], proto TCP (6), length 52)
www5.gametracker.com.57499 > 149.156.229.19.10011: Flags [.], cksum 0x078a (correct), seq 1, ack 152, win 123, options [nop,nop,TS val 3086341234 ecr 1592891947], length 0
19:03:51.449053 IP (tos 0x0, ttl 53, id 5273, offset 0, flags [DF], proto TCP (6), length 146)
www5.gametracker.com.57499 > 149.156.229.19.10011: Flags [P.], cksum 0x0465 (correct), seq 1:95, ack 152, win 123, options [nop,nop,TS val 3086341235 ecr 1592891947], length 94
19:03:51.449069 IP (tos 0x0, ttl 64, id 62218, offset 0, flags [DF], proto TCP (6), length 52)
149.156.229.19.10011 > www5.gametracker.com.57499: Flags [.], cksum 0x06c2 (correct), seq 152, ack 95, win 114, options [nop,nop,TS val 1592892061 ecr 3086341235], length 0
19:03:51.450768 IP (tos 0x0, ttl 64, id 62219, offset 0, flags [DF], proto TCP (6), length 71)
149.156.229.19.10011 > www5.gametracker.com.57499: Flags [P.], cksum 0x3d4b (incorrect -> 0xccbf), seq 152:171, ack 95, win 114, options [nop,nop,TS val 1592892063 ecr 3086341235], length 19
19:03:51.451154 IP (tos 0x0, ttl 64, id 62220, offset 0, flags [DF], proto TCP (6), length 281)
149.156.229.19.10011 > www5.gametracker.com.57499: Flags [P.], cksum 0x3e1d (incorrect -> 0x17da), seq 171:400, ack 95, win 114, options [nop,nop,TS val 1592892063 ecr 3086341235], length 229
19:03:51.565243 IP (tos 0x0, ttl 53, id 5274, offset 0, flags [DF], proto TCP (6), length 52)
www5.gametracker.com.57499 > 149.156.229.19.10011: Flags [.], cksum 0x0543 (correct), seq 95, ack 400, win 131, options [nop,nop,TS val 3086341351 ecr 1592892063], length 0
19:03:51.565273 IP (tos 0x0, ttl 53, id 5275, offset 0, flags [DF], proto TCP (6), length 52)
www5.gametracker.com.57499 > 149.156.229.19.10011: Flags [F.], cksum 0x0542 (correct), seq 95, ack 400, win 131, options [nop,nop,TS val 3086341351 ecr 1592892063], length 0
19:03:51.565734 IP (tos 0x0, ttl 64, id 62221, offset 0, flags [DF], proto TCP (6), length 52)
149.156.229.19.10011 > www5.gametracker.com.57499: Flags [F.], cksum 0x04df (correct), seq 400, ack 96, win 114, options [nop,nop,TS val 1592892178 ecr 3086341351], length 0
19:03:51.678079 IP (tos 0x0, ttl 53, id 5276, offset 0, flags [DF], proto TCP (6), length 52)
www5.gametracker.com.57499 > 149.156.229.19.10011: Flags [.], cksum 0x045c (correct), seq 96, ack 401, win 131, options [nop,nop,TS val 3086341465 ecr 1592892178], length 0


This was created with the command :
tcpdump -vv -i eth0 'tcp port 10011'

In addition - here are my firewall rooles for TS-coonveration:

Chain INPUT (policy ACCEPT)
target prot opt source destination
//
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:9987
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:10011
//
ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:9987
//

Chain OUTPUT (policy ACCEPT)


version of my running TS server -: 3.0.13.6


thanks,
markooff

You are aware that these are the valid Gametracker scanner IPs?
GameTracker scanner IP addresses

If you follow the tests in this link to ensure your server has the correct permissions.
Common TeamSpeak 3 Scanning Problems


Microsoft Telnet> open 149.156.229.19 10011

TS3
Welcome to the TeamSpeak 3 ServerQuery interface, type "help" for a list of commands and "help <command>" for information on a specific command.
use port=9987
error id=0 msg=ok
serverinfo
error id=2568 msg=insufficient\sclient\spermissions failed_permid=23

Thank You chimaera500 very much for help !

Indeed, together with my friends, we changed some of the permissions on our server during the last few days. But it looks a bit strange for me - I didnt imagine that the result of lack of the permission could be the server inaccessibility for Gametracker query mechanism...
The links You've put in Your answer tell me much more about the nature of the problem. I've done the console test using my bash/telnet console (just like You have done) and got the same results.

The problem is solved.

Thank you again!
markooff

Good to hear.
I am pleased to be able to help.

powodzenia