++HOW TO MAKE A SAFER SERVER++
Disclaimer: WARNING! Any modification to the system registry can cause system instability and can destroy your OS!!! I cannot be held responsible for any damage caused to your machine as a result of following the instructions in this document!!! Do it at your own risk!!! If you aren't sure exactly what to do, STOP and don't try! This procedure should be done only if you really know what you are doing!!!!
- What is this for?
I noticed that Skillet uses an attack to kill the server. The first time, I thought he killed the server through the DEV sequence... I made a daemon program that took over any key typed and checked it with the dev sequence. It was successful with version 1.1, there I knew the dev sequence. Not same for 1.2. So I started working to other scripts. Then, monitoring packets, I saw that the attack that Skillet made were not real DOS attacks, neither Syn attacks, due to timing. His attacks are continuos logins until the server crashes. But.... timings of connections must be slightly slow not to be considered syn or dos... say 7-8 per second. By default windows keeps connections open for 3 seconds, so it means 24 contemporary connections... The server is old... so it dies. The key TcpInitialRtt defined in each adapter, can modify this value. Putting 1 in it we will "drop" open connections in 1 second. Now the server handles this volume.... it could be critical sometimes if lots of players are logged in, but I think it is a nice block to Skillet attacks.
- Now how you do it (WINDOWS: XP any sp, 2003)
Goto START -> RUN and type REGEDIT then ENTER.
Locate the following:
HKEY_LOCAL_MACHINE -> SYSTEM -> ControlSet001 -> Services -> Tcpip -> Parameters -> Interfaces
For EVERY interface listed (it is a folder on the file tree at the left), do the following:
Left click on the folder in the left. Now go in the right side and RIGHT CLICK. A menu appears, select:
New -> DWORD value
Type in it:
Then double-click the new voice added and insert the value -> 1
Hit enter. Close everything, reboot your computer, and you're done.