Jump to content
  • 0

Client (or not) problem


altronrain

Question


  • Group:  Members
  • Topic Count:  5
  • Topics Per Day:  0.00
  • Content Count:  15
  • Reputation:   1
  • Joined:  10/14/18
  • Last Seen:  

Hello!
I'm stuck with server & client configure and need some help.
What i've done (i think that more information i provide, faster we can solve this problem):

1. Made a fresh VM install under XenServer with CentOS minimal 7.5 onboard.
2. Using tutorial i got latest (yesterday) rathena server.
3. Made some changes to src/packets.hpp and renewal.hpp (uploaded)
packets.hpp

    #define PACKETVER 20130807
#endif

renewal.hpp

#ifndef CONFIG_RENEWAL_HPP
#define CONFIG_RENEWAL_HPP

//quick option to disable all renewal option, used by ./configure
#define PRERE
#ifndef PRERE

4. Configured char_, map_, inter_athena.conf files (uploaded) 

char_athena.conf

// Server Communication username and password.
userid: rathena
passwd: ragnarok

// Server name, use alternative character such as ASCII 160 for spaces.
// NOTE: Do not use spaces or any of these characters which are not allowed in
//       Windows filenames \/:*?"<>|
//       ... or else guild emblems won't work client-side!
server_name: rAthena

// Wisp name for server: used to send wisp from server to players (between 4 to 23 characters)
wisp_server_name: Server

// Login Server IP
// The character server connects to the login server using this IP address.
// NOTE: This is useful when you are running behind a firewall or are on
// a machine with multiple interfaces.
login_ip: 127.0.0.1

// The character server listens on the interface with this IP address.
// NOTE: This allows you to run multiple servers on multiple interfaces
// while using the same ports for each server.
//bind_ip: 127.0.0.1

// Login Server Port
login_port: 6900

// Character Server IP
// The IP address which clients will use to connect.
// Set this to what your server's public IP address is.y
char_ip: 192.168.88.235

// Character Server Port
char_port: 6121

map_athena.conf

// Interserver communication passwords, set in account.txt (or equiv.)
userid: rathena
passwd: ragnarok

// Character Server IP
// The map server connects to the character server using this IP address.
// NOTE: This is useful when you are running behind a firewall or are on
// a machine with multiple interfaces.
char_ip: 192.168.88.235

// The map server listens on the interface with this IP address.
// NOTE: This allows you to run multiple servers on multiple interfaces
// while using the same ports for each server.
//bind_ip: 127.0.0.1

// Character Server Port
char_port: 6121

// Map Server IP
// The IP address which clients will use to connect.
// Set this to what your server's public IP address is.
map_ip: 192.168.88.235

// Map Server Port
map_port: 5121

inter_athena.conf

// Global SQL settings
// overridden by local settings when the hostname is defined there
// (currently only the login-server reads/obeys these settings)

// MySQL Login server
login_server_ip: localhost
login_server_port: 3306
login_server_id: rathena4444
login_server_pw: verysecretpasswd
login_server_db: rathena4444_rag
login_codepage:
login_case_sensitive: no

ipban_db_ip: localhost
ipban_db_port: 3306
ipban_db_id: rathena4444
ipban_db_pw: verysecretpasswd
ipban_db_db: rathena4444_rag
ipban_codepage:

// MySQL Character server
char_server_ip: localhost
char_server_port: 3306
char_server_id: rathena4444
char_server_pw: verysecretpasswd
char_server_db: rathena4444_rag

// MySQL Map Server
map_server_ip: localhost
map_server_port: 3306
map_server_id: rathena4444
map_server_pw: verysecretpasswd
map_server_db: rathena4444_rag

// MySQL Log Database
log_db_ip: localhost
log_db_port: 3306
log_db_id: rathena4444
log_db_pw: verysecretpasswd
log_db_db: rathena4444_log
log_codepage:
log_login_db: loginlog


