PDA

View Full Version : login Server can not register more than one server?


zhangshen147
08-20-2016, 11:10 AM
I have multiple IP addresses, so I put them are used up, the system is proxmox, I establish a server and login server, normal operation and at the same time eqemulator my local login server registration, when I run a second EMU server, registered to the local login server, server list shows two servers, but the landing to go is the second server, the first server do not know where to go, this is why? The login server cannot support multiple local server registration? (I'm sure the IP address of the 2 server has been set up correctly.)
pls help me~
Some people can provide help, thank you very much!

Drajor
08-20-2016, 11:21 PM
Is this correct?

You are running 1 world server which connects two 2 login servers (public LS and a local LS). The local LS is running on the same IP as the world server.

Maze_EQ
08-21-2016, 12:05 AM
Nah 2 worlds connecting to 1 login is what hes doing.

DanCanDo
08-21-2016, 06:24 PM
I tried that once, just piddling around with two boxes on private lan, with one login,
but router only let me forward the necessary ports to one box, so that didn't pan
out.

zhangshen147
08-21-2016, 10:25 PM
Is this correct?

You are running 1 world server which connects two 2 login servers (public LS and a local LS). The local LS is running on the same IP as the world server.

Yes, and now EMU can register at the same time on the 2 login server!


<!-- Loginserver information. Defaults shown -->
<loginserver1>
<host>login.eqemulator.net</host>
<port>5998</port>
<account></account>
<password></password>
</loginserver1>

<loginserver2>
<host>x.x.x.x</host>
<port>5998</port>
<account></account>
<password></password>
</loginserver2>

zhangshen147
08-21-2016, 10:27 PM
I tried that once, just piddling around with two boxes on private lan, with one login,
but router only let me forward the necessary ports to one box, so that didn't pan
out.

i have three internet ip addr. don't need NAT。

image
08-22-2016, 12:31 PM
this isn't very clear you quote the guy who says you are trying to run 1 world server for 2 login servers, but you mention your original problem being 2 worlds connecting to one login server, where the world servers reside on the same box.

2 world servers on the same box.. routing is the first problem, you sure UDP is using the right interface going out of your box? The logic for the 'resolved' IP/hostname on the login server typically fell to the 'worldaddress' field in eqemu_config.xml -- if you don't provide the worldaddress, the login server will guess based on what you connect with (hence routing).

zhangshen147
08-23-2016, 04:07 AM
this isn't very clear you quote the guy who says you are trying to run 1 world server for 2 login servers, but you mention your original problem being 2 worlds connecting to one login server, where the world servers reside on the same box.

2 world servers on the same box.. routing is the first problem, you sure UDP is using the right interface going out of your box? The logic for the 'resolved' IP/hostname on the login server typically fell to the 'worldaddress' field in eqemu_config.xml -- if you don't provide the worldaddress, the login server will guess based on what you connect with (hence routing).

Sorry, is my description of the problem. I am using KVM virtual machine:
No.1 EMU server and local Login Server in VM1
No.2 EMU server in VM2.
VM Host VM1 VM2 Are using different Internet IP address。
VM Host IP address : XXX.XXX.253.2
VM1 IP address : XXX.XXX.253.3
eqemu_config.xml
<address>XXX.XXX.253.3</address>
<localaddress>XXX.XXX.253.3</localaddress>

<!-- Loginserver information. Defaults shown -->
<loginserver1>
<host>login.eqemulator.net</host>
<port>5998</port>
<account></account>
<password></password>
</loginserver1>

<loginserver2>
<host>127.0.0.1</host>
<port>5998</port>
<account></account>
<password></password>
</loginserver2>
login.ini
[database]
host = 127.0.0.1
port = 3306
db =
user =
password =
subsystem = MySQL

[options]
unregistered_allowed = TRUE
reject_duplicate_servers = TRUE
trace = TRUE
world_trace = FALSE
dump_packets_in = FALSE
dump_packets_out = FALSE
listen_port = 5998
local_network = xxx.xxx.253.

VM2 IP address : XXX.XXX.253.4
eqemu_config.xml
<address>XXX.XXX.253.4</address>
<localaddress>XXX.XXX.253.4</localaddress>

<!-- Loginserver information. Defaults shown -->
<loginserver1>
<host>login.eqemulator.net</host>
<port>5998</port>
<account></account>
<password></password>
</loginserver1>

<loginserver2>
<host>XXX.XXX.253.3</host>
<port>5998</port>
<account></account>
<password></password>
</loginserver2>

image
08-23-2016, 07:44 AM
so again your eqemu_config.xml doesn't contain a worldaddress, it should be below localaddress in most cases

<localaddress>...</localaddress>
<worldaddress>..</worldaddress>

worldaddress should be the external IP that you have out to the web. See if defining those in both EMU servers helps.

If not you probably have to consider getting packet captures so people can see the activity going to/from port 9000 on the client.

zhangshen147
08-23-2016, 11:58 PM
so again your eqemu_config.xml doesn't contain a worldaddress, it should be below localaddress in most cases

<localaddress>...</localaddress>
<worldaddress>..</worldaddress>

worldaddress should be the external IP that you have out to the web. See if defining those in both EMU servers helps.

If not you probably have to consider getting packet captures so people can see the activity going to/from port 9000 on the client.

wow....This is a setting that I don't know, I'm going to test it. Thank you very much

zhangshen147
08-25-2016, 03:24 AM
so again your eqemu_config.xml doesn't contain a worldaddress, it should be below localaddress in most cases

<localaddress>...</localaddress>
<worldaddress>..</worldaddress>

worldaddress should be the external IP that you have out to the web. See if defining those in both EMU servers helps.

If not you probably have to consider getting packet captures so people can see the activity going to/from port 9000 on the client.

This method is not successful.