I'd start by using https://www.yougetsignal.com/tools/open-ports/ while your server is running to see if those ports are indeed open on your router.I changed those files, but I'm still not having any luck. It just won't connect to the login page. Is it acceptable to add the server IP to the DMZ of the router to quickly test it without needing to set port forwarding? Is there a way to test from a client network if the public IP address is resolving to ww01.kddi-mmbb.jp?So if you're going to be hosting clients from outside your server, you're going to change the IP to be your public IP in the following locations:
It was the server's private IP address, but even when I changed it to my public IP address, nslookup on my laptop connected to the 4G network keeps failing.
Edit: Did you mean the game's DNS address setting? Also do I have to change all my IP addresses in the obcomsrv, dnsmaqs config, and both outbreak server configs to my public IP address?
Any client relying on your DNS server to resolve the names will need to change the DNS IP setting in the Outbreak game to point to your public IP. DNS 2 can be left at 0.0.0.0. Keep in mind that as I pointed out previously, clients don't necessarily need to rely on your DNS and can use other options to provide it (such as their own router's DNS server if applicable).Code: Select all
/etc/dnsmasq.d/obcomsrv config.properties
You'll also need to open the ports as previously mentioned.
In your use case if you're trying to test connecting to your server from outside your home network you are acting as one of the "clients."