Connecting - Revision history

Haru: Marked as outdated - contains info about old txt conf files

2016-09-16T18:41:43Z

Marked as outdated - contains info about old txt conf files

HerculesWikiEditor: <replacetext_editsummary>

2016-04-25T12:45:43Z

<replacetext_editsummary>

Semperverus: /* Port Forwarding */

2016-02-20T09:49:27Z

‎Port Forwarding

Semperverus: /* Basics of the three servers */

2016-02-20T09:48:19Z

‎Basics of the three servers

Nobigdeal: /* Configuring Hercules for Use */ Changed file names to use Hercules version and fixed SQL statement to change server password.

2013-09-28T00:59:03Z

‎Configuring Hercules for Use: Changed file names to use Hercules version and fixed SQL statement to change server password.

Mysterious at 04:18, 13 January 2013

2013-01-13T04:18:38Z

Ind at 04:14, 13 January 2013

2013-01-13T04:14:27Z

Mysterious: Created page with "This article covers taking the configuration steps to ensure a successful connection to your servers. You are required to know the in and outs of your OS, as well as what a [[..."

2013-01-13T03:48:52Z

Created page with "This article covers taking the configuration steps to ensure a successful connection to your servers. You are required to know the in and outs of your OS, as well as what a [[..."

New page

This article covers taking the configuration steps to ensure a successful connection to your servers. You are required to know the in and outs of your OS,
as well as what a [[wikipedia:Local area network|LAN IP]] and a [[wikipedia:Wide area network|WAN IP]] are.

==Basics of the three servers==
===Login Server===
The login server handles all login packets from the client. The client sees the login server first and connects to it first. The login server listens on the
port 6900 by default and usually reads data from the login table. The login server connects directly to the character server and passes it's information
to it once the client has successfully logged in. If your login server won't connect, your players cannot login in, but can play.

===Character Server===
The character server handles all character selection and character loading for the map server. The character server receives commands to primarily display characters
once the client has logged in. The character server listens on the port 6121 by default. It also handles the loading and saving of most character data.
If the character server becomes disconnected, character data saving is not possible.

===Map Server===
The map server handles all map functions, including, but not limited to, mob functions, map functions, NPC loading and unloading, as well as NPC processing.
the map server is your bread and butter and allows people to play on your server. It listens on the port 5121 by default.

If the character server becomes disconnected from your map server, it's likely the mapserver will disconnect everyone from it. This is not the case when the
MySQL server loses its connection to Hercules, as Hercules currently does not restore this connection.

==Configuring Hercules for use==
After you have finished [[compiling]] Hercules, you can set it up for use. There will be four files that we will concentrate on. Any settings we change in these files should '''always''' be moved to the relevant import folder files. If your compiler hasn't already made a copy of the {{svn|trunk/conf/import-tmpl}} folder and named it /trunk/conf/import do that now.

=====Using the /conf/import/ folder ({{svn|trunk/conf/import-tmpl/}})=====
In this folder, you can 'import' your settings into each of the respected files. All you need is each parameter. When you do this, your settings will never be overwritten when you need
to update your SVN, as the import folder is built once. You can throw all of your settings in here and they will remain as they are, and will read AFTER the
main settings, which means these settings will take priority.

===Step 1. Interserver Communication Passwords===
First, you will need to set an intercommunication password and user. This is one of the most important steps to securing your server.

In order for the char-server to accept commands and packets from the login server, and for the map-server to accept commands and packets from the char-server they have to 'log-in' to each other, using the Server Communication passwords.
You MUST set these to something other than defaults, but you can set them to random characters, as long as they are the same in the three places they appear in, which are: {{svn|trunk/conf/char_athena.conf}}, {{svn|trunk/conf/map_athena.conf}} and your login sql table.
They are defaulted to s1/p1, and '''MUST''' be changed.

Changes must be made to the import folder to ensure proper upgradability. A good habit to get into when working with SVN.
Simply copy and paste the lines you wish to alter from the .conf file to the relevant .txt file in the import folder.
Your trunk/conf/import/char_athena.txt ''and'' trunk/conf/import/map_athena.txt files should look as follows, with ''no'' changes made to {{svn|trunk/conf/char_athena.conf}} or {{svn|trunk/conf/map_athena.conf}}: <br />
<code><pre>// Server Communication username and password.
userid: [new user]
passwd: [new password]</pre></code>

