Hi,
first of all: Please read some articles, books, FAQs or anything else to get more knowledge about TeamSpeak and especially Linux or you may will get some trouble in the future, because your server is doing things, about you don't know anything.
YOU have to take care about your server and nobody else. Due of that, that you seems like to be interested in hardening your server, I'll help you.
how to configure different port than 22 in fail2ban
All setting files on Linux are located under /etc/<software>/.
In your case, you have to take a look at /etc/fail2ban/ and there you'll find a file called "jail.conf". Just search for "ssh" in this file and change the port to your different one:
[ssh]enabled = trueport = ssh # ssh is default 22; change it to your different port like 2223filter = sshdlogpath = /var/log/auth.logmaxretry = 3
how to give root permissions to another user
I recommend you to add the user to the sudo group:
usermod -g sudo anotherUser
The user "anotherUser" is now able to login or execute everything with root permissions using the command "sudo":
Just tell your SSH settings, that the root user is not allowed to login via SSH (/etc/ssh/sshd_config):
One more question , please help me configure the ipconfig to do not allow any other ddos because idk where to paste these settings to be started automaticly since every vps restart
I'm not sure, but just do a Google research on your "echo" commands. I believe, that you can save the most of them in the "/etc/sysctl.conf" with a little bit different syntax. Do you know more about it, @master_d?
For these iptables firewall rules, I recommend you to install the software "iptables-persistent". By running the command...
/etc/init.d/iptables-persistent save
...or...
/etc/init.d/netfilter-persistent save
...depending on your operating system, it will save the current configured / set firewall rules to make them reboot persistent.
One more thing i've got some type of ddos i don't know if it's the software ddos or what
I believe, if it's a DDoS attack, your server won't respond anymore. Please note, that webinterfaces are sometimes buggy or only show a current snapshot instead of a live graph. You rather should check your CPU loads using the "uptime" command:
$ uptime
19:43:34 up 6 days, 13:10, 1 user, load average: 0,00, 0,02, 0,00