Using the metaserver from the client
Players who want to use the metaserver to list the currently available
servers should go to
this
link, or just follow the "Servers" link from the main dopewars web page.
It cannot be guaranteed that all the listed servers are functional - they
may, for example, have been registered in error, or a server may have crashed
since being added to the list - but the list is checked daily for service,
and so there is at least a good chance that the servers listed there will
be working.
The metaserver, being a collection of CGI scripts, should work happily on
most machines which have web access. A problem occurs, however, if your
connection to the Web is via. an enforced proxy server (i.e. traffic on
port 80 from your machine is blocked by firewall). dopewars can be
configured to connect via. a proxy server without too much difficulty; if
your proxy server is at proxy.com on port 8080 then you should
add the following lines to your dopewars
configuration file:-
MetaServer.Name=proxy.com
MetaServer.Port=8080
MetaServer.Path=http://bellatrix.pcl.ox.ac.uk/~ben/cgi-bin/server.pl
Using the metaserver from the server
People running servers who do not want their details listed by the
metaserver should disable the metaserver comunication of the server with
the MetaServer.Active=0
configuration file setting, or the -S
command line option. Servers
which do register their details can have their accompanying comment
set with the
MetaServer.Comment configuration file setting.
Each dopewars server notifies the metaserver of its current status, and sends this data on startup and shutdown, and when players leave or join the game. See the server page for more details.
But it's displaying the wrong IP address!
Once connected to the metaserver, you may find that it incorrectly
displays the domain name of your server machine. This is usually because the
metaserver cannot resolve your IP address to a domain name.
In this case, you will need to override the hostname that the metaserver guesses for your machine with one you choose yourself. This is done by specifying the hostname with the MetaServer.LocalName variable in your dopewars configuration file. In order to prevent abuse of this facility, you must obtain a password from the metaserver maintainer to authenticate your chosen hostname. Email the maintainer, giving the exact hostname you want to use (be aware that this is case-sensitive) and you will be given a password. Specify this password with the MetaServer.Password variable in the dopewars configuration file.
For example, if you wish your server to be known as dope-serv.com and
you have emailed the maintainer, receiving the password Dope-Auth, then
add the following to the dopewars configuration file:-
MetaServer.LocalName=dope-serv.com
MetaServer.Password=Dope-Auth
Restart your dopewars server, or send it a SIGUSR1 signal, for the change to take effect. Bear in mind that if you make up a non-existent or invalid domain name, the metaserver will accept it, but the server will be removed from the metaserver's list when it is checked daily for service.
But my server has a dynamic IP...
Finally, your server's IP may be resolved happily, but you may have a connection
to the internet which assigns you a dynamic IP. Consider what happens if your
connection is broken before the dopewars server exits; the metaserver will
list the IP of the "old" server, and you will now have no way of removing that
entry when your connection comes back up, as your IP will be different. In
this case, you can email the
metaserver maintainer, and specify a blank MetaServer.LocalName variable.
You will again receive a MetaServer.Password variable (see
above), which the metaserver
will use to identify "your" server; now, when your internet connection is
restored, the server registration with the "new" IP will automatically replace
the "old" one.