![dedicated openttd server dedicated openttd server](http://i402.photobucket.com/albums/pp101/prebsi/tux.jpg)
- #Dedicated openttd server how to#
- #Dedicated openttd server password#
- #Dedicated openttd server Pc#
- #Dedicated openttd server mac#
Note that you wont be able to host the server if you have a private IP. Make another rule for port 3938 ( UDP only ) if you want your server to appear on the OpenTTD site. Choose both TCP and UDP connections and save the rule.ħ. Enter the service port ( 3979 for OpenTTD ) and local IP adress you just reserved for your PC. Find the Port forwarding/Virtual servers tab and add the new rule.Ħ. You might need to reload the router afterwards.ĥ.
![dedicated openttd server dedicated openttd server](https://pics.onsizzle.com/linux-raspberrypi-4-19-50-v7-896-smp-thu-jun-20-16-11-44-60811375.png)
#Dedicated openttd server mac#
Reserve the local IP ( for example 192.168.0.100 ) for your mac adress.
#Dedicated openttd server Pc#
Find the DHCP clients list and copy your PC mac adress.Ĥ. If you want your server to be visible on the public server list (recommended), you will also need to forward UDP connections to port 3978.Ģ. (If you can’t use port 3979 for some reason, you can make OpenTTD use another port by entering “server_port ” into the game’s console.) In this case, UDP and TCP connections to port 3979 will need to be forwarded. Else, the data will simply be discarded before it ever reaches the server. If you are connecting to the Internet through a router you will need to tell the router to send game data from players outside of your home network to the computer that will be running your OpenTTD server. If you want your server to be visible on the public server list as well (recommended), you will also need to open port 3978 to UDP connections only. Instead, configure it to allow UDP and TCP connections to port 3979 (“port opening”). įor your safety, do not disable your firewall entirely. Otherwise, they will need to know your router’s IP address, or your computer’s if you aren’t using a router. If some players are connecting via the public Internet, however, your server will only appear if you have chosen “Internet (advertise)” under “Connection” (there may be a delay of several minutes before it is visible). Players connected to your home network should immediately see your server on the server list and be able to connect easily. Click New Game (to generate random new game), or Load Game (to continue an saved game), or Play Scenario, or Play Heightmap. Max spectators limits the number of clients who can connect to watch but not play (not-players).ĥ.Max companies limits the number of companies at game.Max clients limits the total number of clients (players and spectators) that can connect.Language Spoken is for requesting that users speak a certain language on your server.Connection specifies whether the server is for local/private use only, or advertises itself to the master server so it is visible in the internet server list.
#Dedicated openttd server password#
Set Password sets a password for the server so that only users who know the password can join your game.Pick a name for your game to help others identify it, and enter it into the Game name box
#Dedicated openttd server how to#
This guide will explain how to do it and how to forward the ports if you’re connecting to the Internet through a router.ģ. I think there should be switch/settings whether openttd will use IPv4, IPv6 or autodetect for all network communication - as in some situations, both IPv4 and IPv6 protocols seems to be available (my machine have IPv4 and IPv6 address), DNS for you want to host multiplayer network games, you need to set up an OpenTTD server on your computer. In my case the "guess" parameter of AF_UNSPEC probably ended up with IPv6 being used instead of IPv4. So there seems to be no switch whether to use IPv4 or IPv6 in the attempts to communicate with master server. NetworkAddress(const char *hostname = "", uint16 port = 0, int family = AF_UNSPEC) Looking at definition of NetworkAddress constructor: NetworkAddress out_addr(NETWORK_MASTER_SERVER_HOST, NETWORK_MASTER_SERVER_PORT) Void NetworkUDPAdvertiseThread(void *pntr) Peeking into sources reveals this call reponsible for communication with master server: Seems like it is using IPv6 in the attempts to communicate with master server. I started a dedicated server using "./openttd -D" and it seems not to appear in the master list and on console I see this:ĭbg: advertising to master serverĭbg: sendto(:3978 (IPv6)) failed with: 101 On my system, I have IPv6 support (debian unstable), however due to ISP not supporting IPv6, any IPv6 packets sent to internet basically end up in /dev/null