Your login table should match. Use this SQL query (or make the changes using your favourite SQL gui):
<code><pre>UPDATE login
use databasename_rag;
set `userid` = "[new user]", `user_pass` = "[new password]" where `account_id` = 1;</pre></code>

After the user and password is set, you can move on down the page.

===Step 2. {{svn|trunk/conf/login_athena.conf}}===
Usually there is nothing to be done here in terms on connection.
You may want to edit your login_port to something other than default, but it must be an unused port by your OS.

You can find this out by starting all the services that you need on the server and issuing the following commands to your console:

'''If using Windows:'''<br />
Goto Start, then click 'Run'. Type 'cmd' and press enter. Run the following command:
<code><pre>netstat -a</pre></code>
'''If using *nix:'''
<code><pre>$ lsof -i</pre></code>

Once you have selected a port if you're going to change it, your trunk/conf/import/login_athena.txt file should look as follows, with ''no'' changes made to {{svn|trunk/conf/login_athena.conf}} (again just copy pasting the lines we want to change from one file to the other): <br />
<code><pre>// Login Server Port
login_port: [new port]</pre></code>

===Step 3. {{svn|trunk/conf/char_athena.conf}}===
This file sets parameters for the char-server to read.
When you open this up, there are a few things we need to do in here.

Firstly we should name our server:

When setting server_name, be sure to not use spaces as it says.
<code><pre>// Server name, use alternative character such as ASCII 160 for spaces.
// NOTE: Do not use spaces in the name, or guild emblems won't work client-side!
server_name: [new server name]</pre></code>

<code><pre>// Wisp name for server: used to send wisp from server to players (between 4 to 23 characters)
wisp_server_name: [new server name]</pre></code>

Usually, Hercules will auto-detect your external and internal IP if the IP fields are [[comments|commented out]], but let's go ahead and remove the two slashes (//) from login_ip and char_ip.

The login_ip will point to the IP address where the login server will be running. Usually this is the localhost, or 127.0.0.1.
If the login-server is to be located on the same network as the char-server (but on a different PC), use the LAN IP of the login server's machine.
If you are running a dedicated machine in a datacenter, or you know your IP is not going to change, you can set this to your WAN IP.

<code><pre>// 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: [new ip here]</pre></code>

The char_ip parameter will '''ALWAYS''' be your WAN IP, no exceptions. This is the IP that the char-server will accept connections with.

<code><pre>// Character Server IP
// The IP address which clients will use to connect.
// Set this to what your server's public IP address is.
char_ip: [your wan ip here]</pre></code>

If you changed the login_port in login_athena.conf, this setting here will need to match it.
<code><pre>// Login Server Port
login_port: [new port]</pre></code>

Make sure to make any changes in the import folder as always.

===Step 4. {{svn|trunk/conf/map_athena.conf}}===
This file sets parameters for the map-server to read.

The char_ip will point to the IP address where the login server will be running. Usually this is the localhost, or 127.0.0.1.
If the char-server is to be located on the same network as the map-server (but on a different PC), use the LAN IP of the char server's machine.
If you are running a dedicated machine in a datacenter, or you know your IP is not going to change, you can set this to your WAN IP.

<code><pre>// 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: [new ip here]</pre></code>

The map_ip parameter will '''ALWAYS''' be your WAN IP, no exceptions. This is the IP that the map-server will accept connections with.

<code><pre>// 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: [your wan ip here]</pre></code>

Make sure to make any changes in the import folder as always.

===Step 5. {{svn|trunk/conf/inter_athena.conf}}===
About midway down this file, you will find your SQL settings. These will be set as accordingly.

* The 'sql.db' settings control what the login-server reads for it's database settings.
* Hostname is the IP of the SQL server.
* Username is the username you use to login. For security, this should '''NEVER''' be root!
* Password is the password that the user will login with.
* The database is set to whatever the database name will be. Usually, this is just 'ragnarok'.

If you make any changes in here, copy paste the lines you change into /conf/import/inter_athena.txt and modify them there.

==Starting Hercules==
When you're all done configuring Hercules, you can start it up. You can do this by simply running each of the three servers, or athena-start.

