| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
| config:filter_files [2016/10/17 14:58] – [Filter Exemption Files] Document ipfilter_exempt.cfg digital man | config:filter_files [2017/12/09 13:47] – [Filter Exemption Files] Added link to default ipfilter_exempt.cfg digital man |
|---|
| * ''sysop*'' would mean users could not use names beginning with the word "sysop", like "sysopa" or "sysops" etc. | * ''sysop*'' would mean users could not use names beginning with the word "sysop", like "sysopa" or "sysops" etc. |
| * ''sysop~'' would mean users could not use names that have the word "sysop" anywhere in them, like "imthesysop" or "mesysophere". | * ''sysop~'' would mean users could not use names that have the word "sysop" anywhere in them, like "imthesysop" or "mesysophere". |
| | |
| | ===== IPv4 CIDR Notation ===== |
| | |
| | An additional comparison format was introduced in v3.17 (Feb-9-2017) specifically for partial (ranges of) IPv4 address matching following standard [[wp>Classless_Inter-Domain_Routing]] (CIDR) notation. For example, rather than using the comparison string "192.168.1.*" to match all IP addresses that begin with the first 3 octets of 192, 168, and 1, you could specify the same thing using CIDR notation: |
| | 192.168.1.0/24 |
| | |
| | This enables the flexibility of filtering ranges of IP addresses based on sub-networks that are not multiples of 8-bits (e.g. "192.168.1.33/30") and the format is compatible with commonly available regional block lists. |
| | |
| | All 4 octets of the IPv4 address must be specified in the CIDR comparison string (i.e. "192.168.1/24" is **not** a valid CIDR comparison string). |
| | |
| | CIDR comparisons beginning with the negation prefix (''!'') **are** supported (reverses the IP address comparison logic). |
| | |
| | IPv6 CIDR notation is not supported at this time. |
| |
| ===== Trash Can Files ===== | ===== Trash Can Files ===== |
| |
| ^Filename / Page ^Default Contents^Description^ | ^Filename / Page ^Default Contents^Description^ |
| |''[[ipfilter_exempt.cfg]]'' | | Hostnames and IP addresses that are considered exempt from temporary bans and permanent filtering (added Oct-17-2016)| | |''[[ipfilter_exempt.cfg]]'' |[[http://cvs.synchro.net/cgi-bin/viewcvs.cgi/*checkout*/ctrl/ipfilter_exempt.cfg|ipfilter_exempt.cfg]]| Hostnames and IP addresses that are considered exempt from temporary bans and permanent filtering (added Oct-17-2016)| |
| |''[[dnsbl_exempt.cfg]]'' |[[http://cvs.synchro.net/cgi-bin/viewcvs.cgi/*checkout*/ctrl/dnsbl_exempt.cfg|dnsbl_exempt.cfg]]|Hostnames and IP addresses and e-mail address (enclosed in <angle brackets>) which are to be exempt from positive DNS-based Blacklist results in the [[server:mail|Mail Server]] (see also ''dns_blacklist.cfg'')| | |''[[dnsbl_exempt.cfg]]'' |[[http://cvs.synchro.net/cgi-bin/viewcvs.cgi/*checkout*/ctrl/dnsbl_exempt.cfg|dnsbl_exempt.cfg]]|Hostnames and IP addresses and e-mail address (enclosed in <angle brackets>) which are to be exempt from positive DNS-based Blacklist results in the [[server:mail|Mail Server]] (see also ''dns_blacklist.cfg'')| |
| |''[[spamblock_exempt.cfg]]'' |[[http://cvs.synchro.net/cgi-bin/viewcvs.cgi/*checkout*/ctrl/spamblock_exempt.cfg|spamblock_exempt.cfg]]|Hostnames and IP addresses which are not to be blocked from sending e-mail to the [[server:mail|Mail Server]] (see also ''spamblock.cfg'')| | |''[[spamblock_exempt.cfg]]'' |[[http://cvs.synchro.net/cgi-bin/viewcvs.cgi/*checkout*/ctrl/spamblock_exempt.cfg|spamblock_exempt.cfg]]|Hostnames and IP addresses which are not to be blocked from sending e-mail to the [[server:mail|Mail Server]] (see also ''spamblock.cfg'')| |
