View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001126 | unreal | ircd | public | 2003-07-18 01:23 | 2003-11-20 19:43 |
| Reporter | kuwatog | Assigned To | syzop | ||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | open | ||
| Summary | 0001126: Notice Flood | ||||
| Description | I wish you can program a protection against NOTICE flooders. P.S.fyi, 0001094 was solved by CVS dated July 10. Sorry for not giving feedback soon enough. | ||||
| 3rd party modules | |||||
|
|
what kind of notice floods? (many-to-1, 1-to-many, 1-to-chan, etc.. you are a bit unclear :p). |
|
|
my current problem is 1-to-many. But may I suggest that the fix cover all possible scenarios. If that is not possible at the moment, then I wish 1-to many notice flood can be addressed. |
|
|
Hi; My server users are make very very notice flood.How is only ircops make notice command?Where is the code notice permission for users ? sorry for my english :) good luck |
|
|
Hm for 1 client -> many clients we have a target limit, but I guess that's not working correctly then or not strict enough. |
|
|
is "target limit" an option I can enable in unrealircd.conf? Can you please point me to a text explaining this feature? |
|
|
Currently it's a hardcoded limit which may be modified at compiletime, you can find it in config.h (MAXTARGETS and TARGET_DELAY). |
|
|
just disable the damn thing in m_message.c So far i've sorted nick floods, join/part floods, excessive repeats, part message. :\ and may i add it was bloody hard work. |
|
|
can you give some more detailed info? The default target delay is 20, and I just tested it and it works quite well. It's a bit weird formula, but if you message/notice >20 people it lags you up a lot. [01:37:32] -> -k000-zu,k001-rc,k002-mu,k003-qr,k004-iu,k005-fq- test [01:37:32] -> -k006-dr,k007-ws,k008-dz,k009-gb,k010-oy- test [01:37:36] -> -k011-rl,k012-dc,k013-wv,k014-rf,k015-ae,k016-gq- test [01:37:36] -> -k017-nt,k018-ku,k019-od,k020-ut- test *wait a while just for fun* [01:37:42] -> -k021-mv,k022-qz,k023-bk,k024-ot,k025-th,k026-uc- test [01:37:42] -> -k027-ek,k028-ix,k029-fd- test k021-mv Message target change too fast. Please wait 135424000 seconds k022-qz Message target change too fast. Please wait 135424008 seconds k023-bk Message target change too fast. Please wait 135424016 seconds k024-ot Message target change too fast. Please wait 135424024 seconds (that ........ seconds thing is a bug btw, but you get a lot of lag :p). Not saying there are no bugs, but when I test it a bit here it seems to work quite well. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2003-07-18 01:23 | kuwatog | New Issue | |
| 2003-07-18 03:21 | syzop | Note Added: 0003263 | |
| 2003-07-18 04:45 | kuwatog | Note Added: 0003264 | |
| 2003-07-18 10:27 | kemal | Note Added: 0003268 | |
| 2003-07-18 13:31 | syzop | Note Added: 0003269 | |
| 2003-07-18 13:40 | kuwatog | Note Added: 0003270 | |
| 2003-07-18 14:38 | AngryWolf | Note Added: 0003273 | |
| 2003-07-25 04:06 | Mumin | Note Added: 0003332 | |
| 2003-08-16 23:48 | syzop | Note Added: 0003486 | |
| 2003-08-27 00:59 | syzop | Status | new => resolved |
| 2003-08-27 00:59 | syzop | Assigned To | => syzop |
| 2003-11-20 19:43 | syzop | Status | resolved => closed |
