Post: #28

(05-25-2017 05:36 PM)Coruja Wrote:  probably you're getting an DoS or DDoS attack. Unfortunately there's too many lammers on all servers around the world, and these kind of ppl like to waste their time just to bring servers down for no reason. Instead go study, get a job, get a hobby, go out with the family, etc, they think that "success in life" is stay 24h/day behind an PC cheating games, so they thing that they will reach success at each new bug found, new server taken down, new victim hijacked, etc

basically it's an criminal way of think, always trying to do everything to harm ppl just because they like to harm ppl. Because that's what they are: criminals. DDoS and scam is a crime on most (or maybe every) country of the world

so to make your server safe, the 1st rule is never trust on your clients. Of course most of the players can be trusted, but you must always build everything on the server thinking about protection, because there will be always a lammer trying to exploit everything and everyone

2nd rule is get an anti-DDoS plan. Best option is host your server on an datacenter with local anti-DDoS, but you can also use an paid external anti-DDoS service for traffic tunneling (since all your traffic will pass through this external anti-DDoS server, it must be located on the same country of your base server to prevent high pings). You can also find some datacenters that offer basic/average anti-DDoS protection for free, like OVH which have servers on central europe with local DDoS mitigation

3rd rule is reduce the attack surface. Block all IP port range on your server, and only allow connection on specific ports that you use it

and finally, if everything fail and lame connections still reach your sphere, you can also make some basic changes to reduce the resources usage (CPU/HD). Just create an empty packet filter to block this packet 0x23 without let it write the error on the console. The server will stay under attack but without write 99999999999 errors on the console, and this will reduce CPU/HD usage. To create a packet filter for packet 0x23 just add "PACKET35=f_packet_023_protection" on sphere.ini then add this empty function on any script

Code:

[FUNCTION f_packet_023_protection]
return 1

PS: on sphere.ini you must always write the PACKETx line using numbers in decimal format (023 hex = 35 dec)

Very nice and satisfying answer, thank you so much. I hope server owners try these solutions so we can get feedbacks if it works or not and we can find new ways to resolve it or maybe your trick is going to work. I think this is one of the biggies issues we're facing these days.