Unban

I got banned earlier by the server for reconnecting too many times (or too fast). Unban please.

Pretty sure its an IP Ban:

IP: 24.215.13.216
STEAM_0:0:16059906

thats funny

pretty sure the same thing just happened to me.. only i just joined the server and it said kicked for too many connection attemps


thats some bullllllllshit!





edit: i dunno my ip address so somebody would have to go thru the logs..


time of my ban : between 2:10-2:30, i really cant remember the exact time

I was just banned within the past 10-15 minutes too, and I think it happened earlier to sharky as well

IP 173.48.36.94

Easy:
myipaddress.com

yeah....this literally just happened to me.

76.19.120.222

This smells like Stealthy.....

uhh i did too
ip 192.168.10.6
id 31077283
plz help me irish

mad gay yo

got banned again
ip this time too

lol it's going to keep happening until it resets the connection attempts properly. It happend to me last night too.

It's because the ServSecurity update fixed a problem with LUA users using a disconnect exploit to crash servers so ServSecurities rather limited fix was to simply limit the number of connection attempts in a given time frame, which works but overly seems to be too strict. Thus, utterly flawed fixing nothing simply causing more problems.

Pemburuh Itu wrote:

This smells like Stealthy.....

You give him far too much credit, it has nothing to do with him.

: Klown : wrote:

lol it's going to keep happening until it resets the connection attempts properly. It happend to me last night too.

It's because the ServSecurity update fixed a problem with LUA users using a disconnect exploit to crash servers so ServSecurities rather limited fix was to simply limit the number of connection attempts in a given time frame, which works but overly seems to be too strict. Thus, utterly flawed fixing nothing simply causing more problems.

You are wrong on so many levels. 1) Connection attempt spam has been implemented in ServSecurity for a long time, this has nothing to do with the disconnect exploit and has always been a protection measure. 2) The fix to the disconnect exploit is actually just checking against a list of known disconnect messages and if it doesn't match block it, it works quite well. Blocking connection attempts would do nothing to prevent this. 3) The server doesn't auto-update versions, so even if a new version had been released, which it wasn't, it wouldn't have updated to it anyways.

On a better note, things should be fixed now.

I was hoping to have something witty in response to your reply pops, but i couldn't figure one out. On another note, so what was causing the issues in the first place then? * i'm curious * and i didn't mean "auto-update" you guys recently updated your servsecurity addon correct? * if not then i misunderstood something* that's what i meant to say that the issues came from 0.8.3 and weren't really present in previous releases.

Popsicle wrote:

Pemburuh Itu wrote:

This smells like Stealthy.....

You give him far too much credit, it has nothing to do with him.

Fair enough, I don't know shit about these things. I built my own computer but I can hardly grok how it groks. Oog Oog.