summaryrefslogtreecommitdiff
path: root/conf/packet.conf
diff options
context:
space:
mode:
authorAndrei Karas <akaras@inbox.ru>2016-08-20 17:49:55 +0300
committerAndrei Karas <akaras@inbox.ru>2016-08-20 17:49:55 +0300
commitddf5a3b944b23d0a138f108b8db328ddeaa6df7c (patch)
treeed9485b3870cbc8609385b9ca64b5308edab78bc /conf/packet.conf
parent9417d710b889b660ccb798b69f2dd8a05cbc5bbe (diff)
downloadserverdata-ddf5a3b944b23d0a138f108b8db328ddeaa6df7c.tar.gz
serverdata-ddf5a3b944b23d0a138f108b8db328ddeaa6df7c.tar.bz2
serverdata-ddf5a3b944b23d0a138f108b8db328ddeaa6df7c.tar.xz
serverdata-ddf5a3b944b23d0a138f108b8db328ddeaa6df7c.zip
Get updated configurations from Hercules.
Without evol changes.
Diffstat (limited to 'conf/packet.conf')
-rw-r--r--conf/packet.conf67
1 files changed, 0 insertions, 67 deletions
diff --git a/conf/packet.conf b/conf/packet.conf
deleted file mode 100644
index 3a7ec2c8..00000000
--- a/conf/packet.conf
+++ /dev/null
@@ -1,67 +0,0 @@
-//===== Hercules Sockets Configuration =======================
-//= Hercules Sockets Configuration File
-//===== Translated by: =======================================
-// Davidsiaw
-//============================================================
-
-// Display debug reports (When something goes wrong during the report, the report is saved.)
-debug: no
-
-// How long can a socket stall before closing the connection (in seconds)?
-stall_time: 60
-
-// Maximum allowed size for clients packets in bytes (default: 65535).
-// Default Values:
-// 24576 (Clients < 20131223)
-// 65535 (Clients >= 20131223)
-// NOTE: To reduce the size of reported packets, lower the values of defines, which
-// have been customized, such as MAX_STORAGE, MAX_GUILD_STORAGE or MAX_CART.
-// NOTE: Do not modify this setting, unless the client has been modified to support
-// larger packets. The client will crash, when it receives larger packets.
-//socket_max_client_packet: 65535
-
-//----- IP Rules Settings -----
-
-// If IP's are checked when connecting.
-// This also enables DDoS protection.
-enable_ip_rules: yes
-
-// Order of the checks
-// deny,allow : Checks deny rules, then allow rules. Allows if no rules match.
-// allow,deny : Checks allow rules, then deny rules. Allows if no rules match.
-// mutual-failure : Allows only if an allow rule matches and no deny rules match.
-// (default is deny,allow)
-
-order: deny,allow
-// order: allow,deny
-// order: mutual-failture
-
-// IP rules
-// allow : Accepts connections from the ip range (even if flagged as DDoS)
-// deny : Rejects connections from the ip range
-// The rules are processed in order, the first matching rule of each list (allow and deny) is used
-
-// allow: 127.0.0.1
-// allow: 192.168.0.0/16
-// allow: 10.0.0.0/255.0.0.0
-// allow: all
-
-// deny: 127.0.0.1
-
-//---- DDoS Protection Settings ----
-// If ddos_count connection request are made within ddos_interval msec, it assumes it's a DDoS attack
-
-// Consecutive attempts interval (msec)
-// (default is 3000 msecs, 3 seconds)
-ddos_interval: 3000
-
-// Consecutive attempts trigger
-// (default is 5 attemps)
-ddos_count: 5
-
-// The time interval after which the threat of DDoS is assumed to be gone. (msec)
-// After this amount of time, the DDoS restrictions are lifted.
-// (default is 600000 msecs, 10 minutes)
-ddos_autoreset: 600000
-
-import: conf/import/packet_conf.txt