[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        : 2013/10/25 21:03
User        : saru
Edit Summary: 

@@ -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
+ 
  
  
  
  
@@ -34,9 +35,9 @@
    * 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)
+   * If running a public server, you will most likely want to advertise your server via the metaserver (filename metaserver2 located in /usr/games/crossfire/etc/crossfire)
      * 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.


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

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