[NA - 2011] "Map Under Maintenance" when trying to connect from Public IP

**seerofvoid420** · 08-01-17

I got an Odin (2011) pserver set up, and everything worked when I played from inside my network.
I then set it up to be able to connect from my external IP.
When i try and connect to my external IP OR my internal IP, I get a "Map under maintenance" message.

EDIT: See 2nd post for the new errors

Old problem

Spoiler:

Looking in the Zone server logs, I get "18:25:44 *FAILED Listen_Add - IP = myexternalIP912x" on Zone00, Zone01, Zone02, and Zone03.

I assume this means it tried to bind to my public IP, and then failed. Oddly the other services bind fine to my external. All ports on firewall are open (9000-9126) and I can even make characters and delete them, but I can't load in to any maps.
Zone00 Msg Log

Spoiler:

Zone00 Assert Log

Spoiler:

Zone01 Msg Log

Spoiler:

Zone01 Assert Log

Spoiler:

Zone02 Msg Log

Spoiler:

Zone02 Assert Log

Spoiler:

Zone03 Msg Log

Spoiler:

Zone03 Assert Log

Spoiler:

They all have the exact same error, except the different port number of course. Here's the server IP conf

Spoiler:

When I bind it to the local IP (172.16.15.4 in my case) everything works fine except (obviously) I can't connect via external IP. I'm using the batch file with

Code:

 Client.exe -osk_server myexternalIP -osk_token IPutMyTokenHereLolol -osk_store http://google.com

Hopefully this is all the information needed to find a solution, but I will gladly provide more. I appreciate all the work that went in to making this possible! Thanks guys!

EDIT: See next post for the new problem.

**MentaL**

[NA - 2011] "Map Under Maintenance" when trying to connect from Public IP

**seerofvoid420** · 09-01-17

I now got all the servers to bind correctly to their IPs, but now I can't connect to the server anymore. "The map is under maintenance". I'm getting
This

Code:

FAILED - ZONE Parser's unknowned packer
000227 2017-01-09 09:18:07 Closed ZN from (SERVER_ID_ZONE            world=  0 zone=  0, -1   =     172.16.0.1: 5620)    0/ 100°³ (DEP=2,CMD=2,LEN=9,WORK=3)
000228 2017-01-09 09:18:08 ERROR - ´ë±âÁßÀÎ WorldNo=0, ZoneNo=2 IP=71.90.208.44, Á¢¼ÓÇØ¿Â WorldNo=0, ZoneNo=2 IP=172.16.0.1 ´Ù¸§

in the World Manager logs, but I don't know how to troubleshoot this error. Anyone know anything about this error?

EDIT: Attached my ServerInfo files.

**Evildarkang** · 10-01-17

you have 3 ip's

192.168.*.*
71.90.*.*
and 127.0.0.1

why not try 192.168.*.* ???? :S

**seerofvoid420** · 10-01-17

Originally Posted by Evildarkang

you have 3 ip's

192.168.*.*
71.90.*.*
and 127.0.0.1

why not try 192.168.*.* ???? :S

I'm trying to set this up so other people can play from outside my network without using something like Hamachi. Also, my internal network is set up in a /16 subnet, so that's why I'm using 172.16.*.* instead of 192.168.0.*

The only way to get the client to try to connect on the public IP is by having it set up this way, as detailed here: http://forum.ragezone.com/f593/local...machi-1097712/

My understanding of it is the 3 different configs allow the servers to tell the client to use the Public IP (71.90.208.44), but the servers still talk to each other with the local IP (172.16.15.4 or 127.0.0.1).

If anyone has successfully been able to get these configs to work, let me know what I'm doing wrong. I've forwarded every port between 9000 and 9200 to be safe, and I still get "Map under maintenance", and then that weird error from the World Manager

**Taiga** · 16-01-17

Use your WAN IP Address and make sure it's port forwarded correctly. Double check it for your WAN IPs. (Some ports might be blocked by your ISP so check that as well). Also Make sure you've set-up the correct internal IPs and check your firewall(s).

**Pagefault404** · 17-01-17

If you're following the linked post by the letter, you missed a config line.

Code:

SERVER_INFO "w0_World_Manager",  5, 0, 0, 8, "172.16.15.4",        9116,  1,        30     ;         From OPTOOL

The IP should be 127.0.0.1 if you're following that guide.

Also, unrelated, why are you using a class B subnet on an internal home network? You've essentially allowed yourself 1,073,741,824 total IP addresses for your network. 16,384 total networks. You can still use a Class C subnet and keep your existing 172.16 network. Even if 172.16 is a class B private IP address range, if you use a Class C subnet (255.255.255.0) then the only addresses that matter are whatever are on the same subnet which it seems like that's what you're doing now. You're occupying the 172.16.15.X IP address range. Change your subnet to 255.255.255.0 and reduce your attack surface.

Edit: Unless you're taking some kind of computer class and are fucking around to understand subnets, the use of a Class B range is total overkill.

**seerofvoid420** · 18-01-17

