Please help, internet and network can't both connect, Using Mangos.

[Darkfrost101]

Hi all!

I'm hosting a server using Mangos, and I got a small problem:

I set it up so people can connect via the internet, first just using my net ip (That worked, but I got the realm loop, they got on fine), then I tried using no-ip (Same problem)

I think i know what the problem is, but I have no idea how to fix it.

You see, when I got to my ip on my network, (192.168.0.14) It goes to the 'Make an account page', but when I got to my ip on the internets (Either my real ip or my no-ip ip), it goes to my router's login panel (192.168.0.1).

I've tryed setting my realmlist.wtf to..
192.168.0.1 - Wouldnt connect
192.168.0.14 - Realm loop
127.0.0.1 - Realm loop
My real ip - (Can't remember :P)
My no-ip ip - (Can't remeber)
My other no-ip ip - Wouldnt connect

None of these worked.

Hope someone can help, thanks.

[MentaL]

[Darkfrost101]

Meh, set realmlist localhost does realmloop too. Please help :)

[Darkfrost101]

Ok, I worked out why this happens, but no fix yet. Except maybe a proxy would work.

It happens because when I set up port forwarding on my router, it only redirects requests from the internet, not the network.

So, when everyone is going to my comp on the network, (192.168.0.14), people on my network are still going to my router (192.168.0.1)

Hmm.. wonder how I can fix this :/

[THE_Wolfman]

Sounds like your router dosn't fully support loopback, which gives a router the ability to loop LAN requests to WAN addresses thet are forwarded back to LAN addresses. A number of home/office routers suffered this issue when they started to become popular, but in most cases the problem has been solved by firmware releases from each manufacturer.

I would recommend you check the router manufacturer's website for a firmware update.

The reason the problem becomes complicated with a MaNGOS server, is that you actually make two connections... one to the realmd daemon (to log on) and then another to the mangosd daemon (which hosts the game world). So, in order to host an internet connection you need the WAN address to appear in your realmlist (used by realmd - which provides address for the second connection to mangosd), but your LAN cannot loop network requests to that address. However all is not lost...


Your Temporary Fix: 'Trick' your LAN computers into thinking your server's LAN IP is really a WAN IP.


To do this, we will make use of your hosts file (\Windows\System32\drivers\etc on a Win XP Box) Take the default value:

127.0.0.1 localhost
(which directs your PC to access the 127.0.0.1 IP whenever the name localhost is used)


On your server, add you no-ip domain name (not an IP address) to the end:

127.0.0.1 localhost server.no-ip.com
(which directs your PC to access 127.0.0.1 when either the name localhost or server.no-ip.com is used)


On your other LAN PCs, add your server's LAN IP followed by it's no-ip domain name:

127.0.0.1 localhost
192.168.0.14 server.no-ip.com
(which directs your PC to access the 127.0.0.1 IP whenever the name localhost is used, and 192.168.0.14 whenever the name server.no-ip.com is used)


In this way, all machines that access server.no-ip.com can resolve an accessible IP according to where they are:
Server sees 127.0.0.1
LAN PC sees 192.168.0.14
Internet sees (whatever your WAN IP is)

And because your server and LAN PC traffic remains on the LAN, the loopback issue is avoided.


Reboot and test!


Note: Replace the "server.no-ip.com" used in my examples with your own no-ip domain name.

[aceindy]

Yeah, this should do it;
I spend many topics on how DNS will resolve any loopback failure, but it seems nobody cares to read it :-/
(that is the reason I don't bother to answer anymore either)