View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006511 | unreal | ircd | public | 2025-05-08 05:21 | 2025-05-08 18:11 |
| Reporter | armyn | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Product Version | 6.1.9.1 | ||||
| Summary | 0006511: Managing Automatic Ban Durations in IRC (Gline...) | ||||
| Description | I noticed that a colleague from IRCop sometimes bans users with the following command: /gline *@2a02:1808:1a9:111:* Dehors ! but forgets to add the ":" before the reason. As a result, the ban duration is set to 'permanent.' He doesn’t correct it. Is there a way to block this, prevent the permanent bans, or make the permanent ban expire after 7 days? Or perhaps in UnrealIRCd, is there a place where I can change the default '0' or 'permanent' to something like '7d' ? | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
|
|
Hi. As you may have noticed, this is a bug tracker, used to bug reports or feature requests and should not be used as a mean to get help/support. The preferred methods to get help, are the following: 1) IRC 2) Forum - https://forums.unrealircd.org/ We suggest using IRC first. Now, to answer your question: The `:` isn't really needed in the ban reason and that wouldn't change the ban time. You can use the set::default-bantime (https://www.unrealircd.org/docs/Set_block#set::default-bantime) to specify something like
set {
default-bantime 7d;
}
Hope this helps and I'm sorry if I sounded harsh at the beginning but some issues (like this one and other already closed) could have been discussed on IRC first. |
|
|
The "default-bantime" has already been set for several years, it's set to 1 day. The default gline is still 'permanent'. If we don't put a colon (:) before the reason and it contains more than two words, it won't work correctly. |
|
|
You can test it: /gline *@11.22.33.44 Dehors ! you'll see this: tkl.TKL_ADD [info] G-Line added: '*@11.22.33.44' [reason: Dehors !] [by: ...] [duration: permanent] However, I don't understand why it doesn't work with this ban reason: /gline *@11.22.33.44 test1 test2 tkl.TKL_ADD [info] G-Line added: '*@11.22.33.44' [reason: test2] [by: ...] [duration: 1s] |
|
|
It seems like it's because the ban reason starts with "de" |
