[Sew_Sumi]

Quote:

Originally Posted by Dairyll Read how I used OT again, I wasn't referring to the whole thread before I said OT. Lmao.

I was referring to your post you ignorant idiot... How you used it was incorrect.

Quote:

Originally Posted by Dairyll Me being "whinger"? I've been stating facts and fact-supported opinions on my previous posts. Stop trying to be a white knight for the devs, boy.

You're whinging over a previously unconfirmable exploit... Nothing "White knight" about it.

Quote:

Originally Posted by Dairyll Anyways, blocking the IP's won't fix anything. As I've said on the previous posts, they're spoofing IP's. Read up on spoofing. Legitimate players who are trying to connect to a server that's being attacked will also have their IP's recorded. Right now, there's no way of telling what is real and what isn't on this exploit.

I know that the blocking of IPs won't work on spoofed connections, but making a script that counts the connection overflow as an exploit, and shuts that IP down, as shown in that post that you linked, will cut out what attacks it can complete.

Now, as for "Legit players" being caught in the attacks "logs" is wrong... They won't cause the overflow because of the fact that they, aren't connecting thousands of times over, simply port flooding like a bitch.



Anyways kid, Sit the fuck back down... You wanna call me "boy", then I'll call you kid. Everything I've stated is my contribution, Even though I don't have any attacks or logs, it was pretty plain to see in the first reports of it that it resembled a port flood, doesn't take 10 seconds to add to that that it's possibly masqueraded (Either via the fact that the attacker uses botnets to do it, or through true masquerading), and after that, blocking the IPs, doesn't actually seem to be such a problem.

Anyone on those IPs should be told via the script to check their computer for viruses if those IPs connect. Fact is that to even counter this, being that many are on dynamic IPs and such, having a timeout for each block of the attack on that IP, with a re-check, and maybe have a week of unbanning it and re-banning if it starts attacking. 7 "hits" means perm-blocked.

Even go as far to run the server, adding all of those IPs to a list, checking for duplicates and removing the duplicates to get a more broad idea on how many IPs this thing is pumping out.


If you can't actually take heed of the advice shown in these posts, and even the post you yourself quoted, to test and advise the outcomes of those tests, then you, need to sort yourself out.

Really, DDoS protection should almost cover this attack by it's nature... Can't see why it can't be fixed via the DDoS protection everyone is paying for.