| 1 |
# BANFILE |
| 2 |
# A file which contains users or sites which are banned from playing. |
| 3 |
# wildcards can be used in the file. Valid entries are put on seperate lines. |
| 4 |
# For a ban to result, both the user and ip must be true. |
| 5 |
# Note: Crossfire does not do a ip -> dns name, so matches for the |
| 6 |
# second part must be by ip. |
| 7 |
# |
| 8 |
# Syntax is "user@ip.address". Note that when actually putting in lines, the |
| 9 |
# double quotes should be ignored. user can be "*" to match any user. The |
| 10 |
# line may be prefixed by '~' to allow an entry. The lines are matched in the |
| 11 |
# given order; the first match is used. |
| 12 |
# |
| 13 |
# The ip address portion is done as a substring and not wildcard |
| 14 |
# match. Some examples, and results: |
| 15 |
# |
| 16 |
# "mark@tavern.us" - won't work - tavern.us would not match - must be ip |
| 17 |
# address. |
| 18 |
# "*@10.1.31.1" - users from 10.1.31.1 will not be able to play. |
| 19 |
# "*@10.1.31.*" - will not work - * is not a wildcard for host matches. |
| 20 |
# "*@10.1.31." - will do above - every ip that has 10.1.31. will be banned. |
| 21 |
# "*@10.1.31" - will ban above, but would also ban things like |
| 22 |
# "129.10.1.31". |
| 23 |
# "mark@10.1.31.1" - user mark from 10.1.31.1 will not be able to play. |
| 24 |
# "mark@" - user mark will not be able to play. |
| 25 |
# "mark@*" - user mark will not be able to play - * matches any host |
| 26 |
# name. |
| 27 |
# "~mark@1.2.3.4" - accept user mark from 1.2.3.4, regardless if a following |
| 28 |
# line would forbid it. For example, together with a |
| 29 |
# following line "mark@*" would allow mark to play only if |
| 30 |
# he connects from 1.2.3.4. |
| 31 |
# |
| 32 |
# Ip address can be determined by looking at the logs, or with the who command. |
