I would use firewall rules for assistance.
What/Who exactly does use your ts3server? just ts3client or some teamViewer, customMade scripts?
perhaps some client have terrible connectivity.
My suggestion is to isolate the source of your problem or perhaps see in firewall rules stats what portion of IP range is actually 'flooding'. (hopefully its not attack I think it might be, cuz it would explain the whole situation... DEV's?)
Code:
iptables -N testRanges
iptables -A testRanges -s 10.0.0.0/8 -j RETURN
iptables -A testRanges -s 172.16.0.0/12 -j RETURN
iptables -A testRanges -s 192.168.0.0/16 -j RETURN
iptables -A testRanges -s 169.254.0.0/16 -j RETURN
iptables -A testRanges -s 0.0.0.0/3 -j RETURN
iptables -A testRanges -s 32.0.0.0/3 -j RETURN
iptables -A testRanges -s 64.0.0.0/3 -j RETURN
iptables -A testRanges -s 96.0.0.0/3 -j RETURN
iptables -A testRanges -s 128.0.0.0/3 -j RETURN
iptables -A testRanges -s 160.0.0.0/3 -j RETURN
iptables -A testRanges -s 192.0.0.0/3 -j RETURN
iptables -A testRanges -s 224.0.0.0/3 -j RETURN
then add this chain before the accepting rule for your teamspeak3 in your firewall.
example: iptables -I INPUT -p udp --dport 9987 -j testRanges #if that is not good enough, tell me.
to view amounts of packets and data that matched the rule(the range of IPs in the rule) use my normal way of looking into firewall:
Code:
iptables -nvL testRanges
or to have it filed in separate console:
Code:
while true; do iptables -nvL testRanges >> testRanges_`date +%F_%H%M`; sleep 120; done
to stop saving to file each 2min, hit CTRL+C.
I am did not look into rrdtool, to make even graphs from it on the fly, sry.
I am not suggesting you to then ban the source of the problem, which might help you, but not someone else using this SW, with same problems.
But later on, we could, select just that single source and log every traffic from it. send it to devs or study it, etc....
(We)You can then fine tune the source location.
I will post that part, if (we)you can isolate the source of the issue.
#subscribed few days ago
Reply With Quote
