DB:Auth:ip banned 548
Jump to navigation
Jump to search
Back to auth database list of tables.
The `ip_banned` table
This table contains all of the banned IPs and the date when (or if) the ban will expire.
Structure
Field | Type | Attributes | Key | Null | Default | Extra | Comment |
ip | varchar(15) | NO | 127.0.0.1 | ||||
bandate | int | unsigned | NO | ||||
unbandate | int | unsigned | NO | ||||
bannedby | varchar(50) | unsigned | NO | [Console] | |||
banreason | varchar(255) | unsigned | NO |
DB Structure
CREATE TABLE `ip_banned` ( `ip` varchar(15) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL DEFAULT '127.0.0.1', `bandate` int UNSIGNED NOT NULL, `unbandate` int UNSIGNED NOT NULL, `bannedby` varchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL DEFAULT '[Console]', `banreason` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL DEFAULT 'no reason', PRIMARY KEY (`ip`, `bandate`) USING BTREE ) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_general_ci COMMENT = 'Banned IPs' ROW_FORMAT = Dynamic; ;
Description of the fields
ip
The ip address.
bandate
The date when the ip was banned, in Unix time.
unbandate
The date when the ip will be automatically unbanned, in Unix time. A value less than the current date means, in effect, a permanent ban.
bannedby
The GM character's name who banned that ip. If banned from the console, then it will be empty (until improved).
banreason
The reason for the ban.