![]() There's not much you can do in this case besides requesting a static IP to your internet provider check your external IP again and send it to who wants to connect. Your ISP may also change your external address. In this case just change the Internal Address field in your port forward. Your router may decide to assign a different address to your server, changing its address and preventing people from connecting. You can find it here.Ī note on IP addresses: unless configured otherwise, both local and external IPs are probably dynamic, which mean they may change over time. This is probably 192.168.1.something.ĭone this, others can join by connecting to EXT_IP:EXT_PORT, where EXT_PORT is the one you specified in the second field, while EXT_IP is your external IP address. Internal IP Address: the local IP address of your server. ![]() Internal Start Port: this is the port the server is configured to listen to, by default 3979. As long as it is not used by anything else, you can use any port number you want. Protocol: I believe they tell you somewhere to allow both UDP and TCP, but I could be wrong Įxternal Start Port: this is the port others' clients attempt to connect to. Service #3 is the one that routes OpenTTD traffic to the server. This is a sample configuration, on your router will most likely look different. This allows you to enter commands to select levels, change settings, and more. ![]() By default, no command line options are needed. Your router simply doesn't know what to do with traffic coming from those ports. To run OpenTomb, simply run the executable generated by the build. It's most likely a port forwarding problem. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |