The Lamplighters League download the last version for ipod

That's obviously a lot different than someone running a larger server, who will most likely only know some of the operators / assistant admins.

I haven't had the pleasure of experiencing a (D)Dos yet, and I don't believe I've been under attack at all other than the 2 suspicious client names I saw in the database - it definitely wasn't anyone I knew that used those names, and whenever we let people have access to the server we give them the password obviously, so they would have eventually had a successful login and I would have been informed of the nickname. The way things are now with TeamSpeak, it doesn't seem like there's a way for me to tell if they're trying to brute force (I haven't found a 'contiguous failed login attempts' value anywhere, if it exists let me know) and only the IP from the last successful login is logged in the database, so the values are 'null' currently my only recourse that i've thought of is to ban the unique ID. I'm hoping that everything above helps clear up where I'm coming from on this and my use case. What do you want to do? If you want to protect your server you can only allow spcial adresses for the Query and if your client has an dynamic ip you can create a VPN or you can use SSH-Tunnel to connect over rinetd and you local interface to your query.That's something I have thought about, i don't really have the server resources to have that many people connect on VPN (trying to keep cost very low)Īs for SSH, It's something that I have done for myself in other situations, but that's just it it was for myself.

The Lamplighters League download the last version for ipod