![]() |
|
#61
|
||||
|
Quote:
Would rather block the attack and worry about the culprit later.
__________________
| |||
|
|
||||
|
#63
|
||||
|
Quote:
| |||
|
|
||||
|
#64
|
||||
|
Quote:
Like you said, it is wasted effort to try to go after who is doing it because even in the unlikely event you find and stop them there is another person ready to do it. The best way to stop someone is to make it a waste of their time. | |||
|
|
||||
|
#65
|
|||
|
Willing to bet it isn't even their firepower anyways, nobody cares if they can take off a server for 5 minutes.
__________________
Ingame names:
Skywardfire 36 Magician. Cybrosis 5 Bard. | ||
|
|
|||
|
#66
|
|||
|
I just don't understand why this is causing the entire system to go down. I mean, the actual game server should only accept requests from IP addresses that have been authenticated already, no? So someone spamming a login server or whatever, should have little effect on the active "good" player connections with an established login who are communicating with the game server not the login server. Are the two not separated in such a way? I'm sure there are many limitations placed on the system due to the client, perhaps that is big hangup in finding a good solution to this? Please edumucate muh as I am not network savvy.
| ||
|
|
|||
|
#67
|
||||
|
Quote:
| |||
|
|
||||
|
#68
|
||||
|
Quote:
But thanks for your zero cents. | |||
|
|
||||
|
#69
|
|||
|
Just an update -
Made some changes today. We'll see if they help, and if not we have one more change we're holding in reserve that should definitely stop it (The data center wants me to exhaust all other avenues before implementing it). To answer questions - We're way past the point of understanding the attack. We know exactly what type of attack it is and the possible solutions. Just working on getting things implemented.
__________________
| ||
|
|
|||
|
#70
|
|||||
|
Quote:
Quote:
| ||||
|
|
|||||
![]() |
|
|