It seems to be due to "spambot" or script kiddies trying to connect the server (port scan or whatever), causing the sockets available to fill up rapidly, and probably causing other problems, as the server is/was not programmed to handle datas that are not the usual protocol.
This is not a server issue per se, having a stronger server will only delay the appearance of the bug.
So I'm currently working on spambot protections.
Yesterday, another attacking occurring, proving that the FA server is now relatively safe.
I'm now working on the lobby server.
This can result in some issues while trying to connect.
This can happen :
- When you launch the lobby, it connect to the server and ask for a session id. If the request is not done within 3 seconds after opening the socket, you are kicked out. I will lower that value later if it work correctly.
- When you login, the server will send you "pings" request more regularly than usual (from 60 seconds to 5 seconds).
If you "miss" two pings during that time, you are kicked out.
This is actually to avoid people hammering the server when it's under attack : The server is unable to get all requests, so you automatically miss the ping the socket is closed rapidly.
You may have noticed that : you see the "logging in" screen for minutes.. During that time, the server is trying to keep up with all the previous requests, and yours, even if you disconnect in-between. Each attempt will make that request list longer, making the server unable to catch up with "real time".
This is reverted to 60 seconds after the login.
I'm currently not banning IP that fails the test, but it will come at some point if it works as planned.
If you have trouble connecting and feel that's the protections are the cause, please open a thread in the tech forum. (don't forget the logs !!!!)Statistics: Posted by Ze_PilOt — 31 Dec 2012, 17:05
]]>