The only purpose of the massive subnet is to fuck around with networking, yes. I've reduced the subnet from a /12 to a /16 (which is still a ton of IPs) and I use a different 172.16.x.* for each "service" I run to keep them organized. I'm not worried about my attack surface sitting behind a pfSense firewall and Cloudflare, and each server runs in its own VM on my ESXi cluster.
I've since also moved the VM to Server 2008r2 and changed the server's IP to "172.16.21.1".

Back on topic, when I set the configs to run on external IP, I get the "Map under maintenance" error still. I can ping all the ports from the external IP, I checked with an online port checker tool. Feel free to check them yourself, my public IP is 71.90.208.44. I went through and re-wrote every config file to match the Local host your pserver thread, and no luck. Is anyone willing to take a look with Teamviewer?

**Pagefault404** · 18-01-17

Since you're operating over an, essentially, simulated corporate infrastructure, you're going to need to create a network topographic map for all related nodes, their IP addresses on the inbound and outbound adapters, your internal and external facing addresses, and likely post that here (You can change the IPs for the network map if you're worried about security)

This seems like something isn't forwarding correctly, or you're only getting partial connections (connecting enough to access characters or accounts, but failing when attempting to connect to a map)

I'm not sure how many nodes an external connection would need to hit over your network, but at least three minimum:

pfSense
Router
Server

This could be an issue with network segmenting as well. If you're able to ping the ports on their listening services, but get MuM error, it's possible that a segmenting issue is keeping something from going where it's supposed to. If pings get routed appropriately, chances are, your server is having difficulty communicating with itself. Are you using any corporate switching hardware, like Cisco Catalyst switches, HP Procurve, Juniper EX Series, NetGEAR ProSafe?

If so, you're going to need to create VLANs for your network. If you're running a /16 network, have you done the subnetting for your entire network and broken down where the network segments exist? If you have critical services sitting on different network segments and no VLAN switching in place, they won't be able to communicate.

The guide you're following was designed with a much less complex network in mind than you currently have set up. You may be a victim of your own technical aptitude at this point. If you have CloudFlare guarding your network entry point, it's possible that the timeout CloudFlare is provoking is throwing a MuM error as the client is unsure how to translate any kind of delay in communication, so it assumes the map is under maintenance.

You're a pretty savvy guy, otherwise I wouldn't suggest this:

Tear it all down. All of it. Get the server working over a standard home network setup. Analyze how it works and why it works in that environment, then rebuild your more complicated network around that methodology so as to preserve it's function.

Ultimately, you're probably going to need to create a DMZ with little to no security at all, that exists parallel to, but unaffected by, your network topography in order to preserve the simple network structure that the guide you're following was designed for. If you're trying to simulate a corporate infrastructure for training purposes, then this is a perfect exercise because in the corporate networking world, sometimes, you have legacy applications that are business critical that WILL NOT operate on a modern network. So you need to create special exceptions for them.

I say all of this because it appears as though you have done your due diligence in regards to following the guide to the letter from a configuration standpoint. At this juncture, Occam's Razor would suggest that it's some sort of communication issue that exists when trying to accept inbound external traffic.

You seem the type to see hoof prints and think zebras. This is good, but, sometimes it's only horses. Use the OSI model and work your way up.

- - - Updated - - -

FYI that's me running an Nmap scan on your IP. I was having issues pinging it.

- - - Updated - - -

So right away, I can only see one publicly available port. 9110. Which is the world server. Something is filtering the other ports that need to be publicly available. I would check your ACL on pfSense

Code:

Initiating Connect Scan at 11:23
Scanning 71.90.208.44 [1000 ports]
Discovered open port 80/tcp on 71.90.208.44
Discovered open port 21/tcp on 71.90.208.44
Discovered open port 443/tcp on 71.90.208.44
Discovered open port 8080/tcp on 71.90.208.44
Discovered open port 8443/tcp on 71.90.208.44
Discovered open port 9080/tcp on 71.90.208.44
Discovered open port 9110/tcp on 71.90.208.44
Completed Connect Scan at 11:24, 53.50s elapsed (1000 total ports)

- - - Updated - - -

Nice website, too.

**seerofvoid420** · 19-01-17

I'd love to tear it down, time permitting, but college has just started up again, and along with work, finding time to do so might be challenging.

I went ahead and did some packet sniffing client-side, and a packet containing my public IP gets sent from the world manager server at some point. I assume this is the WM telling the client, "Hey, zones are here". Seeing your port scan only report the 1 service accessible leads me to believe there is indeed a network issue (likely the pseudo-corporate infrastructure).

You mentioned making a network map, and until I find the time to make an image based one, here's this.

Code:

 Charter Modem ---> pfSense --> VLAN10 --> Nortel Gigabit Switch --> VLAN10 --> ESXi cluster --> ESXI vSwitch --> PServer VM
  71.90.208.44    172.16.0.0/16  --------------------------------------------------------------------------------> 172.16.21.1

Yeah, there's a few points of failure, but I can assure you from the Nortel switch to the VM is wide open, so the issue is likely pfSense. I may DMZ the VM and bring the Windows firewall up, eliminate the pfSense setup.
The list of open ports in pfSense to the PServer VM: 9000, 9005, 9010, 9015, 9101, 9110, 9115, 9120, 9122, 9124, 9126 (literally every service port). Can't imagine why none of them showed up on your port scan, here's my scan from t1shopper.com:

Spoiler:

This is all I had time to fuss with tonight, but I can actually do some testing tomorrow night. I'll keep this thread updated.

**Pagefault404** · 19-01-17

"I'd love to tear it down, time permitting, but college has just started up again, and along with work, finding time to do so might be challenging. "

Shit, that sucks.

All things considered, it would probably be MUCH better from a learning perspective, to try and keep your network as intact as possible and figure this out (I know I recommended tearing it down which contradicts this) but after giving it some thought, I feel this would ultimately be the best approach for you and your goals of network configuration.

One thing I would scrutinize heavily in your network is the ESXi virtual switching for your VM cluster. Because virtual machines aren't physical machines, they don't (always) operate under the same logic that physical machines do. You might need to ensure that traffic on the fiesta service ports are getting passed along at all stops. From what I can see, things seem okay and hypothetically should work.

Spoiler:

A DMZ for the Pserver would be the best case for now, just to get the server confirmed working. Something is off somewhere, connectivity wise. From what little I have seen of your setup, it looks like you want to do something semi-professional with this. So a DMZ may not be a good idea long-term, as the Odin files have weird security issues (from what I understand).

Please do keep this posted and if you need me to do anything else externally, let me know.

**seerofvoid420** · 19-01-17

Up to this point, I've never had any issues with the ESXi switching. I may try putting another physical NIC in the ESXi host and doing a physical passthrough to the VM (where the VM would have full control over physical hardware). I will also try moving the VM to the other host in the cluster to see if it's related to the hardware in the host.
The only issue is adding another physical NIC requires migrating all the VMs to the other host, which takes an hour or so.

I've also just passed a full port range through in pfSense (9000 through 9300) to see if that makes a difference. If you could do another port scan now, please post the new results. I've also disabled the firewall on the VM, again, to see if it makes a difference.

EDIT: Tried connecting from a 4g hotspot with my laptop, still getting "MuM" error.
I just noticed the VM is using an ESXi VMXNet3 virtual NIC. I've switched it to emulate an Intel E1000 NIC instead. Hopefully something changes.

EDIT2: Now I can't get in at all. I reset the firewall rule back to what it was before, still nothing. This looks like pfSense is at fault for any issues I have. I'll fuss with it more tonight.

**seerofvoid420** · 24-01-17

I've left this alone for a few days to clear my head, and instead worked on the website for the pserver (which btw is looking really nice). Hopefully this means I can come at the issue with less frustration. Tomorrow night I have a good bit of free time, and I'm going to put the VM in a DMZ. I'll update this post as I go.

And yes, I'm still not done translating all the PHP to work with PDO, so there are plenty of errors on the site.

**Pagefault404** · 26-01-17

Look a lot different than the site I saw when I did the port scan. Good stuff.

**seerofvoid420** · 10-02-17

I've since given up on getting my port forwarding to work (for now) and moved to a VPN solution. Since the pserver is running on Server 2016 (upgraded from 2008 r2), I just installed the RRAS (Routing and Remote Access) role. Using an SDK for C#, the launcher creates a Windows VPN connection to my server. The VPN clients sit on a small VLANed subnet, and are handed address leases from a DHCP server running on another Server 2016 instance. The only traffic this VPN routes is from the client, so users still have internet access, and gameplay works flawlessly.

This at least fills the requirement of not using Hamachi, and with how seamless it is integrated (only about 30 lines of code to add the VPN, configure it and connect, and an average time until connected of less than 1 second) it's as if there was no VPN.
If anyone wants details of this setup, PM me.

EDIT: I've since had a VM crash and lost all my source code, reverted the pserver back to 2008r2, and given up on the VPN method (since the code was all lost

)
I'm still looking for help on this issue.

