Use this property sheet to apply an attack protection level and general security measures to all users who are members of this user class.
Important With the exception of the Cannot log on option in the Access property sheet, none of the class settings affect sysops or sysop managers. Therefore, even if you set an attack protection level, a defective bot operating as a sysop can accidentally flood a server. It is recommended that you grant sysop or sysop manager access only to bots that require it in order to operate properly.
This property sheet contains the following options.
| Option | Description | |||||||||||||||||||||||||||||||||||
| Attack protection | Regulates the flow of traffic from members of a user class by limiting the frequency with which Chat Service processes data messages, invitations, join messages, messages from the host to the channel, and standard messages (private messages, notices, and whispers). If the service receives one of these messages, it temporarily suspends the user's session. After the delay expires, the service resumes normal message processing. Also, if a user tries to join a channel using the wrong password, the service delays processing subsequent attempts by that user to join the channel. The four levels of attack protection are None (no delay), Low, Medium, and High. As shown in the following table, each level corresponds to a specific delay time (in seconds) according to the type of message the service receives or the type of event that occurs.
The attack protection delay is added to the Message processing delay and the Channel Lag, which you set with the IRCX PROP command. |
|||||||||||||||||||||||||||||||||||
| Maximum IP connections | Designates the maximum number of connections an IP address can open on a chat network. You can set a value from 0 to 1000000. The default setting is 0 (unlimited connections). |
|||||||||||||||||||||||||||||||||||
| Maximum channels | Sets the maximum number of channels that this class permits. You can set a value from 0 to 10. |
|||||||||||||||||||||||||||||||||||
| Input flood limit (bytes) | Designates the amount of unprocessed input data on the service that causes a user to be disconnected. You can set a value from 0 to 4096 bytes. A value of 0 indicates that the service can accept an unlimited amount of data from a client. Caution A value of 0 leaves the server vulnerable to flooding attacks. |
|||||||||||||||||||||||||||||||||||
| Output saturation limit (kilobytes) | Designates the maximum amount of data that the service can buffer for a client before it drops the client connection. You can set a value from 1 to 1024 kilobytes (KB). |
|||||||||||||||||||||||||||||||||||
| Ping delay (seconds) | Sets the time interval between PINGs that the service sends to inactive clients. You can set a value from 15 to 3600 seconds. The default value is 90 seconds. |
|||||||||||||||||||||||||||||||||||
| Message processing delay (seconds) | Delays processing all messages from a class of members. You can set a value from 0 to 10 seconds. |
|||||||||||||||||||||||||||||||||||
| Nickname change delay (seconds) | Designates the number of seconds that must elapse between nickname changes. You can set a value from 0 to 3600 seconds. A value of 3600 prevents all nickname changes. Unlike the other delays in the Settings property sheet, Nickname change delay does not slow the activity of a class member session. If a member tries to change nicknames before the delay has elapsed, the chat server notifies the member that he or she tried to change nicknames too soon. |
|||||||||||||||||||||||||||||||||||
| Enable IP/DNS masking | Prevents Chat Service from showing a user's full IP address or Domain Name System (DNS) host name to other users. However, sysops and sysop managers can see this information at all times so they can ban or grant access to users. Similarly, channel hosts and owners can see the full IP address or DNS host name of users who are members of their channels. |