NPCs and server-full attack - Printable Version
+- SA-MP Forums Archive (https://sampforum.blast.hk)
+-- Forum: SA-MP Scripting and Plugins (https://sampforum.blast.hk/forumdisplay.php?fid=8)
+--- Forum: Scripting Help (https://sampforum.blast.hk/forumdisplay.php?fid=12)
+--- Thread: NPCs and server-full attack (/showthread.php?tid=406147)
+- SA-MP Forums Archive (https://sampforum.blast.hk)
+-- Forum: SA-MP Scripting and Plugins (https://sampforum.blast.hk/forumdisplay.php?fid=8)
+--- Forum: Scripting Help (https://sampforum.blast.hk/forumdisplay.php?fid=12)
+--- Thread: NPCs and server-full attack (/showthread.php?tid=406147)
NPCs and server-full attack - Lorenc_ - 09.01.2013
Well, if you have more than 20 NPCs (loaded on a loop), the server-full attack exploit is triggered thus blocking any other NPCs to connect.
Код:
[05:21:50] Incoming connection: -.-.-.-:37566 [05:21:50] Incoming connection: -.-.-.-:42697 [05:21:50] Incoming connection: -.-.-.-:50772 [05:21:50] Incoming connection: -.-.-.-:33405 [05:21:50] Incoming connection: -.-.-.-:45887 [05:21:50] Incoming connection: -.-.-.-:40798 [05:21:50] Incoming connection: -.-.-.-:54447 [05:21:50] Incoming connection: -.-.-.-:45088 [05:21:50] Incoming connection: -.-.-.-:39333 [05:21:50] Incoming connection: -.-.-.-:50857 [05:21:50] Incoming connection: -.-.-.-:46957 [05:21:50] Incoming connection: -.-.-.-:60395 [05:21:50] Incoming connection: -.-.-.-:37534 [05:21:50] Incoming connection: -.-.-.-:46989 [05:21:50] Incoming connection: -.-.-.-:59955 [05:21:50] Incoming connection: -.-.-.-:41165 [05:21:50] Incoming connection: -.-.-.-:40973 [05:21:50] Incoming connection: -.-.-.-:57679 [05:21:50] Incoming connection: -.-.-.-:55693 [05:21:50] Incoming connection: -.-.-.-:59440 [05:21:50] Incoming connection: -.-.-.-:37537 [05:21:50] Incoming connection: -.-.-.-:34565 [05:21:50] Incoming connection: -.-.-.-:33032 [05:21:50] Incoming connection: -.-.-.-:43883 [05:21:50] Incoming connection: -.-.-.-:54203 [05:21:50] Incoming connection: -.-.-.-:59623 [05:21:50] Incoming connection: -.-.-.-:35207 [05:21:50] Incoming connection: -.-.-.-:48082 [05:21:50] Incoming connection: -.-.-.-:49679 [05:21:50] Incoming connection: -.-.-.-:56304 [05:21:50] Incoming connection: -.-.-.-:53305 [05:21:50] Blocking -.-.-.- due to a 'server full' attack (1)
Re: NPCs and server-full attack - JernejL - 09.01.2013
you need to connect npcs slowly. it works same as any other connection.
Re: NPCs and server-full attack - Lorenc_ - 09.01.2013
Yeah I do that, but it would be great if this really did require no timers at all.
Re: NPCs and server-full attack - rbN. - 10.01.2013
Bump.
Would be best if this was fixed in a certain way.
Re: NPCs and server-full attack - wups - 10.01.2013
Agree, this bug is kind of annoying, because people start connecting to the server while the bots are still not connected, and the IDs get kind of messed up.
AW: NPCs and server-full attack - BloodyEric - 10.01.2013
Yeah we suffer from this problem too. Would be nice if we could connect bots faster.
Re: NPCs and server-full attack - Hiddos - 10.01.2013
I can confirm this as well, annoying bug
Re: NPCs and server-full attack - Babul - 10.01.2013
®NPCs tend to crash/quit aswell quite often, thats why i didnt see another solution than a timer for connecting them, then another 10sec timer to check if all bots are still connected.
and i agree, the connect-spam-block issue is still persistent - is it possible to allow or whitelist a certain IPrange?
Re: NPCs and server-full attack - Lightning[SV] - 10.01.2013
The only solution is to use a timer.
Whitelisting localhost would allow a spoofed source attack because sa-mp uses udp.
All the server full attacks we have had involved spoofed source addresses which got around the built in filter anyway.
Re: NPCs and server-full attack - MP2 - 22.01.2013
Quote:
|
Originally Posted by Babul
 ®NPCs tend to crash/quit aswell quite often, thats why i didnt see another solution than a timer for connecting them, then another 10sec timer to check if all bots are still connected.
and i agree, the connect-spam-block issue is still persistent - is it possible to allow or whitelist a certain IPrange? |