-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathmasterd.prf
79 lines (63 loc) · 2.82 KB
/
masterd.prf
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
#=============================================================================
# Pushbutton Labs' Torque Master Server Preferences/Configuration File
#=============================================================================
#-----------------------------------------------------------------------------
# General Server Settings
#-----------------------------------------------------------------------------
# Name of the Master Server. Default: "PBMS"
$name "PBMS"
# Region the Master Server is in. Default: "Earth"
$region "Earth"
# IPv4 address that the Daemon listens and sends on. Default: "0.0.0.0" for All
# NOTE: IPv6 currently not supported.
$address "0.0.0.0"
# Port number that the Daemon listens and sends on. Default: 28002
$port 28002
# How long since the last heartbeat from a server before it is deleted.
# Default: 180 (3min)
$heartbeat 300
# Verbosity of log output. Default: 4
# 0 - No Messages
# 1 - Error Messages
# 2 - Warning Messages*
# 3 - Informative Messages*
# 4 - All [miscellaneous] Messages*!
#
# * Indicates it includes all the message types above it.
#
$verbosity 4
#-----------------------------------------------------------------------------
# Flood Control Settings
#
# Flood control uses a ticket based approach to deal with remote hosts
# that are either game clients continously querying us or malicious parties
# attempting cause an Denial of Service attack by keeping the master busy.
#
# A remote host will be ticketed for every packet of data it sends to this
# master server, so keep that in mind when setting the maximum of tickets.
# There's even a setting to incor a severe penalty for sending bad/unknown
# packets to us of which helps ban the offending remote host a lot sooner.
#
# Once maximum tickets has reached for a remote host they are then temporarily
# banned. When a remote host is banned they are ignored until the ban time has
# expired. A remote host is forgotten about after not receiving a packet from
# them after a time of seconds ($flood::ForgetTime), except when they are
# currently banned. Once unbanned then the forget time is reset so they are
# not forgotten too soon.
#-----------------------------------------------------------------------------
# Maximum number of tickets before a remote host is banned.
# Default: 300
$flood::MaxTickets 30000
# Time in seconds until the tickets placed on a remote host is reset.
# Default: 60 (1 minute)
$flood::TicketsResetTime 60
# Time in seconds for how long a remote host is banned once reaching max tickets.
# Default: 300 (5 minutes)
$flood::BanTime 600
# Time in seconds after last hearing from a remote before it's forgotten about.
# Default: 900 (15 minutes)
$flood::ForgetTime 900
# Number of tickets placed against remote host for sending bad or
# unknown formatted packets.
# Default: 50
$flood::TicksOnBadMessage 1