[Crossfire-wiki] [Crossfire DokuWiki] page changed: serverhosting:hosting_a_crossfire_server

[no-reply_wiki at metalforge.org]

A page in your DokuWiki was added or changed. Here are the details:

Date        : 2011/01/18 00:06
User        : mwedel
Edit Summary: add information for settings and metaserver2 file.

@@ -16,8 +16,9 @@
      * More bandwidth is of course better - even if not constantly being used, just so that the bursts of data get delivered faster
    * Have an ISP allows for server hosting
    * Network security to allow remote connections (aka, tweaked firewall rules) and communication to the metaserver(s).  The server runs on port 13327 - if you have a firewall, it will need to allow that port for incoming connections, and if you are running NAT, you will need to make sure that the connection to port 13327 gets routed to the correct server.  For metaserver2 updates, it is an outgoing connection to standard HTTP port (80), so very few firewalls should block it.
      * NOTE: Make sure the hostname is a Fully Qualified Domain Name (FQDN), otherwise there will be connections issues within the Crossfire client
+ 
  
  
  ===== Post Deployment =====
  
@@ -29,14 +30,29 @@
    * Edit and update the MOTD (Message of the Day) information (filename motd)
    * Edit and update the Server Rules file (filename rules)
      * As an example, if you want to ban players who exploit bugs, PK other players, disrupt gameplay for others, etc. - say so in the server rules file so if/when something like this happens you can take action and avoid the long "debate" afterwards 
    * Edit and update the Server News file - players like to know about new maps, bug fixes, special events, etc. (filename news)
+   * Look over the settings (filename settings)
+     * The default settings file will work just fine, and is most supported
+     * The file controls many aspects of play - permadeath or not, number of starting stat points, etc.
+   * If running a public server, you will most likely want to advertise your server via the metaserver (filename metaserver2)
+     * metaserver 1 (in settings file) is obsolete
+     * metaserver2 file is will documented and should be pretty clear.  localhostname is critical, and it must resolve to the IP address from which the update originates.  This means that if you have a NAT router, it will need to resolve to the router.
+     * metaserver2_notification must be changed from off to on.
+     * The server sends an update to the metaserver every minutes - if you do not see your server immediately, wait 5 minutes.
+     * If after 5 minutes, updates are still not happening, check the logs - messages should be generated.
+       * If curl is not installed on your system, metaserver2 updates will not happen, but the server will print a message stating the curl is missing.
+       * If localhostname does not match the IP address that metaserver2 sees the request coming from, it will send a message to the server but not add it.
+       * It is possible your subnet has been blacklisted from the metaserver - this is highly unlikely, but could result if another user from that same address block or ISP was abusing metaserver2 update policy.
    * Consider limiting how many guilds are initially available 
      * This will prevent a player or small group of players from buying all the guilds at once
      * This helps to make sure guilds will be available for new players who join your server later on
+     * FIXME: More information on how to do this is probably desirable
    * Have access to the server firewall rules for the extremely problematic player(s) and/or network(s)
      * Unfortunately, it's advised that you learn how to block (ban) networks and subnets
      * Much of this can be done in game while in DM mode (command: banish) but sometimes attacks are too widespread or not coming from player(s) from within the game
+   * The ban_file (filename ban_file) can be used to ban certain IP addresses or IP ranges - this may be easier than modifying firewall rules.  Note that the check is done at connection time, so would not cause players already connected to get dropped.
+   * Some of the above file changes will take effect immediately, while others require the server to restart before they take effect.
  
  
  
  ===== Technical Recommendations =====


IP-Address  : 173.228.106.246
Old Revision: http://wiki.metalforge.net/doku.php/serverhosting:hosting_a_crossfire_server?rev=1295329517
New Revision: http://wiki.metalforge.net/doku.php/serverhosting:hosting_a_crossfire_server

-- 
This mail was generated by DokuWiki at
http://wiki.metalforge.net/