Difference between revisions of "FloodProtection"
From Chat4AllFAQ
m |
m |
||
| Line 1: | Line 1: | ||
| − | + | == Flood Protection == | |
| − | |||
| − | + | Getting tired off those endless fights against floodbots or annoying users who like to flood your clients so it crashes or hangs ? Now there is a way to fight those users/bots. Even 2 way's [[image:Smile.gif]] Chat4All provides 2 different way's to fight those spam/virus/floodbots. | |
| − | + | We've explained the feature that you can configure below , the other feature [[watcher|Watcher]] is a Chat4All Service and operated by us. | |
| − | |||
| + | #Flood protection | ||
| + | ## *[[watcher|Watcher]] | ||
| + | ## *Serverside flood protection | ||
| − | + | ||
| + | === Serverside Flood protection settings === | ||
Our server supports new channel modes, a brief explaination : | Our server supports new channel modes, a brief explaination : | ||
| − | + | '''K''' : no /knock | |
| − | + | '''N''' : no nickchanges | |
| − | + | '''C''' : no CTCPs | |
| − | + | '''M''' : only regged (+r) users can talk | |
| − | + | '''f''' : flood settings. This is the one we are going to discuss | |
This mode helps you protect your channel against floods, it's much faster and more advanced then any channelbot. | This mode helps you protect your channel against floods, it's much faster and more advanced then any channelbot. | ||
How to use ? | How to use ? | ||
| − | + | /mode #channel +f [action type[#counter action, (more)]:seconds | |
An overview off the different floodtypes: | An overview off the different floodtypes: | ||
| − | + | # '''c''' "CTCPs" --> default action : +C (m,M) | |
| − | + | # '''j''' "joins" --> default action : +i (R) | |
| − | + | # '''k''' "knocks" --> default action : +K | |
| − | + | # '''m''' "messages/notices" --> default action = +m (M) | |
| − | + | # '''n''' "nickchanges" --> default action = +N | |
| − | + | # '''t''' "text" --> default action : kick [[ExtendedBans|b]] | |
Some examples : | Some examples : | ||
| − | ChanOp sets mode: +f | + | ChanOp sets mode: +f [20j,50m,7n]:15 |
Evil1 (~fdsdsfddf@Clk-17B4D84B.blah.net) has joined #test | Evil1 (~fdsdsfddf@Clk-17B4D84B.blah.net) has joined #test | ||
| Line 38: | Line 40: | ||
Evil3 (~toijhlihs@Clk-38D374A3.aol.com) has joined #test | Evil3 (~toijhlihs@Clk-38D374A3.aol.com) has joined #test | ||
Evil4 (~eihjifihi@Clk-5387B42F.dfdfd.blablalba.be) has joined #test | Evil4 (~eihjifihi@Clk-5387B42F.dfdfd.blablalba.be) has joined #test | ||
| − | -- snip XX lines -- | + | -- snip XX lines -- |
Evil21 (~jiovoihew@Clk-48D826C3.e.something.org) has joined #test | Evil21 (~jiovoihew@Clk-48D826C3.e.something.org) has joined #test | ||
| − | -server1.test.net:#test *** Channel joinflood detected (limit is 20 per 15 seconds), putting +i | + | -server1.test.net:#test *** Channel joinflood detected (limit is 20 per 15 seconds), putting +i |
server1.test.net sets mode: +i | server1.test.net sets mode: +i | ||
| − | <Evil2> fsdjfdshfdkjfdkjfdsgdskjgsdjgsdsdfsfdujsflkhsfdl | + | <Evil2> fsdjfdshfdkjfdkjfdsgdskjgsdjgsdsdfsfdujsflkhsfdl |
| − | <Evil12> fsdjfdshfdkjfdkjfdsgdskjgsdjgsdsdfsfdujsflkhsfdl | + | <Evil12> fsdjfdshfdkjfdkjfdsgdskjgsdjgsdsdfsfdujsflkhsfdl |
| − | <Evil15> fsdjfdshfdkjfdkjfdsgdskjgsdjgsdsdfsfdujsflkhsfdl | + | <Evil15> fsdjfdshfdkjfdkjfdsgdskjgsdjgsdsdfsfdujsflkhsfdl |
| − | <Evil10> fsdjfdshfdkjfdkjfdsgdskjgsdjgsdsdfsfdujsflkhsfdl | + | <Evil10> fsdjfdshfdkjfdkjfdsgdskjgsdjgsdsdfsfdujsflkhsfdl |
| − | <Evil8> fsdjfdshfdkjfdkjfdsgdskjgsdjgsdsdfsfdujsflkhsfdl | + | <Evil8> fsdjfdshfdkjfdkjfdsgdskjgsdjgsdsdfsfdujsflkhsfdl |
| − | -- snip XX lines -- | + | -- snip XX lines -- |
| − | -server1.test.net:#test *** Channel msg/noticeflood detected (limit is 50 per 15 seconds), putting +m | + | -server1.test.net:#test *** Channel msg/noticeflood detected (limit is 50 per 15 seconds), putting +m |
server1.test.net sets mode: +m | server1.test.net sets mode: +m | ||
| Line 60: | Line 62: | ||
Evil7 is now known as Hmmm7 | Evil7 is now known as Hmmm7 | ||
Evil8 is now known as Hmmm8 | Evil8 is now known as Hmmm8 | ||
| − | -server1.test.net:#test *** Channel nickflood detected (limit is 7 per 15 seconds), putting +N | + | -server1.test.net:#test *** Channel nickflood detected (limit is 7 per 15 seconds), putting +N |
server1.test.net sets mode: +N | server1.test.net sets mode: +N | ||
If you like to specify other counter action then the default one you have to modify the syntaxis | If you like to specify other counter action then the default one you have to modify the syntaxis | ||
| − | + | eg /mode #channel +f [20j#R,50m#M]15 | |
| − | meaning, after 20 joins in 15 seconds, the channel mode would become +i but now it's becomming +R | + | meaning, after 20 joins in 15 seconds, the channel mode would become +i but now it's becomming +R |
A need feature for the more "forgetting types" is the auto remove: | A need feature for the more "forgetting types" is the auto remove: | ||
| − | + | eg /mode #channel +f [20m#M15]:15 | |
| − | the message flood gets triggerd after 20 messages (off all users) in 15 seconds, channel mode becomes +M for 15 minutes. | + | the message flood gets triggerd after 20 messages (off all users) in 15 seconds, channel mode becomes +M for 15 minutes. |
A last example to get the hang of it : | A last example to get the hang of it : | ||
| − | /mode #channel +f | + | /mode #channel +f [15j#i20,50m#M15,10c#C35,5n#N5,3k#K20]:15 |
* all gets triggerd after 15 seconds! | * all gets triggerd after 15 seconds! | ||
* after 15 joins, channels goes +i and will be unset after 20 minutes | * after 15 joins, channels goes +i and will be unset after 20 minutes | ||
| Line 80: | Line 82: | ||
* 3 /knock commands in a row, +K channelmode , unset after 20 minutes | * 3 /knock commands in a row, +K channelmode , unset after 20 minutes | ||
| − | + | <font color="#FF0000">: Use the flood command wise! If there is no OP (@) in the channel, your channel could be locked for some time!!</font> | |
Hope this will help you protect your channel even more | Hope this will help you protect your channel even more | ||
| − | have a nice chat | + | have a nice chat [[image:Smile.gif]] |
Revision as of 19:23, 3 December 2004
Flood Protection
Getting tired off those endless fights against floodbots or annoying users who like to flood your clients so it crashes or hangs ? Now there is a way to fight those users/bots. Even 2 way's 
Chat4All provides 2 different way's to fight those spam/virus/floodbots.
We've explained the feature that you can configure below , the other feature Watcher is a Chat4All Service and operated by us.
- Flood protection
- *Watcher
- *Serverside flood protection
Serverside Flood protection settings
Our server supports new channel modes, a brief explaination :
K : no /knock N : no nickchanges C : no CTCPs M : only regged (+r) users can talk f : flood settings. This is the one we are going to discuss
This mode helps you protect your channel against floods, it's much faster and more advanced then any channelbot.
How to use ?
/mode #channel +f [action type[#counter action, (more)]:seconds
An overview off the different floodtypes:
- c "CTCPs" --> default action : +C (m,M)
- j "joins" --> default action : +i (R)
- k "knocks" --> default action : +K
- m "messages/notices" --> default action = +m (M)
- n "nickchanges" --> default action = +N
- t "text" --> default action : kick b
Some examples :
ChanOp sets mode: +f [20j,50m,7n]:15
Evil1 (~fdsdsfddf@Clk-17B4D84B.blah.net) has joined #test Evil2 (~jcvibhcih@Clk-3472A942.xx.someispcom) has joined #test Evil3 (~toijhlihs@Clk-38D374A3.aol.com) has joined #test Evil4 (~eihjifihi@Clk-5387B42F.dfdfd.blablalba.be) has joined #test -- snip XX lines -- Evil21 (~jiovoihew@Clk-48D826C3.e.something.org) has joined #test -server1.test.net:#test *** Channel joinflood detected (limit is 20 per 15 seconds), putting +i server1.test.net sets mode: +i
<Evil2> fsdjfdshfdkjfdkjfdsgdskjgsdjgsdsdfsfdujsflkhsfdl <Evil12> fsdjfdshfdkjfdkjfdsgdskjgsdjgsdsdfsfdujsflkhsfdl <Evil15> fsdjfdshfdkjfdkjfdsgdskjgsdjgsdsdfsfdujsflkhsfdl <Evil10> fsdjfdshfdkjfdkjfdsgdskjgsdjgsdsdfsfdujsflkhsfdl <Evil8> fsdjfdshfdkjfdkjfdsgdskjgsdjgsdsdfsfdujsflkhsfdl -- snip XX lines -- -server1.test.net:#test *** Channel msg/noticeflood detected (limit is 50 per 15 seconds), putting +m server1.test.net sets mode: +m
Evil1 is now known as Hmmm1 Evil2 is now known as Hmmm2 Evil3 is now known as Hmmm3 Evil4 is now known as Hmmm4 Evil5 is now known as Hmmm5 Evil6 is now known as Hmmm6 Evil7 is now known as Hmmm7 Evil8 is now known as Hmmm8 -server1.test.net:#test *** Channel nickflood detected (limit is 7 per 15 seconds), putting +N server1.test.net sets mode: +N
If you like to specify other counter action then the default one you have to modify the syntaxis
eg /mode #channel +f [20j#R,50m#M]15
meaning, after 20 joins in 15 seconds, the channel mode would become +i but now it's becomming +R
A need feature for the more "forgetting types" is the auto remove:
eg /mode #channel +f [20m#M15]:15
the message flood gets triggerd after 20 messages (off all users) in 15 seconds, channel mode becomes +M for 15 minutes.
A last example to get the hang of it :
/mode #channel +f [15j#i20,50m#M15,10c#C35,5n#N5,3k#K20]:15
- all gets triggerd after 15 seconds!
- after 15 joins, channels goes +i and will be unset after 20 minutes
- on the count of 50 messages, +M will become a channelmode and will be removed by the server after 15 minutes
- 10 channel ctcp's in 15 seconds, set channelmode +C for 35 minutes
- 5 nickchanges , channelmode +N , unset after 5 minutes
- 3 /knock commands in a row, +K channelmode , unset after 20 minutes
: Use the flood command wise! If there is no OP (@) in the channel, your channel could be locked for some time!!
Hope this will help you protect your channel even more
have a nice chat
