#Flightgear multiplayer code#

most data is -unconditionally- transmitted to all 'active' clients), which may thus create considerable amounts of traffic this ought to be taken into consideration due to bandwidth limitations in most hosting packages (i.e.

#Flightgear multiplayer code#

Note: Currently (May 2008), the server code basically boils down to a packet multiplexer (i.e. about 5-10 MB of hard disk space (mainly required for building the binary).fgms source code, currently version 0.10.23.a working GNU toolchain including gcc/g++ (compiler), make & cmake.permission to run unattended background processes (this may only be an issue with certain limited hosting packages).firewall policies will need to be set up to allow for incoming and outgoing UDP traffic for the corresponding ports, the same applies to the administration port (TCP).if the server is meant to be a public internet server: an internet connection, featuring sufficient upstream/downstream capabilities (see below for details concerning bandwidth requirements).SSH/telnet, a conventional web hosting package will usually not be sufficient!)-suitable hosting packages are: dedicated root servers, virtual private servers, shell servers - for a collection of free shell account providers that may be suitable for fgms, see Free Shell Providers (you may want to check this out if you are interested in running fgms but don't have hosting yet) direct/physical or remote access to the server (i.e.For specific documentation for setting up on FreeBSD see Howto:Set up a multiplayer server on FreeBSD.

Speed of the machine isn't of great consequence as the protocol is a multiplexer which doesn't require much processing grunt.

A computer running a variant of *nix to compile and host the server.

8 Check the status of the server through Telnet.