View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001349 | unreal | ircd | public | 2003-11-08 12:27 | 2003-11-08 18:54 |
| Reporter | medice | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | open | ||
| Product Version | 3.2-beta18 | ||||
| Summary | 0001349: why is embedding ip-ranges in allow-block in "aa.bb.cc.dd/XX"-format not supported? | ||||
| Description | I've gone through the bug-tracker but didn't find any matching issue - so i hope this is no repeating of anything known/wanted and so on... Allright: along the manual you may only include IP-Ranges inserting * as wildcard which works fine with really Class A networks (or B/C) for example 192.168.0.0-192.168.255.255 which can be set as "192.168.*" but not all ranges of Providers are established in clear Class A / B / C nets. for example a range of 192.168.160.0 - 192.168.191.255 is much more complicated and needs several allow-blocks - but in fact you would only need one block "192.168.160.0/19" i tried to establish one special class for a provider who ownes 5 ranges which would mean 5 blocks für config and that's it in fact i needed 35 allow-blocks just for this. This is not a problem for me, as it's a small net with no I/Y-line-concept but what's about complex servers? i got lists of I:lines from other networks flooding me out of the server ;) as there are several hundreds of different ranges this means you will have to get thousands of Lines noone is able to manage/understand/admin anymore. So i ask if this is something wrong or did i miss some important facts here ;) | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