**seerofvoid420** · 10-08-17

Bumping, issue is still present :(

[NA - 2011] "Map Under Maintenance" when trying to connect from Public IP

Thread Tools

[NA - 2011] "Map Under Maintenance" when trying to connect from Public IP

Re: [NA - 2011] Zone server won't bind to IP

Re: [NA - 2011] Zone server won't bind to IP

Re: [NA - 2011] Zone server won't bind to IP

Re: [NA - 2011] "Map Under Maintenance" when trying to connect from Public IP

Re: [NA - 2011] "Map Under Maintenance" when trying to connect from Public IP

Re: [NA - 2011] "Map Under Maintenance" when trying to connect from Public IP

Re:

Re: [NA - 2011] "Map Under Maintenance" when trying to connect from Public IP

Re: [NA - 2011] "Map Under Maintenance" when trying to connect from Public IP

Re: [NA - 2011] "Map Under Maintenance" when trying to connect from Public IP

Re: [NA - 2011] "Map Under Maintenance" when trying to connect from Public IP

Re: [NA - 2011] "Map Under Maintenance" when trying to connect from Public IP

Re: [NA - 2011] "Map Under Maintenance" when trying to connect from Public IP

Re: [NA - 2011] "Map Under Maintenance" when trying to connect from Public IP

Advertisement