WAN Char-server timeout

[Discount Ninja]

I've had a similar problem in the past, this time I've run into a dead end.

 

I'm using client 2013-08-07 that's been diffed. It matches the same dates in mmo.h, which I have recompiled. I haven't edited the packet lines though. Server is running Linux, CENTOS.

 

My LAN computers can connect to the server just fine. No errors. The server confirms this in the logs.

 

The client XML is pointing to the right area.As the WAN client can log-on to the login server. It can see how many people are connected. However, it times out at they try to go to the char server. The server shows no logs or reports the issue of any WAN connection.

 

This isn't the first server I've used. I have confirmed that the ports are setup correctly, and the firewall is setup. I can even telnet, using the ports 5121, 6121, 6900 to the server using the WAN computer. The WAN computer has access to all of those ports on the server, and the rAthena servers all say they have a strange packet(s) coming from the WAN computer.

 

I still think it's a config issue but I haven't found something that's worked.

Char_conf.txt

login_ip: 192.168.0.10 //LAN
char_ip: WANIP //WAN

Map_conf.txt
char_ip: 192.168.0.10 //LAN
//bind_ip: 192.168.0.10 -not needed?
map_ip: WANIP //WAN IP

Subnet_athena.conf
subnet: 255.0.0.0:WANIP:WANIP
subnet: 255.0.0.0:192.168.0.10:192.168.0.10
I have also used:
subnet: 255.255.255.0:WANIP:WANIP
subnet: 255.255.255.0:192.168.0.10:192.168.0.10

I had a different server working. So I'm really at a loss on what's going on. Any ideas?

Edited December 5, 2013 by Discount Ninja

[Discount Ninja]

I really hope someone can help me with this. I’ve spend a long time trying to figure out the problem and I've narrowed it down. Using the command “lsof –i” I can see what programs are listening to what ports and addresses. It took some tinkering to get all of the servers to listen appropriately.

(key)
PROGRAM    PID  USER        FD  TYPE  DEVICE SIZE/OFF NODE  NAME
clock-app  2866 ragnarok   21u  IPv4  99207      0t0  TCP 192.168.0.10:51311->weather.noaa.gov:http (ESTABLISHED)
login-ser 11080 ragnarok    5u  IPv4  99226      0t0  TCP localhost:38355->localhost:mysql (ESTABLISHED)
login-ser 11080 ragnarok    6u  IPv4  99228      0t0  TCP *:6900 (LISTEN)
login-ser 11080 ragnarok    7u  IPv4  99272      0t0  TCP 192.168.0.10:6900->192.168.0.10:50175 (ESTABLISHED)
char-serv 11084 ragnarok    4u  IPv4  99270      0t0  TCP *:6121 (LISTEN)
char-serv 11084 ragnarok    5u  IPv4  99271      0t0  TCP 192.168.0.10:50175->192.168.0.10:6900 (ESTABLISHED)
char-serv 11084 ragnarok    6u  IPv4  99274      0t0  TCP localhost:6121->localhost:48537 (ESTABLISHED)
map-serve 11088 ragnarok    5u  IPv4  99263      0t0  TCP *:5121 (LISTEN)
map-serve 11088 ragnarok    6u  IPv4  99273      0t0  TCP localhost:48537->localhost:6121 (ESTABLISHED)

As you can see from the table, all of the servers are connected and listening to the right ports.

 

The real issue is with the char-server. I’m looking at a packet sniffer and it says the program appropriately connects to the login server at the WAN IP. However, after that initial connection, the client is told to look locally on the network that it isn’t a part of. The client attempts server’s LAN address, not the WAN IP. I've tried to force the WAN subnet only and char-server to wan only. It still tells the client to go to the LAN ip.

 

Does anyone know how to get the server to tell the client to keep on the WAN IP?

 

[Discount Ninja]

For anyone using Linux, the HOSTNAME of your computer DOES MATTER. Especially if your using a domain or no-ip.

 

Edit your domain with root access: "nano /etc/sysconfig/network"

Edit the HOSTNAME to your choosing, save and exit.

 

Then restart your network to ensure your changes last after a reboot.

"/etc/init.d/network restart"

[Winz]

Hello, I have some suggestions, which works perfectly with me.

 

first, I would suggest you to use:

Char_conf.txt
 
login_ip: 127.0.0.1
char_ip: WANIP //WAN
 
Map_conf.txt
char_ip: 127.0.0.1
map_ip: WANIP //WAN IP
 
Subnet_athena.conf:
just don't do anything with it. some problems comes from not proper editing of this file.

default subnet.conf:

 

// Subnet support file
// Format is:
// subnet: net-submask:char_ip:map_ip
// you can add more than one subnet

subnet: 255.0.0.0:127.0.0.1:127.0.0.1

[Discount Ninja]

Yea, every post about this sort of thing says the same thing. If you look at the posts you can see those configs are correct. The problem was every time I could connect and it would forward the port to a LAN that didn't exist outside of the network. That problem was with the Linux network configuration that was installed by default.Solution is in the third post.

 

But as for the subnet, my server has 3 that connect to it.

[Winz]

well, that's insane. I've never happen that problem.

 

well then, maybe you can rename this thread to a [guide] ?

[Discount Ninja]

I know, it took me over a week to figure that out.

 

I'm not sure that this would be that useful as a guide, I haven't seen that many people with a similar issue.

[Winz]

probably. so that by the next time people get the same problem, IFF they search first, they don't have to post the problem. but, only if they do.