==Client Side==
===Diff your client===
See [[Hexing#Creating_custom_RagRE_client_using_a_DIFF_patcher|Hexing]].

===Data Folder===
#Download the most recent data folder [http://svn6.assembla.com/svn/ClientSide/ here].
#Edit your [[Clientinfo|clientinfo.xml]] as needed.

===Connect===
Execute your exe.

==Trouble Shooting==
Its always best to post in the [http://hercules.ws/board/forum/31-client-side-support/ client support] sub-forum for things that go wrong with the client, and [http://hercules.ws/board/forum/14-general-server-support/ server support] sub-forum for things that go wrong with Hercules connecting or if errors pop up in your server log.

===CHARACTER_INFO size error!!===
To fix this, locate the src/common folder and open mmo.h in notepad. Find the following line:
<code><pre>#ifndef PACKETVER
#define PACKETVER 20110609
</pre>
Edit this Part, put:
<pre>#define PACKETVER YOURCLIENTDATE</pre>

So if my client was 2011-10-25aRagexeRE it would look like:
<pre>#define PACKETVER 20111025</pre>

[[Category:Configuration]]

← Older revision		Revision as of 18:41, 16 September 2016
Line 1:		Line 1:
		+	{{outdated}}
		+
		+
	This article covers taking the configuration steps to ensure a successful connection to your servers. You are required to know the in and outs of your OS,		This article covers taking the configuration steps to ensure a successful connection to your servers. You are required to know the in and outs of your OS,
	as well as what a [[wikipedia:Local area network\|LAN IP]] and a [[wikipedia:Wide area network\|WAN IP]] are.		as well as what a [[wikipedia:Local area network\|LAN IP]] and a [[wikipedia:Wide area network\|WAN IP]] are.

@@ Line 22: / Line 22: @@
 ===Port Forwarding===
-If you intend to let your players play from an external internet connection, you ''must'' forward ports 6900, 6121, and 5121 respectively. Simply forwarding port 6900 is not enough to allow clients to connect, and traffic will not be passed solely through your login server.
+If you intend to let your players play from an external internet connection, you ''must'' forward ports 6900, 6121, and 5121 respectively in your router's control panel. Simply forwarding port 6900 is not enough to allow clients to connect, and traffic will not be passed solely through your login server, even though they can communicate with one another internally on your localhost address.
 ==Configuring Hercules for use==

@@ Line 156: / Line 156: @@
 ==Trouble Shooting==
-Its always best to post in the [http://hercules.ws/board/forum/31-client-side-support/ client support] sub-forum for things that go wrong with the client, and [http://hercules.ws/board/forum/14-general-server-support/ server support] sub-forum for things that go wrong with Hercules connecting or if errors pop up in your server log.
+Its always best to post in the [http://herc.ws/board/forum/31-client-side-support/ client support] sub-forum for things that go wrong with the client, and [http://herc.ws/board/forum/14-general-server-support/ server support] sub-forum for things that go wrong with Hercules connecting or if errors pop up in your server log.
 ===CHARACTER_INFO size error!!===

@@ Line 19: / Line 19: @@
 If the character server becomes disconnected from your map server, it's likely the mapserver will disconnect everyone from it. This is not the case when the
 MySQL server loses its connection to Hercules, as Hercules currently does not restore this connection.
 ==Configuring Hercules for use==

@@ Line 21: / Line 21: @@
 ==Configuring Hercules for use==
-After you have finished [[compiling]] Hercules, you can set it up for use. There will be four files that we will concentrate on. Any settings we change in these files should '''always''' be moved to the relevant import folder files. If your compiler hasn't already made a copy of the {{git|conf/import-tmpl}} folder and named it /trunk/conf/import do that now.
+After you have finished [[compiling]] Hercules, you can set it up for use. There will be four files that we will concentrate on. Any settings we change in these files should '''always''' be moved to the relevant import folder files. If your compiler hasn't already made a copy of the {{git|conf/import-tmpl}} folder and named it /conf/import do that now.
 =====Using the /conf/import/ folder ({{git|conf/import-tmpl/}})=====
@@ Line 32: / Line 32: @@
 In order for the char-server to accept commands and packets from the login server, and for the map-server to accept commands and packets from the char-server they have to 'log-in' to each other, using the Server Communication passwords.
-You MUST set these to something other than defaults, but you can set them to random characters, as long as they are the same in the three places they appear in, which are: {{git|conf/char_athena.conf}}, {{git|conf/map_athena.conf}} and your login sql table.
+You MUST set these to something other than defaults, but you can set them to random characters, as long as they are the same in the three places they appear in, which are: {{git|conf/char-server.conf}}, {{git|conf/map-server.conf}} and your login sql table.
 They are defaulted to s1/p1, and '''MUST''' be changed.
 Changes must be made to the import folder to ensure proper upgradability. A good habit to get into when working with GIT.
 Simply copy and paste the lines you wish to alter from the .conf file to the relevant .txt file in the import folder.
-Your trunk/conf/import/char_athena.txt ''and'' trunk/conf/import/map_athena.txt files should look as follows, with ''no'' changes made to {{git|conf/char_athena.conf}} or {{git|conf/map_athena.conf}}: <br />
+Your /conf/import/char_conf.txt ''and'' /conf/import/map_conf.txt files should look as follows, with ''no'' changes made to {{git|conf/char-server.conf}} or {{git|conf/map-server.conf}}: <br />
 <code><pre>// Server Communication username and password.
 userid: [new user]
@@ Line 43: / Line 43: @@
 Your login table should match. Use this SQL query (or make the changes using your favourite SQL gui):
-<code><pre>UPDATE login
+<code><pre>use databasename_rag;
-use databasename_rag;
+UPDATE login
 set `userid` = "[new user]", `user_pass` = "[new password]" where `account_id` = 1;</pre></code>
 After the user and password is set, you can move on down the page.
-===Step 2. {{git|conf/login_athena.conf}}===
+===Step 2. {{git|conf/login-server.conf}}===
 Usually there is nothing to be done here in terms on connection.
 You may want to edit your login_port to something other than default, but it must be an unused port by your OS.
@@ Line 61: / Line 61: @@
 <code><pre>$ lsof -i</pre></code>
-Once you have selected a port if you're going to change it, your trunk/conf/import/login_athena.txt file should look as follows, with ''no'' changes made to {{git|conf/login_athena.conf}} (again just copy pasting the lines we want to change from one file to the other): <br />
+Once you have selected a port if you're going to change it, your /conf/import/login_conf.txt file should look as follows, with ''no'' changes made to {{git|conf/login-server.conf}} (again just copy pasting the lines we want to change from one file to the other): <br />
 <code><pre>// Login Server Port
 login_port: [new port]</pre></code>
-===Step 3. {{git|conf/char_athena.conf}}===
+===Step 3. {{git|conf/char-server.conf}}===
 This file sets parameters for the char-server to read.
 When you open this up, there are a few things we need to do in here.
@@ Line 98: / Line 98: @@
 char_ip: [your wan ip here]</pre></code>
-If you changed the login_port in login_athena.conf, this setting here will need to match it.
+If you changed the login_port in login-server.conf, this setting here will need to match it.
 <code><pre>// Login Server Port
 login_port: [new port]</pre></code>
@@ Line 104: / Line 104: @@
 Make sure to make any changes in the import folder as always.
-===Step 4. {{git|conf/map_athena.conf}}===
+===Step 4. {{git|conf/map-server.conf}}===
 This file sets parameters for the map-server to read.
@@ Line 126: / Line 126: @@
 Make sure to make any changes in the import folder as always.
-===Step 5. {{git|conf/inter_athena.conf}}===
+===Step 5. {{git|conf/inter-server.conf}}===
 About midway down this file, you will find your SQL settings. These will be set as accordingly.
@@ Line 135: / Line 135: @@
 * The database is set to whatever the database name will be. Usually, this is just 'ragnarok'.
-If you make any changes in here, copy paste the lines you change into /conf/import/inter_athena.txt and modify them there.
+If you make any changes in here, copy paste the lines you change into /conf/import/inter_conf.txt and modify them there.
 ==Starting Hercules==

@@ Line 25: / Line 25: @@
 =====Using the /conf/import/ folder ({{git|conf/import-tmpl/}})=====
 In this folder, you can 'import' your settings into each of the respected files. All you need is each parameter. When you do this, your settings will never be overwritten when you need
-to update your SVN, as the import folder is built once. You can throw all of your settings in here and they will remain as they are, and will read AFTER the
+to update your GIT, as the import folder is built once. You can throw all of your settings in here and they will remain as they are, and will read AFTER the
 main settings, which means these settings will take priority.
@@ Line 35: / Line 35: @@
 They are defaulted to s1/p1, and '''MUST''' be changed.
-Changes must be made to the import folder to ensure proper upgradability. A good habit to get into when working with SVN.
+Changes must be made to the import folder to ensure proper upgradability. A good habit to get into when working with GIT.
 Simply copy and paste the lines you wish to alter from the .conf file to the relevant .txt file in the import folder.
 Your trunk/conf/import/char_athena.txt ''and'' trunk/conf/import/map_athena.txt files should look as follows, with ''no'' changes made to {{git|conf/char_athena.conf}} or {{git|conf/map_athena.conf}}: <br />