| version 1.1 | | version 1.2 |
|---|
| | |
| # BANFILE | | # BANFILE |
| # A file which contains users or sites which are banned from playing. | | # A file which contains users or sites which are banned from playing. |
| # wildcards can be used in the file. Valid entries are put on seperate lines. | | # wildcards can be used in the file. Valid entries are put on seperate lines. |
| # example entries: | | # For a ban to result, both the user and ip must be true. |
| # "joeblow@*.*.abc.edu" ban joeblow at the given site : note only works if | | # Note: Crossfire does not do a ip -> dns name, so matches for the |
| # user is using a client, as telnet does not report | | # second part must be by ip. |
| # userid. | | # Note2: The user portion is currently igored - the ban check is |
| # "*@*.*.abc.edu" ban the entire site...works both with telnet and | | # done before the user logs in. |
| # client. | | |
| # | | # |
| # Note - banning by user name should not be used - the client | | # Syntax is "user@ip.address". Note that when actually putting |
| # (including the newclient) can easily be changed to use any | | # in lines, the double quotes should be ignored. user should |
| # username. Also, with the new client, numeric host id is | | # always be "*" for any form of banning to work. |
| # used (ie, 192.15.4.6). So to ban sites, you need to find out their | | # |
| # numeric IP address - not hard, 'who reports this | | # the ip address portion is done as a substring and not wildcard |
| | | # match. Some examples, and results: |
| | | # |
| | | # "mark@tavern.us" - won't work - mark won't match, nor would tavern.us |
| | | # match - must be ip address. |
| | | # "*@10.1.31.1" - users from 10.1.31.1 will not be able to play. |
| | | # "*@10.1.31.*" - will not work - * is not a wildcard for host matches. |
| | | # "*@10.1.31." - will do above - every ip that has 10.1.31. will be banned. |
| | | # "*@10.1.31" - will ban above, but would also ban things like "129.10.1.31". |
| | | # |
| | | # Ip address can be determined by looking at the logs, or with the who command. |