[ikey07]

I talk about this kind of attacks:

Code:

[00:16:38] (1) Invalid client connecting from 88.212.*.*
[00:16:38] [join] sil_ioiJwzhxP has joined the server (21:95.132.2.49)
[00:16:38] [join] sil_HRoN4bXF9 has joined the server (21:95.132.2.49)
[00:16:38] [join] sil_K27uG6PVn has joined the server (21:95.132.2.49)
[00:16:39] [join] sil_ImiEpYls1 has joined the server (21:95.132.2.49)
[00:16:39] [join] sil_mNbAvEAsU has joined the server (21:95.132.2.49)
[00:16:39] [join] sil_Z7e0WkcdQ has joined the server (21:95.132.2.49)
[00:16:39] [join] sil_JFPfi7UCI has joined the server (21:95.132.2.49)
[00:16:39] [join] sil_yVHCVp63A has joined the server (21:95.132.2.49)
[00:16:39] [join] sil_ITj64pLXD has joined the server (21:95.132.2.49)
[00:16:39] [join] sil_bBgqsZaGC has joined the server (21:95.132.2.49)
[00:16:39] [join] sil_aR9iEVNNd has joined the server (21:95.132.2.49)
[00:16:40] [join] sil_5jlU3yUI1 has joined the server (21:95.132.2.49)
[00:16:40] [join] sil_UPXXB9bhs has joined the server (21:95.132.2.49)
[00:16:40] [join] sil_R777BZ48z has joined the server (21:95.132.2.49)
[00:16:40] [join] sil_PpcnQbnwk has joined the server (21:95.132.2.49)

Since SAMP server detects such things, give us a callback which is being called whenever something isn't right.
Make a seperate config stat in server.cfg which let us set how many players can join from the same IP and so on.

Its obvious that one player can't connect to server twice without being disconnected.

Ofcourse I can use some server log reader script etc, but why I should use it, if samp server itself register such things, just doesn't share, what I wish is a full control over incomming connections, even if they are just initalizing.


Still, thank you about what is done so far , just wish such things would be finished, not left in the server log only, there was that plugin with callback which being called about print() to server log, add it by default, I could live with current features, just increase security.


Im sorry if I feel like a noob , but from what I know how these things works, it should be quick job, thank you.

[Twizted]

"set how many players can join from the same IP"

https://sampforum.blast.hk/showthread.php?tid=321533

[ikey07]

Such attacks doesn't even gets to OnPlayerConnect(playerid)

[Si|ent]

Quote:

whenever something isn't right

That's nice and specific...

Quote:

Its obvious that one player can't connect to server twice without being disconnected.

Note that each nick is different. You suggest blocking connections from the same IP? Many players share network connections and play SA-MP together.

'attacks' like the one you show above are quite easy to block/prevent/counter. Check the scripting sections of the forum

[ikey07]

I suggest to add a stat in server settings, which let to set amount of connections, or just limit how many connections per second 1 IP can do.


and

Invalid client connecting from ..
Modified packet
Invalid dialog
Kicking **** because they didn't logon to the game.


would be these isn't right things, but will try to make some custom script for these things, thanks anyways, didn't expected to be answered at all

[Isolated]

Such a weird and uncalled for title. Most attacks can be prevented server-side, from YOUR coding.

[justsomeguy]

Yes because making a multiplayer game DDoS resistant is sooooooo easy!
Find a host that provides DDoS protection.

[LeGGGeNNdA]

Get a host that provides you DDoS protection or make a script about that, there are many tutorials in this forum + *******.

[ikey07]

I got ddos protection, just that it kicks in at high traffic, these small ones just passes by, and any of you have such serverwise script? mind share, as it could be useful for me.

[Mauzen]

As I already said before, samp is not meant to be a firewall. Spamming attacks are not limited to samp, but are a thing that every network server has to face. So why should every single one of them integrate its own firewall? That features you are yelling for can simply be done with firewall software, in a much more complete and efficient way than samp could ever reach. So why should the devs waste their time with that? Just because some guys are too lazy/unable to set it up themselves?

[ikey07]

Quote:

Originally Posted by Mauzen As I already said before, samp is not meant to be a firewall. Spamming attacks are not limited to samp, but are a thing that every network server has to face. So why should every single one of them integrate its own firewall? That features you are yelling for can simply be done with firewall software, in a much more complete and efficient way than samp could ever reach. So why should the devs waste their time with that? Just because some guys are too lazy/unable to set it up themselves?

Im just saying that once those messages appears in the server log:

Invalid client connecting from ..
Modified packet
Invalid dialog
Kicking **** because they didn't logon to the game.

Would be useful to have some notification callback.

[Mark™]

This is nothing more than a bot attack which can be prevented, if you use maxIPs filterscript from sa-mp server package and set the connection limit per IP to 1 or the number of your choice. If you wish to know more of about this, pm me.

[iZN]

This thing is possible to prevent with scripting. My server once got attacked by 20 bots, they all get kicked instantly.

[Gryphus One]

While that kind of attack can be prevented by script, I agree with the author on having a callback whenever a system message is printed to the console. Yeah, I know ****** made a plugin for that, but as far as I know it had the problem of not printing to server_log.txt

[Memoryz]

Quote:

Originally Posted by Mauzen As I already said before, samp is not meant to be a firewall. Spamming attacks are not limited to samp, but are a thing that every network server has to face. So why should every single one of them integrate its own firewall? That features you are yelling for can simply be done with firewall software, in a much more complete and efficient way than samp could ever reach. So why should the devs waste their time with that? Just because some guys are too lazy/unable to set it up themselves?

How would you detect this through a firewall without flagging innocent players connection? Could you share some wisdom?