Page 5 of 5

Re: Plans to go open source

Posted: Sun Jan 26, 2020 9:59 pm
by Isles487


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?
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:

Code: Select all

/etc/dnsmasq.d/obcomsrv config.properties
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).

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."
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?
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.

Re: Plans to go open source

Posted: Mon Jan 27, 2020 3:33 am
by refan988


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:

Code: Select all

/etc/dnsmasq.d/obcomsrv config.properties
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).

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."
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?
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.
Nu luck unfortunately, even when I set my server's IP address to the dmz and opened all the ports I couldn't connect from a different public IP address. The odd thing was that if I did set my PS2's DNS address to my public IP address, it did work for connecting to the server within my private network, but not outside of it

Re: Plans to go open source

Posted: Mon Jan 27, 2020 4:30 am
by ragnar1990
I'm stuck in setting up the DNAS, which gives me the following messages...
https://ibb.co/KWCzYxD

Pretty sure that the former steps are totally correct.

Re: Plans to go open source

Posted: Mon Jan 27, 2020 4:44 am
by refan988
I'm stuck in setting up the DNAS, which gives me the following messages...
https://ibb.co/KWCzYxD

Pretty sure that the former steps are totally correct.
It probably means that the dns setup isn't correct.

Re: Plans to go open source

Posted: Mon Jan 27, 2020 6:09 am
by ragnar1990
I'm stuck in setting up the DNAS, which gives me the following messages...
https://ibb.co/KWCzYxD

Pretty sure that the former steps are totally correct.
It probably means that the dns setup isn't correct.
https://ibb.co/SvYcRC8
https://ibb.co/K0LjbC7
No luck at all.

Re: Plans to go open source

Posted: Mon Jan 27, 2020 7:53 am
by refan988
I'm stuck in setting up the DNAS, which gives me the following messages...
https://ibb.co/KWCzYxD

Pretty sure that the former steps are totally correct.
It probably means that the dns setup isn't correct.
https://ibb.co/SvYcRC8
https://ibb.co/K0LjbC7
No luck at all.
You can use my Virtualbox exported program if you want. It runs well. https://drive.google.com/file/d/1lrKHM3 ... sp=sharing

Re: Plans to go open source

Posted: Mon Jan 27, 2020 2:45 pm
by ragnar1990


It probably means that the dns setup isn't correct.
https://ibb.co/SvYcRC8
https://ibb.co/K0LjbC7
No luck at all.
You can use my Virtualbox exported program if you want. It runs well. https://drive.google.com/file/d/1lrKHM3 ... sp=sharing
Thank you so much though the image is damaged.

Re: Plans to go open source

Posted: Tue Jan 28, 2020 12:18 am
by ragnar1990
You can use my Virtualbox exported program if you want. It runs well. https://drive.google.com/file/d/1lrKHM3 ... sp=sharing
Thanks, finally worked from extracting the vmdk file by using 7-Zip. >_>

Re: Plans to go open source

Posted: Fri Jan 31, 2020 6:39 pm
by refan988
My issue is I can't figure out how to get dnsmasqn to work on the internet. Anytime I try nslookup www01.kddi-mmbb.jp [my public Ip address] from outside my network all I get is "DNS request timed out."

Edit: Apparently incoming port 53 is blocked by my ISP.

Re: Plans to go open source

Posted: Fri Jan 31, 2020 11:28 pm
by Isles487
My issue is I can't figure out how to get dnsmasqn to work on the internet. Anytime I try nslookup www01.kddi-mmbb.jp [my public Ip address] from outside my network all I get is "DNS request timed out."

Edit: Apparently incoming port 53 is blocked by my ISP.
Pretty common - which is part of the reason why I asked you to use that website to check open ports. Sometimes port 25 outbound (SMTP) is blocked as well as some other common ports.

The solution is to have clients use their own DNS server and then connect to you for the rest, or, if they are using emulator, they can set their own DNS settings in the dev9 plugin and skip the need for a DNS server entirely.

Re: Plans to go open source

Posted: Sat Feb 01, 2020 1:06 am
by ragnar1990
My issue is I can't figure out how to get dnsmasqn to work on the internet. Anytime I try nslookup www01.kddi-mmbb.jp [my public Ip address] from outside my network all I get is "DNS request timed out."

Edit: Apparently incoming port 53 is blocked by my ISP.
I think you may give OpenVPN a look and open port 1194. Create another firewall rule for port 53, 443, 8200, 8300, 8590, 8690 separately to only allow connection from subnet 10.8.0.0/24. Launch PCSX2 and make sure that the DNS settings in your memcard has been set to auto, then set the CLR_DEV9 plugin settings like this.https://ibb.co/VSpzJ5W

Re: Plans to go open source

Posted: Sat Feb 01, 2020 2:21 am
by refan988
My issue is I can't figure out how to get dnsmasqn to work on the internet. Anytime I try nslookup www01.kddi-mmbb.jp [my public Ip address] from outside my network all I get is "DNS request timed out."

Edit: Apparently incoming port 53 is blocked by my ISP.
Pretty common - which is part of the reason why I asked you to use that website to check open ports. Sometimes port 25 outbound (SMTP) is blocked as well as some other common ports.

The solution is to have clients use their own DNS server and then connect to you for the rest, or, if they are using emulator, they can set their own DNS settings in the dev9 plugin and skip the need for a DNS server entirely.
The emulator config did the trick! Tested it by tethering to my phone and it worked (oddly enough it only worked when I tethered to my phone over wifi instead of usb).

Re: Plans to go open source

Posted: Wed Feb 05, 2020 6:26 am
by Ji29
So after ample time configuring it, I finally have it speaking to the server using Windows Server 2012 setup however, It seems to get stuck at 40% for the DNAS authorisation in progress screen & cannot advance. I'm currently installing wireshark to monitor the traffic but having no luck.

Any advice?

Re: Plans to go open source

Posted: Fri Feb 21, 2020 1:20 am
by leotreves
So turns out that even with my 53 port open I cannot connect to my server without using the CLR9 file with that 192.0.2.1 setup. Is there any way around this that doesn't involve Hamachi or VPNs?