[Jay_]

I was testing for an issue on my server and needed to connect 70 NPCs to trace a bug for debugging purposes.

I successfully connected the first 30 NPCs until a message occurred displaying the following:
"Blocking 127.0.0.1 due to a 'server full' attack (2)"

Log:

Code:

[13:18:16] Incoming connection: 127.0.0.1:52979
[13:18:16] Incoming connection: 127.0.0.1:52980
[...]
[13:18:21] Blocking 127.0.0.1 due to a 'server full' attack (2)

If this is a protection tool against server flood attacks, perhaps an exception could be added for local IP addresses?

Thanks.

[Amit_B]

This have been already reported. I'm wondering how they'll handle it.

[linuxthefish]

Don't connect them all at once, connect maby 10 at a time.

[Jochemd]

Quote:

Originally Posted by linuxthefish Don't connect them all at once, connect maby 10 at a time.

Or 5, because 10 got also blocked for me once

[niCe]

Connecting one NPC each 100ms works too (for unlimited amount of NPCs).

[Meta]

Guys, this has been added in some 0.3b/c version. I never knew a correct delay tho.

[Jochemd]

I bet Kalcor won't tell because bot spammers can make an easy workaround knowing that.

[Norrin]

Quote:

Originally Posted by niCe Connecting one NPC each 100ms works too (for unlimited amount of NPCs).

Tried 2000ms, won't work.

[CodyCummings]

It seems there's some obvious security issues regarding NPC's that haven't been addressed yet, anyone with a prompt and the samp-npc file can fill up the NPC slots as he wishes on any server, to be honest NPC's should only be allowed to connect from the server's local network...

[aleck]

I just put 0.3x on my server , and i saw i have that problem too , any solution for that? only got 14npc.