server:hosting
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
server:hosting [2016/04/18 21:32] saru Added a section on where account and player data is stored so that server hosts can archive it |
server:hosting [2018/03/05 06:26] karl reverted my "vandalism" from last time, i had been rock solid confessed, that the ports would be in the 132 range, and not 133, added mentioning of port 13325 for the watchdog |
||
|---|---|---|---|
| Line 17: | Line 17: | ||
| * Connections issues can occur within the Crossfire client if the domain name is not full qualified. | * Connections issues can occur within the Crossfire client if the domain name is not full qualified. | ||
| - Network security to allow remote connections and communication to the metaserver (if a public server). | - Network security to allow remote connections and communication to the metaserver (if a public server). | ||
| - | * The server runs on port 13327 | + | * The server runs (by default) on port **13327** |
| * if you have a firewall, it will need to allow that port for incoming connections, | * if you have a firewall, it will need to allow that port for incoming connections, | ||
| * if you are running NAT, you will need to make sure that the connection to port 13327 gets routed to the correct server. | * if you are running NAT, you will need to make sure that the connection to port 13327 gets routed to the correct server. | ||
| - | * The metaserver runs on port 13326 and 80 (HTTP) | + | * The metaserver runs (by default) on port **13326** and 80 (HTTP) |
| * if you have a firewall, it will need to allow 13326 and 80 for incoming connections, | * if you have a firewall, it will need to allow 13326 and 80 for incoming connections, | ||
| * if you are running NAT, you will need to make sure that the connection to port 13326 gets routed to the correct server. | * if you are running NAT, you will need to make sure that the connection to port 13326 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. | * For metaserver2 updates, it is an outgoing connection to standard HTTP port (80), so very few firewalls should block it. | ||
| + | ==== Watchdog ==== | ||
| + | The watchdog feature can be enabled manually in the //server/include/config.h// at [[:server:server_compiling]] as //#define WATCHDOG 1// . \\ | ||
| + | The watchdog port number is hardcoded inside //void watchdog(void)// located in the //server/socket.loop.c// source file as //13325// . \\ | ||
| + | :!: The watchdog feature may not work as it should currently until incl. server v1.70.0 to create | ||
| + | * a port at startup already ( but will create it after %503 ticks ) | ||
| + | * an //udp// port of the number 13325 ( but some random udp-port above 32768 ) | ||
| + | :!: Further it would create an additional socket, and that may lead to problems that the code does not work to add a new client. You may better not enable that feature! | ||
| ===== Installing a Crossfire Server from a Binary ===== | ===== Installing a Crossfire Server from a Binary ===== | ||
server/hosting.txt ยท Last modified: 2019/06/16 02:33 by saru
Page Tools
