View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003878 | unreal | ircd | public | 2009-11-15 19:58 | 2009-11-16 10:41 |
| Reporter | Fn | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | N/A |
| Status | closed | Resolution | no change required | ||
| Summary | 0003878: Flood | ||||
| Description | One thing to add, is when a user floods, they are killed. And when a user joins/parts flood for example 4 joins and parts in one channel, they are killed. | ||||
| 3rd party modules | |||||
|
|
There's a difference between channel management and server management. If a channel wants to protect themselves against join part floods, there are a variety of options such as +j and +f. In fact, +j is pretty effective, and can be set quite tight. A small join part flood can be annoying, but is no threat to the server, nor to most users, and therefore there's no reason to kill the user (let alone, ban the user, as that would surely be the next feature request). If you want to prevent join part floods on all channels, then you can force +j on all channels and/or set it in the default channel modes. As for general floods, these can be a threat, to both the server and users, and therefore something called 'excess flood' was invented... you can tweak this in class::recvq, see the docs for more information. This too is highly effective, but should be treated with care and tweaked - it really depends on the network - as to not cause too many false positives (innocent users being killed). Of course, if you or others feel otherwise, feel free to make a module to do this. That said, I suggest using +j (and +f as a backup), and tightening class:recvq, this should really help. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2009-11-15 19:58 | Fn | New Issue | |
| 2009-11-16 10:40 | syzop | QA | => Not touched yet by developer |
| 2009-11-16 10:40 | syzop | U4: Need for upstream patch | => No need for upstream InspIRCd patch |
| 2009-11-16 10:40 | syzop | Note Added: 0015957 | |
| 2009-11-16 10:40 | syzop | Status | new => closed |
| 2009-11-16 10:41 | syzop | Resolution | open => no change required |