5. Made changes to mariadb login table according to char_ map_ conf user/pass
6. Compiled server with this options:

./configure --enable-64bit --with-MYSQL_LIBS=/usr/lib64/libmysqlclient.so && make clean && make server --enable-packetver=20130807

7. Made permanent changes to firewalld (uploaded --list-all)
 

public (active)
  target: default
  icmp-block-inversion: no
  interfaces: eth1
  sources: 
  services: ssh dhcpv6-client
  ports: 6900/tcp 5121/tcp 6121/tcp 4500/tcp
  protocols: 
  masquerade: no
  forward-ports: 
  source-ports: 
  icmp-blocks: 
  rich rules: 
	


So, server part seems to work well. 0 errors during startup.
 

Client part:

Downloaded Official kRo latest (or not for nowadays) from here: http://www.mediafire.com/file/3ysd21j25i3457e/Official+kRO+Client+(Last+Update+2017-07-05).rar
Then i tried to use 2013-08-07 Full client from user themon (if i didnt mistake). That included .exe, lua, hercules.grf, option changer exe. 
(Then i tried my own default 2013-08-07Ragexe with some diff wariations). What's the problem:
I cant see even tries for connect from client (in console). tcpdump on CentOS also says dat 0 packets recieved on port 6900. Windows with client said some strange info:

at first tries my client seems to connect to korean ip's. Then after some plays with exe and diffs i cant see nothing in Wireshark. So it even didnt try to send packets, and Fails To Connect to Server.
I tried to add clientinfo (using 36,46,45 versions with 192.168.88.235 ip - no result). But rathena itself dont need packet_db.txt anymore, and seems not to read clientinfo. Idk where is a mistake. I need help. 
It seems it's a client side problem mostly. I want to play RO already. if i'm right and this is a client< could someone ultimatively give me 20130807 full client as a solution.

map_athena.conf

firewall.txt

inter_athena.conf

char_athena.conf

packets.hpp

renewal.hpp

Link to comment
Share on other sites

4 answers to this question

Recommended Posts

  • 0

  • Group:  Members
  • Topic Count:  3
  • Topics Per Day:  0.00
  • Content Count:  351
  • Reputation:   263
  • Joined:  09/08/13
  • Last Seen:  

  https://mega.nz/#!lI90TTxI!6l2xp20o9gdDrpsKBohMaR46PZqMtHosYSWLlK5kO88

You should download file connect_log.mix and copy it to the game folder. After connection attempt module will create log file connect_log.txt with info.

  • Upvote 1
Link to comment
Share on other sites

  • 0

  • Group:  Members
  • Topic Count:  5
  • Topics Per Day:  0.00
  • Content Count:  15
  • Reputation:   1
  • Joined:  10/14/18
  • Last Seen:  

A-ha! 
Using different variations of .exe in connect_log.txt i get 127.0.0.1:6900
Where should i change that to my server address (clientinfo.xml seems not affecting)

Link to comment
Share on other sites

  • 0

  • Group:  Members
  • Topic Count:  3
  • Topics Per Day:  0.00
  • Content Count:  351
  • Reputation:   263
  • Joined:  09/08/13
  • Last Seen:  

Maybe you have clientinfo.xml in the data folder or EXE takes clientinfo.xml from another GRF.

Edited by Functor
  • Upvote 1
Link to comment
Share on other sites

  • 0

  • Group:  Members
  • Topic Count:  5
  • Topics Per Day:  0.00
  • Content Count:  15
  • Reputation:   1
  • Joined:  10/14/18
  • Last Seen:  

RAGE MODE activated!
Thank you! Who know that opening clientinfo inside grf editor and saving changes didn't work ?
Ofc i should repack grf with NEW file. 
Eh, my incredible stupidity
 

 

so, tomorrow i should get rid of clif_parse and unknown packetver errors ?

 

solved! 

  • Upvote 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...