Results 1 to 15 of 15
Thread: TS: Flood protection Join/leave
-
24-10-2005, 05:58 #1
-= TeamSpeak User =-
- Join Date
- Oct 2005
- Location
- na
- Posts
- 4
TS: Flood protection Join/leave
Hello all and yes we have came crosss where fags flood servers and the work around is password server I have a few ideas if possiable
1) Default channel We can not edit the limit of this channel if we could do so Like max 5 players we would move voice users to a dirrent channel or they can move themselfs and if idek they get kicked from that channel
thats one
2) I have seen many people make it so you can join a server from a web interface is there anyway possiable when somone join from a web internface they can join a password protected server that way the flood willl be very lame and not as strong as the one on the internet .
so basicly have them login to the ts server without seeing the password but only using the web interface
I know nothing about coding but this will help many people instead of makeing ts uselsss I know nothing about designing my own thing soo all help please if you dont under stand what im say just let me know
one other way limiting TS access for 1 ip account to TS but im sure thats firewall rules does anyone have any ideas about any of this
thanks for your time and effot
-
24-10-2005, 11:25 #21. Not Possible because in the default channel are coming all users who didn't configure any channel. So it's not possible to edit the max users
Originally Posted by weaklinks
2. I'm not sure. It is possible to connect via viewer or webinterface to a password protected server. And also at the first time the user didn't see password. But when you click on the link you will get something like this:
teamspeak://SERVER_IP:PORT?nickname=Guest?password=server_pass
So everybody can see the password.
-
24-10-2005, 16:43 #3
-= TeamSpeak Fanatic =-
- Join Date
- Nov 2002
- Location
- Germany / Kempen
- Posts
- 1,844
Best way to protect: A serveradmin and the ability to set a serverpassword. Currently nothing else.
-
25-10-2005, 14:26 #4
youre right crow... maybe this flood-protection could also be a feature-request for ts³
-
25-10-2005, 17:08 #5
-= TeamSpeak Fanatic =-
- Join Date
- Nov 2002
- Location
- Germany / Kempen
- Posts
- 1,844
I'm sure the developers keep that problem in mind and will find and insert a compfortable solution to suppress such actions.
-
25-10-2005, 23:37 #6
-= TeamSpeak User =-
- Join Date
- Oct 2005
- Location
- na
- Posts
- 4
ok how about this windows server 2003 IPrules or something like that limiting 1 connection per that port you want on TS somehting to add in firewall rules for linux that must be possiable
-
26-10-2005, 05:05 #7
-= TeamSpeak Fanatic =-
- Join Date
- Nov 2002
- Location
- Germany / Kempen
- Posts
- 1,844
Before TS opens a udp connection, the old one is closed. And what whould you do if two persons share an ip? they use a router, because the live in one house. when it's limited only one can join.
So that won't work.
-
26-10-2005, 15:38 #8
-= TeamSpeak Fanatic =-
- Join Date
- Oct 2004
- Location
- Germany
- Posts
- 1,710
Problem is UDP is a stateless protocol only packages no real connection
Originally Posted by weaklinks
-
26-10-2005, 18:50 #9
-= TeamSpeak User =-
- Join Date
- Aug 2005
- Location
- omaha
- Posts
- 14
Originally Posted by Crow
regardless of what protocal is used TS has to know where to send it's clients "info" as in chats to each other . "info" I.E ip:port # of clients . all he is saying is that if ts had a way to save all connected clients ip's address in a DB file for a few min's "even after you disconnect" regardless of witch port # is being using at the time . as each client gets there own udp port# upon conection and do a "compair address" and not allow say, more then say 5 connection in a 1 or 2 mins time frame from 1 ip , you would kill the spammers join/leave bots as ts would not allow the same client to join more then the 5 times as it would "remember" that client from ip 11.22.33.44:2799 is the same as 11.22.33.44:3739 and so on and disallow any new conections from that ip . 5 is a good # but maybe that # could be edited in a new ts version .ini file to allow more/less connections on your server if need be. this would add to the security of a new version and would be welcomed
Originally Posted by DarkCyrus
-
26-10-2005, 19:31 #10
-= TeamSpeak Fanatic =-
- Join Date
- Oct 2004
- Location
- Germany
- Posts
- 1,710
READ before posting. we didn't talk about a change in the TS software but about using firewalls or routers for the flood protection
-
26-10-2005, 21:41 #11
-= TeamSpeak User =-
- Join Date
- Aug 2005
- Location
- omaha
- Posts
- 14
no shit i did read it ! did you read post #4 ?
youre right crow... maybe this flood-protection could also be a feature-request for ts³
do you read the first post he is asking how to stop it and is looking for a third party app to do so and my post if this was added to a new version it would work
all i am saying is this could be coded in a new version not a third party app "as per this thread topic", and should not be that hard to add , it would be about the same as the spam setting that are all ready in ts but based off the ip not swicthing channels to fast . and would be what is wanted as per the first poster
and to top it off my post is more of a sugestion , one that would work i might add
or even someone could code something like this to work with ts2 but would work better if it was apart of tsLast edited by M&M; 09-11-2005 at 07:33.
-
28-10-2005, 02:43 #12
-= TeamSpeak User =-
- Join Date
- Oct 2005
- Location
- na
- Posts
- 4
hey guy i didnt mean to flar anything up but only to try and find a temp solution but i think the best way to do this is using firewall rules
What I might do is have it where the firewall will alert me when a user usses that port and if I want to add the user I dont know that wont work for dymantic ips
dam
-
09-11-2005, 07:24 #13
-= TeamSpeak User =-
- Join Date
- Aug 2005
- Location
- omaha
- Posts
- 14
it would work till the client resets his connection to get a diferant ip , but the firewall would alert you when it is tryed again with his new ip , as your pc will have 1 ip till it is reset
-
09-11-2005, 11:35 #14Bastian Guest
You could use the timeban feature to ban all connecting clients for a short time. This would stop flooding. Unfortunately the minimum bantime is 1 minute and the banlist can only hold 20 entrys. This would mean that this sort of protection is useless when more than 20 people join in less than 1 minute.
You could remove the bans yourself with a complicated script, but parsing the whole banlist every time would take some time and increase CPU load.
However, it's a feature that would fit into the TS2 PerlMod as it already has an "on join" functionality for its "extended welcome message" feature.
Talk to "ScP" from come2play.org.
-
28-11-2005, 03:06 #15
-= TeamSpeak User =-
- Join Date
- Nov 2005
- Location
- Virginia Beach, VA
- Posts
- 15
Hi guys, hopefully this will work for you as it seems to work well for us:
http://forum.goteamspeak.com/showthread.php?t=27502
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Similar Threads
-
Gibt es ein Anti Flood script?
By MASTER KILLER in forum [TeamSpeak 2] Server SupportReplies: 11Last Post: 09-03-2007, 22:36 -
Brute Force Protection On Login Page
By 33rdSSLite in forum [TeamSpeak 2] General QuestionsReplies: 7Last Post: 13-10-2005, 10:20 -
Possible Flood Bug
By cig_r in forum [TeamSpeak 2] Server SupportReplies: 4Last Post: 26-05-2005, 16:38 -
Virus Protection
By FatAlbert in forum [TeamSpeak 2] Server SupportReplies: 4Last Post: 15-08-2004, 23:09 -
excess flood
By Lcpl Merlin BB in forum [TeamSpeak 2] Server SupportReplies: 2Last Post: 18-03-2004, 11:31


Reply With Quote


