IMM_BAN
Keywords: IMM_BAN, IMM_UNBAN, WIZ_BAN, WIZ_UNBAN
=== STAFF MANUAL ===
Usage: ban
ban <all | new | select> <site>
unban <site>
Description:
Prevent connections from a hostname or IP pattern. With no
arguments, lists every active ban with its type, creation date,
and the staff member who set it. Bans persist across reboots and
apply to any incoming hostname that contains the banned pattern
as a substring -- partial matches succeed, so a ban on evilhost
also blocks mail.evilhost.net.
Ban Types:
all ............ Block all connections from the site. Any new
descriptor is closed on the login screen.
new ............ Allow existing characters to log in, but
reject new character creation from the site.
select ......... Allow only players whose characters carry
the SITEOK flag. Used to whitelist trusted
players from an otherwise-banned site.
Output:
The no-argument listing is a four-column table:
Banned Site Name Type Banned On Banned By
Site Hostname substring matched against connections.
Type all, new, or select.
Banned On The date the ban was created.
Banned By The staff character who issued the ban.
Unbanning:
unban <site> removes an existing ban by exact site string.
To change the type of an existing ban, you must unban it first
and re-add it with the new type.
Restrictions:
- Requires the Security staff permission.
- Issuing an all ban additionally requires full Security
privileges -- lesser security staff may only create new or
select bans.
- Duplicate site strings are rejected; unban the existing
entry first if you want to replace it.
- Site names are lowercased and truncated to the maximum
banned-site length on insertion.
Notes:
- All ban and unban actions are announced on the staff
wiznet and written to the mudlog.
- Matching is substring-based, not glob -- choose patterns
carefully to avoid catching innocent hostnames.
- The ban list is saved to disk immediately on every add
or remove, so changes survive a crash.
Related Helpfiles: WIZ_WIZLOCK, WIZ_ACCTLOCK
=== END MANUAL ===