He is using specific packets that cause the world manager to crash, he is sending it through the world manager and the zone servers apparently are affected by this and there shouldn't be much more packets that can cause the same effect. I think that should be enough for now. As for which packets, you got to find it out yourself. :)
Post something useful or don't say anything at all.Originally Posted by Radeyo
Last edited by fiestanerd69; 22-10-13 at 10:41 PM.
@Dragonluck4
[Strike]The packets are sent to Manager and Manager then asks Zone. And because Zone is running thats why it crashes.[/Strike]
Test showed that if no Zones are running then Manager won't crash.
I know that no one will believe you without a proof, but I don't care, as I have proven already that I'm not just talk. Those who really need the fix, will contact me, not right away, but if they don't see any other way.
Also you have to thank Dragonluck4 for providing me enough data to find the problem and the fix for it.
Last edited by NextIdea; 22-10-13 at 10:48 PM.
I fail to see why you wouldn't just post the fix?
More traffic for your own server?
Feel its "spoon feeding"
I don't have my own server, just so you know.
So, you have a fix, and don't own a sever yet aren't willing to help everyone who needs a fix?
Bullshit pls. It would be more believable if you had a server, more traffic for you.
So you don't know me from KDev days then.
Lucky him
No one cares about your KDev rep here. :') Anyone can tell a lie easily.
Don't get me wrong; I love giving people crap. But I think we should move on.
But on a serous note has anyone actually got anything to input on this issue that will actually help? x:
That ... they're not going to "Not release"
I'm aware of that.
And it means, you haven't been there and if you would have then you wouldn't have said it.
And if I had a server then I wouldn't even tell that I have a fix as then I won't give it out at any cost.
Whoever want to see proof send me PM with your Skype name (And do you accept to share your Skype name with others to make Multi conversation) and I'll share desktop to show that it fixes it.
Though I would prefer to show to all non believers at once so I don't have to do it multiple times, [STRIKE]so after 30 mins (16:00 GMT+2) I have some time[/STRIKE] or [STRIKE]after about 3,5 hours (19:00 GMT+2) would be the times[/STRIKE]. [STRIKE](The posting time is 15:27 GMT+2, telling just in case)[/STRIKE]
Last edited by NextIdea; 23-10-13 at 06:56 PM.
Why would people care about the "Proof", and it would be hard to show it fixes it considering the crashes aren't instant.
Lmfao.
That shows that you don't even know how to copy the attacker methods to test it.
It very simple to copy those, just use FiestaShark to see what the attacker sent.
If it's any consolation, I believe you NextIdea.
Try it with Peerblock ?
Common Port Used by the attack 22018 UDP - Recommended Action Block - 20000~65535 (all ports above 20000) ON BOTH UDP and TCP! Noticed due to firewall logs! - By looks of things if they can't get in above 20k they'll try anything below including and not excluding the default port for Remote Desktop connection (3389) Just keeping ya updated!
[UPDATE] To the person who recommended Peer Block i LOVE YOU!! i forgot all about that application! :D
Last edited by Evildarkang; 24-10-13 at 02:47 AM.
Reply With Quote