rathena/conf-tmpl/packet_athena.conf
skotlex da13939d47 - Merged Meruru's update to socket.c, which includes a rewritten parse function, which should hopefully be more efficient than the previous code.
- The new code includes support for two config settings (packet_athena.txt): frame_size, which can be used to alter the logic packet-size allowed by the code, and mode_neg, which when set to yes, sets TCP_NODELAY on all connections (defaults to yes).


git-svn-id: https://svn.code.sf.net/p/rathena/svn/trunk@8799 54d463be-8e91-2dee-dedb-b68131a5f0ec
2006-09-18 22:28:07 +00:00

58 lines
1.6 KiB
Plaintext
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

// Athena sockets Configuration file
// translated (davidsiaw)
// Display debug reports (iWhen 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
// When enabled, sets TCP_NODELAY (disable nagel Algorythm) on all connections
mode_neg: yes
// frame packet size as considered by the server (when there's enough
// information in queue to fill the frame_size, a "send" is forced)
//frame_size: 1054
//----- IP Rules Settings -----
// Do we check IP's before allowing incoming connections?
enable_ip_rules: yes
// Decide the order of access restriction (Same as apache?)
// deny,allow Is the standard
order: deny,allow
// order: allow,deny
// order: mutual-failture
// The IP list which it uses to access controls
// allow : Allows access regardless of permissions
// deny : Completely disallow
// Žwè³µ : If the permission check encounters mutual-failure(whatever that means) it will disallow access
// 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 there is a connection request within ddos_interval msec for ddos_count number of times, it will assume it is a ddos attack
// Consecutive intervals(msec)
ddos_interval: 3000
// Connection frequency
ddos_count: 5
// The time interval after which the threat of ddos is assumed to be gone
// After this amount of time, the ddos restrictions are lifted.
ddos_autoreset: 600000
//import: conf/import/packet_conf.txt