View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002378 | unreal | ircd | public | 2005-02-28 08:18 | 2007-04-27 06:42 |
| Reporter | arbiter | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | wont fix | ||
| Summary | 0002378: another parameter in stats G | ||||
| Description | we normaly check gline/zline with /stats G , but we do not know how many users are affected by that Gline/Zline , I think it would be better to see another parameter like "time of affect" in stats G. now it's like this: G *@200.87.203.6 21438 162 <[email protected]> <reason> we don't know how many users are affected by this ban , if we have another param before <nick!user@host> that shows number of affection we get more info about that ban , and we see if it affects larg numbers of users or it's useless ban. we can do such a thing for shun/gline/zline . | ||||
| 3rd party modules | |||||
|
|
you mean.. a number to show how many users are banned from a specific hostname / ip? |
|
|
exactly |
|
|
If a user is banned... is not allowed in. How can u know the number of users? |
|
|
a user must connect to the network to get ban , isn't it? then it's possible to count them . |
|
|
ok. Then if you are attacked by 1000 bots and you G-line a 2-3 B-Classes to ban them.. then the ircd will count the reconnects... how many memory/cpu you thing it will "eat"? i think it will crash the machine at all. |
|
|
no at all , it's just need a counter for each ban , not so much cpu/memory consuming that you mean , and it does nothing with attacks/clones , ban will affect them , and new codes will just count them like lusers . |
|
|
It isn't as simple as that. Not only do you need to count them for your server, but you need to count them for all the servers, which means more bandwidth will be used by having the servers send thousands of gline counter messages broadcasted to the whole network. I don't see a use for this at all. What difference does it make if your server denied connections from 1 or 1000 people becuase of a gline? If you think you can use the "counter" to see when the gline should be removed, you should be using timed glines instead of permanent ones. Also, use services: If they gline someone, they usually remove the gline in a small amount of time so you can see how many times it has been re-added. |
|
|
Bugz has a point there, for global bans this is either impossible, unfeasable or inaccurate. Another point: if a few people reconnect all the time your counter will be at like '200', but that might mean just 3 unique ips reconnecting all the time. It could also be '200' when it are like 150 unique ips.. In short: it will not tell you "how many *users*" got rejected, rather.. the # of times the *line rejected something. I wonder if it's really useful hmmm. |
|
|
Lets also not forget the 32bit limitation here. During an attack, servers might receive thousands of connect requests each minute. Within a few hours, there could be millions. Give it a few days and you're sure to reach the ~4.3 billion mark that a 32bit integer can hold. I know of some Unreal servers that have been running for months straight. I'm sure the counters would reset to 0 many times if they are networks that are frequently attacked by proxies/botnets/etc. In which case, it doesn't even give you an accurate count of how many bans have been issued. It might read 5 but really it means 4294967300. |
|
|
it might be helpfull for just small amount of users not all, espcialy on small networks , with no attack! with all of these reasons (wasting bw, 32bit Limitation , wrong result) this parameter is not reasonable now. thanks (: |
|
|
what about to add anotther parameter in stats G , I mean something else , for example we are looking for a gline that ends with .net , we have to check all /stats G ... if we could do /stats G *@*.net <server> it was great. and about affected users , is it possible to count baned users on local servers only (no BW wasting) and counting baned session every 1 min (or some period of time) to show more accurate number. and about limitation, reset is not bad , it shows it reaches that big number. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2005-02-28 08:18 | arbiter | New Issue | |
| 2005-02-28 08:24 | vonitsanet | Note Added: 0009349 | |
| 2005-02-28 08:28 | arbiter | Note Added: 0009350 | |
| 2005-02-28 08:33 | vonitsanet | Note Added: 0009351 | |
| 2005-02-28 08:38 | arbiter | Note Added: 0009352 | |
| 2005-02-28 08:40 | arbiter | Note Edited: 0009352 | |
| 2005-02-28 08:43 | vonitsanet | Note Added: 0009353 | |
| 2005-02-28 08:48 | arbiter | Note Added: 0009354 | |
| 2005-02-28 08:50 | arbiter | Note Edited: 0009354 | |
| 2005-02-28 12:50 | Stealth | Note Added: 0009361 | |
| 2005-02-28 14:53 | syzop | Note Added: 0009364 | |
| 2005-02-28 16:18 |
|
Note Added: 0009370 | |
| 2005-03-01 04:16 | arbiter | Note Added: 0009374 | |
| 2005-03-04 13:22 | arbiter | Note Added: 0009400 | |
| 2007-04-27 06:42 |
|
Status | new => closed |
| 2007-04-27 06:42 |
|
Resolution | open => wont fix |
