Yeah I put my no-ip Adress but nothing :s so after some test. Before the test, I was thinking the server was kicking me out. but I think I just cannot log on char-server. if I put -- <<address>192.168.2.20</address> I see me connect on the login. if I put -- <<address>riourik.no-ip.com</address> I don't see me connect on login. with 192.168.2.20 cannot log on char. so hard to get it. don't know where I miss something. on wan everything work number 1 but not on lan.
I follow it but cannot play in local my server lan ip is 192.168.2.20 and my lan ip is 192.168.2.14
login screen
but after I have on my client :
"failed to connect to server"
I will quote you my network files just in case I did something wrong
// Network configuration file
/*
* List here any LAN subnets this server is in.
* Example:
* - char- (or map-) server's IP in LAN is 192.168.0.10
* - Public IP is 198.51.100.37
* If the list contains "192.168.0.10:255.255.255.0", any clients connecting
* from the same 192.168.0.0/24 network will be presented with the LAN IP
* (192.168.0.10) in the server list, rather than the public IP (198.51.100.37).
*/
lan_subnets: (
"127.0.0.1:255.0.0.0",
"riourik.ddns.net:255.255.255.0",
"192.168.2.14:255.255.255.0",
)
/*
* List here any IP ranges a char- or map-server can connect from.
* A wildcard of "0.0.0.0:0.0.0.0" means that server connections are allowed
* from ANY IP. (not recommended).
*/
allowed: (
"0.0.0.0:0.0.0.0",
"192.168.2.20:255.255.255.0",
"192.168.2.14:255.255.255.0",
)
/*
* List here any IP ranges a char- or map-server can connect from. These ranges
* will also be excluded from the automatic ipban in casee of password failure.
* Any entry present in this list is also automatically included in the
* allowed IP list.
* Note: This may be a security threat. Only edit this list if you know what
* you are doing.
*/
trusted: (
"127.0.0.1:255.0.0.0",
"192.168.2.14:255.255.255.0",
)
