Nainstalovat Steam
přihlásit se
|
jazyk
简体中文 (Zjednodušená čínština)
繁體中文 (Tradiční čínština)
日本語 (Japonština)
한국어 (Korejština)
ไทย (Thajština)
български (Bulharština)
Dansk (Dánština)
Deutsch (Němčina)
English (Angličtina)
Español-España (Evropská španělština)
Español-Latinoamérica (Latin. španělština)
Ελληνικά (Řečtina)
Français (Francouzština)
Italiano (Italština)
Bahasa Indonesia (Indonéština)
Magyar (Maďarština)
Nederlands (Nizozemština)
Norsk (Norština)
Polski (Polština)
Português (Evropská portugalština)
Português-Brasil (Brazilská portugalština)
Română (Rumunština)
Русский (Ruština)
Suomi (Finština)
Svenska (Švédština)
Türkçe (Turečtina)
Tiếng Việt (Vietnamština)
Українська (Ukrajinština)
Nahlásit problém s překladem
that is a security thing you would need to address on your end. Protecting against an actually DDoS is very difficult. Requires really good infrastructure and even big companies have a challenge with this depending on the scale of the DDoS.
it's not some simple freebie software that works for everyone. Each scenario can utilize a different solution based on need.
You may even get the IP addresses of the users connected to your server at the moment and whitelist them (no requests limits) and allow unknow IPs to only perform few requests/hour.
In this way, who is playing can play without troubles. Who is trying to connect to your server can. Who want to attack you, gets blocked after a little while.
After that, if you have a big server (100+ slots) and you see some weird traffic from one of the players IP, you can ban him from your server, and he will be automatically blocked by your filters.