e3b534df81
This is to follow the precident set by Atheme's atheme.conf.example file. Since the ircd now fails to start on a non-existant configuration file, seeing that message would make one know where to look. |
||
|---|---|---|
| .. | ||
| old | ||
| sgml/oper-guide | ||
| technical | ||
| account-notify.txt | ||
| away-notify.txt | ||
| challenge.txt | ||
| CIDR.txt | ||
| collision_fnc.txt | ||
| extban.txt | ||
| extended-join.txt | ||
| hooks.txt | ||
| Hybrid-team | ||
| index.txt | ||
| ircd.8 | ||
| ircd.example.conf | ||
| ircd.motd | ||
| logfiles.txt | ||
| Makefile.in | ||
| modeg.txt | ||
| modes.txt | ||
| monitor.txt | ||
| operguide.txt | ||
| opermyth.txt | ||
| Ratbox-team | ||
| README.cidr_bans | ||
| reference.conf | ||
| sasl.txt | ||
| server-version-info | ||
| services.txt | ||
| Tao-of-IRC.940110 | ||
| tgchange.txt | ||
$Id: README.cidr_bans 6 2005-09-10 01:02:21Z nenolod $ Basically what this patch does is allow for users to use cidr masks when setting bans, exceptions, and invite invex(modes beI respectively). This works for both IPv4 and IPv6 addresses. I won't go into details of how cidr works here, but to use them, you could do something like: /mode #foo +b *!*@10.0.0.0/8 /mode #foo +e *!*@10.0.10.0/24 Aaron Sethman <androsyn@ratbox.org> August 06, 2002