Post: #21

(05-17-2017 01:11 PM)Coruja Wrote:  56d is compatible with old scripts, of course to jump from an 8 year ago 56b to the latest 56d you can't just update your SphereSvr.exe, there's some root scripts that must be updated too (sphere.ini, sphere_defs.scp, sphere_msgs.scp, spheretables.scp, ...) but in general all triggers/functions/etc still the same

depending how deep is your server customization, this can be an simple copy/paste overwriting all scripts or even an manual work of many weeks, but this is only valid to root scripts. You doesn't have to rewrite all your custom systems, custom items, etc. Unfortunately custom changes made by users on root scripts are not our responsability, so although we always try to keep everything backward compatible, sometimes the user itself made so many custom changes on his code that this will turn into a headache when these scripts must be updated to match the latest official changes

it still worth update these scripts to keep using the latest updates (56d) rather than use an old sphere build (56b), but anyway, you can find some official 56b builds here: https://github.com/Sphereserver/Source/releases
the latest 56b build is from 2013, maybe it could be better than an 56b build from 2009

Hey, thanks for your reaction.
I've read changelogs from github and couldn't find anything related to this issue. Did you fix this in 56d, if yes, can you link me commit hash?

Post: #22

nah, honestly I don't remember too much about this specific issue because there's tons of changes between 56b code from 4~8 years ago (2009/2013) from current 56d code (2017)

but since sphere was being improved and optimized through all these years, 56d is much faster, stable and bugfree compared to 56b

Post: #23

sphere 56d, today

Post: #24

(05-20-2017 09:19 PM)WRWR Wrote:  

Code:

07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.
07:55:WARNING:16:Unknown game packet (0x23) received.

sphere 56d, today

this is not an server-side error, packet 0x23 is only sent by server to client, not from client to server, that's why sphere is telling you that it received an "unknown packet 0x23"

so unfortunately it's not a sphere fault if someone is trying to cheat on your server sending invalid packets to server

but anyway, this doesn't really mean that your server have bugs or errors, it's just a message to make the server admin aware about what the client is trying to do

Post: #25

This problem became very popular in Turkey previously. Some stupid lamers are sending unknown packets to Sphere servers. Few servers shut their services down. This G-Defender guy is one of the software developer for servers in Turkey, he makes connectors for servers, so probably his clients (customers) are having issues and thats why he is here probably. As long as I know from Turkish forums; people say that lamers are renting cheap VDS/VPS servers and sending unknown packets to Sphere servers and after a while server can't effort to carry that much pressure and shuts down itself.

I think we should focus on how to avoid these attackes from Sphere part. It can be with a software update, .ini setting, script or third part protection, I don't know.

I'm very interested on this topic cuz I'm also thinking of building a new server in my freetimes but I'm worried about what if I make it online and get these attacks...

Post: #26

No one knows how these attacks. If it is known how to do it, protection can be improved accordingly

Post: #27

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
PS: on sphere.ini you must always write the PACKETx line using numbers in decimal format (023 hex = 35 dec)

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.

Post: #29

Any way to disable all unknown packets?

Post: #30

@Criminal

maybe he see his job
https://forum.spherecommunity.net/Thread...et-Support