flooding connection requests

[ashwinharry]

I seem to be getting this message a lot from quite a few of my users
  [FI]

• [Security] [CT] [2] [Kick] <PROTOTYPE™> IP: 10.22.28.193 / Reason: Flooding connection requests.

is there anything I can do about it

[LadyStardust]

You can adjust hub settings in !set Security CT section.

[Security] [CT]

type: !set security ct in main chat to check your settings.

All categories in security section work the same and have the same basic options:

Length limits:
.._maxlength    Maximum length of the message
.._minlength    Minimum length of the message
.._length_action    Action to take when message is too short or too long

Anti flood settings:
For most categories there are 2 different limits: 1 and 2, each with their own independent settings.
The first limit is normally used to ignore more messages, or notify or warn a user about sending too many of these messages.
The second limit is normally used for a more severe action: kick or ban the user because it's most likely the user is intentionally flooding the hub.

.._usermax1 <number>    When this number of messages is sent in...
.._usertime1 <seconds>   ...this many seconds...
.._useraction1 <action>   ...this action will be performed.

.._usermax1 <number>    When this number of messages is sent in...
.._usertime1 <time>    ...this many seconds...
.._useraction1 <action>   ...this action will be performed.

For actions you can choose the following: Ignore, Notify, Warn, Mute, Disconnect, Kick, Ban, Redirect, NotifyOpchat, LockMain

[sergius_s]

One of my user has a share of 62TB, natural that many users find it in the share what they are looking and many search requests goes to him. My bot constantly kick him because "Flooding connection requests".
My hub has 300-350 users.

Question: That's right i did when i did the setting !set ct_usermax2 400 or no? This does not greatly affect the security hub?

[en_dator]

most of those settings can be increased a lot, most of them limits the amount of traffic that the hub will allow, so as long as your hub does not lag or exhaust the available bandwidth you can try and increase until the warnings go away.

The other option you have is to move this user to a special user profile and let him bypass the protection (with override <profile> securityct ). Then it just affects that user and not the whole hub.

[sergius_s]

G'evening 
Thank you en_dator. Indeed, after increasing this parameter the problem disappeared and warnings stopped. And it did not affect on the job hub
Btw, the idea of ​​creating a special profile is also good