#Openttd port forwarding code#

Build from master was advertising only the IPv4, as IPv6 was blocked by this 'better than nothing' firewall.I think the subject really speaks for itself. Disabled it to test and connection type became 'Public'. I had an issue with a ':3979' server, but I can't reproduce it :(Įdit: I had the IPv6 firewall activated on the router, and it has only 2 modes on or off, no fine tuning.

joined the only left server as spectator, works as expected.

after a short time both local ipv4 are removed from the list, and I can see some redrawing issues for the server list too.

clicked 'search LAN' again, server is added with the other local ipv4.

clicked 'search LAN', server is added with one of the local ipv4.

#Openttd port forwarding code#

clicked 'search internet', server is listed, its address is the invite code.connection type is 'Behind NAT', while a build from master is correctly advertised on master server, so direct connection should work.This PR affects the NewGRF API? (label 'needs review: NewGRF')ĭid some testing with a dedicated server and a client.The compatibility wrappers (compat_*.nut) need updating.ai_changelog.hpp, gs_changelog.hpp need updating.This PR affects the GS/AI API? (label 'needs review: Script API').This PR affects the save game format? (label 'savegame upgrade').The bug fix is important enough to be backported? (label: 'backport requested').This list is a reminder for the reviewers. Some things are not automated, and forgotten often. Let me know if you find any problems, etc. Notice how you didn't have to setup firewalls, port-forwarding, etc? Start a server, make it public or invite-only.Start the client by downloading it here: (or build it yourself, make sure you name your branch pr9017!).You can refresh individual servers if you want up-to-date information. Server info is delayed by 30s (by design).See the individual commits and the gist above. Public servers are the old advertised servers.Invite-only servers: the owner of the server needs to give the invite-code to someone before he can join.'Search LAN' does work for these servers, as do people with the public IP and if port-forwarding is setup correctly. Local servers: do not connect to the Game Coordinator.It tries 3 methods: direct connect, STUN, and if all fails, TURN (see gists for details) The Game Coordinator will try to connect the server and client.A client can join any server based on this 'join key' (without even knowing the IP of the server), either via listing or directly inputting it.Server listing returns only the 'join key' of a server.Every server gets assigned an unique 'join key' (called an 'invite code' in the UI).Every invite-only / public server creates a persistent TCP connection to a Game Coordinator (replacing the master-server).So, can we do this? I wrote a gist to explain the process of getting to this PR: īut in case you are not into reading, let me summarize: ) we need 'invite codes' so people can join each others game. This is way to advanced for the average Joe, and this becomes very clear when looking at Steam Discussions.įor Rich Presence (Discord, Steam.

Motivation / ProblemĬurrently, to host a network server you really need to know a few things about routers and networking. !!NOTE!! Currently the Game Coordinator is not working with this PR, while I rebuild this PR from the ground up. Otherwise your revision will not match anyone using the binaries above. If you build yourself, make sure to name your branch 'pr9017'.