Review Teamspeak3 Proxy

[Bluscream]

I made some preparations but im not trying to finish it at 1:29am xD

https://github.com/Bluscream/ts3proxy/commits/weblist

 

[FarisDev]

I'm not understand what is the feature of ts3 proxy, can you make some pictures.

 

[maxst]

@B1uscr34m why not?
@SpeciaL please read the first post in this thread carefully and try to understand it. I already described it easily for another user of r4p3.net. A screenshout wouldn't help you to understand what's going on.

 

[Shield]

new script works fine

 

[Grid]

Thanks for the intel @maxst and @B1uscr34m !

 

[maxst]

Thx @1nject I really appreciate that! And even thanks to @B1uscr34m for his pull request that allows to disable the relays if wanted.

 

[Shield]

got error after typr ts3proxy command
root@ubuntu:/home# ts3proxy
[2017-05-30 08:10:04,754] Voice: 0.0.0.0:9987 <-> 152.104.47.16:9987
Traceback (most recent call last):
File "/usr/local/bin/ts3proxy", line 9, in <module>
load_entry_point('ts3proxy==0.2', 'console_scripts', 'ts3proxy')()
File "/home/ts3proxy/ts3proxy.py", line 49, in main
file_transfer = Tcp(*file_transfer_args[:4])
File "/home/ts3proxy/tcp.py", line 20, in __init__
self.socket.listen()

 

[maxst]

@Shield what python version? Maybe the script is already running (or the port ist already used?).

 

[Shield]

@Shield what python version? Maybe the script is already running (or the port ist already used?).

python3 installed manually, default version python2.7.2 (Script working, proxy works fine but i need to fix this errors) check inbox i send you my config file

 

[spamek23]

So It's random IP or I must buy 2x VPS?

 

[maxst]

@spamek23 I described that in the first post. Please read it carefully - this tool is useless for someone with an own teamspeak3 vps without a second vps. It's a proxy.

 

[Shield]

@maxst this is how i filled my config... still got error

system:
logLevel: INFO
ts3server:
enabled: True
relayAddress: 0.0.0.0
relayPort: 9987
remoteAddress: 173.105.47.16 (Do not delete this comment IP is fake)
remotePort: 9987
ts3FileTransfer:
enabled: True
relayAddress: 0.0.0.0
relayPort: 30033
remoteAddress: 173.105.47.16
remotePort: 30033
ts3ServerQuery:
enabled: True
relayAddress: 0.0.0.0
relayPort: 10011
remoteAddress: 173.105.47.16
remotePort: 10011

 

[maxst]

@Shield config isnt neccessary if there is a fault in the config you would notice another error message. Did you use the second Release? https://github.com/Kandru/ts3proxy/releases
And are you sure that this was the complete error? The traceback doesn't seem to be complete. If it's complete something is wrong on your system. Check if the port is already used by another application.

 

[spamek23]

maxst so If aggressors use DDoS for "fake" IP so clients can't connect to ts3.

 

[Shield]

@Shield config isnt neccessary if there is a fault in the config you would notice another error message. Did you use the second Release? https://github.com/Kandru/ts3proxy/releases
And are you sure that this was the complete error? The traceback doesn't seem to be complete. If it's complete something is wrong on your system. Check if the port is already used by another application.

got this error on second release.... port not used by another program... :/

 

[maxst]

@spamek23 not exactly but somehow yes.
If you want to hide your origins teamspeak IP (as an server owner) you'll set up one or more other VPS in different data centers and install this proxy on it. These VPS will then proxy all requests to the origin teamspeak3 server. If someone wants to take down your ts3 he'll probably only will take down your proxy. If you have multiple vps it's more hard to take down your teamspeak. At least all people will disconnect once when the DDoS starts but they can reconnect using another proxy vps - you could even try to automate that with DNS entries. If a provider has some DDoS protection it's even more effective. But you should may notice: if someone does "spam" the ts3 server ports the proxy will send all that stuff to the origin teamspeak3. So not every kind of DDoS attack is covered.

 

[spamek23]

My friend use iptables or proxy I don't know what. But he use random IP.
Example:
Client name: XYZ connect to teamspeak domain: asd.com on 30-05-2017 r. 11:50 and see IP: 1.1.1.1
Client XYZ quit.
Client XYZ connect to teamspeak domain asd.com on 30-05-2017 r. 11:51 and see IP: 1.1.2.2
and so on.
Maybe it's better from DDoS and for GreyList xD
Regards

 

[maxst]

@spamek23
Random IP would only be possible if you hide your real IP with an VPN or if you have a big subnet (and much different IP addresses). That's not the goal of this proxy. Nevermind I just committed a blacklist / whitelist a few seconds ago. README for this feature is on its way.

 

[XRV-Webix]

I had something like this working with iptables last year.
I had 7 servers has "frontends" and the server with the teamspeak on "backend".
I used the srv records to distribute the connections to each "frontend".
It was awesome against DDoS attacks, but the problem is that the teamspeak server can't see the "real" IP of the client.
It may be better to use iptables than a python script to do the job because is less resource consumption and has a better performance.

Just my oppinion.

 

[maxst]

Hey @Webix,
I think unless you have 1.000s of users you won't notice any difference at all. And ts3proxy does more then just simply proxy the request - it has a built in white / blacklist and informs the teamspeak weblist about the proxy if wanted. But yes, IPtables would be okay. I would at least setup some logging to grep some statistics about the usage.