Author Topic: Did the master server just poop itself or something?  (Read 3547 times)


Stopping a D/DoS attack on a server is like trying to stop a flood of water from the opposite side of the flood source. You can't block a D/DoS from the server because it's like pretending there actually isn't water around you yet no one can get through the flood water.

The only way to stop it is to take down the attacker(s) or get the server host to assist. Neither option is likely.

Stopping a D/DoS attack on a server is like trying to stop a flood of water from the opposite side of the flood source. You can't block a D/DoS from the server because it's like pretending there actually isn't water around you yet no one can get through the flood water.

The only way to stop it is to take down the attacker(s) or get the server host to assist. Neither option is likely.
That's a pretty good way to put it.

Stopping a D/DoS attack on a server is like trying to stop a flood of water from the opposite side of the flood source. You can't block a D/DoS from the server because it's like pretending there actually isn't water around you yet no one can get through the flood water.

The only way to stop it is to take down the attacker(s) or get the server host to assist. Neither option is likely.
And to prevent being flooded in the future put up a dam.

And to prevent being flooded in the future put up a dam.
Putting up a dam around the server still leaves the room flooded and the path to the server impassable.





I'm the one who knew it was a DDoS and only one person blamed me :(

I'm the one who knew it was a DDoS and only one person blamed me :(

are you trying to tell us something

I'm the one who knew it was a DDoS and only one person blamed me :(
What kind of evidence is there for that?

I'm the one who knew it was a DDoS and only one person blamed me :(
It's pretty obvious that it's a DDoS

I still don't understand how you can figure out its a Ddos.

Ben claims to know who did it.