Jump to content

[ZERO] Unable to make first connection


thecapn

Recommended Posts

Posted

Hello everyone,

I'm attempting to get my private server running for the first time, I am hosting an install on a Ubuntu 12.04LTS VirtualBox session. The compile, setup, configuration and everything from the Generic Linux Install went just fine and I've gotten to the point where I can run realmd & mangosd but can not select a realm. I've heard this called Realm Loop?

Steps I've taken:

1) Set realmlist.wtf

set realmlist localhost

2) Edited realmlist mysql table to listen on 0.0.0.0

mysql> select id, address, port FROM realmlist;
+----+---------+------+
| id | address | port |
+----+---------+------+
| 1 | 0.0.0.0 | 8085 |
+----+---------+------+
1 row in set (0.00 sec)

3) Set mangosd.conf mysql username & pass, port = 8085, BindIP = 0.0.0.0

LoginDatabaseInfo      = "127.0.0.1;3306;mangos;xxx;realmd"
WorldDatabaseInfo      = "127.0.0.1;3306;mangos;xxx;mangos"
CharacterDatabaseInfo    = "127.0.0.1;3306;mangos;xxx;characters"

LoginDatabaseConnections   = 15
WorldDatabaseConnections   = 15
CharacterDatabaseConnections = 15
MaxPingTime         = 300
WorldServerPort       = 8085
BindIP            = "0.0.0.0"

4) Set realmd.conf the same (Port 3724)

LoginDatabaseInfo    = "127.0.0.1;3306;mangos;xxx;realmd"
LogsDir        = "/opt/mangos-server/logs"
PidFile        = ""

MaxPingTime      = 300
RealmServerPort    = 3724
BindIP         = "0.0.0.0"

5) Created account

I have confirmed that there are services listening on the host at 3724 & 8085

netstat -a | grep LISTEN
tcp    0   0 localhost:mysql     *:*           LISTEN   
tcp    0   0 *:3724         *:*           LISTEN   
tcp    0   0 *:8085         *:*           LISTEN

In the end, since the VirtualBox session uses a NAT configured network it uses port forwarding for incoming data connections. The 8085 and 3724 are mapped and work. I've heard the issue comes with binding to 0.0.0.0. If that's the case what IP would I want to bind on my Virtual Host? Would I want to use localhost or the reserved internal IP on the server (10.0.2.15).

I have to run to work, but I'll check this thread in ~8hrs to answer any questions. I hope I haven't overlooked something silly.

Posted

do you get any errors/warnings in console window?

try to change connection type in virtual box from nat to bridged. you will be able to set static address for a virtual machine.

i'm not sure what's wrong with setting static ip address in "BindIP". i've always set it for a static address of a virtual machine.

Posted

For the binding IP parts you want to bind that to the network adapter that is hosting realmd and mangosd.

The database is the only thing that uses 127.0.0.1 (localhost).

Also, with the realm IP in the database im pretty sure that needs to be set, it cant be 0.0.0.0 and 127.0.0.1 would only work if you were playing from inside the virtualbox but since you are connecting from the host O/s it needs to also be the network IP of the virtualbox.

Hope this makes sense.

Posted

Well toots. I had tried using the Bridged Adapter prior and still couldn't make connections. I was not getting any console errors and was unsure how to troubleshoot further.

I really appreciate the reality check guys, you are life savers.

For anyone stumbling into this...

SOLUTION

- Use Bridged Adapter Network in VirtualBox, Promiscuous mode = Allow All

- Set all Bind IPs (MySQL && conf files) to the private IP (172.16.1.xx in my case)

- Update realmlist.wtf on client within host machine

- Play

Extra junk I did...

If you need to test whether the computer is listening, use the netstat command above. The port will be "LISTENING"

If you want to test inbound connections use netcat (nc -l <port>) on Linux, then use puTTY to connect to the port using Telnet from Host (Windows 7 in my case)

Thanks again guys!

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy Terms of Use