Initiate Mage
- Joined
- Oct 30, 2011
- Messages
- 0
- Reaction score
- 4
the link to PKG Extractor (needed to unpack/repack) pkg files, is broken.
reupload?
reupload?
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature currently requires accessing the site using the built-in Safari browser.
the link to PKG Extractor (needed to unpack/repack) pkg files, is broken.
reupload?
Take this
You must be registered to see links
(Credits Eperty123)
Sorry for my bad english
Someone have an Skype to help me ? because i'm french and i need more details
can i run this server files on public ip ? coz, i just see everybody use vmware to be able playing this game
Why can not use Wan Ip?@Eperty123
@Hycker
Wan Connecting fixed After many hours of testing it is done.
First you need to run a query on FFMember Table tb_user
Code:INSERT INTO "public"."tb_user" ("mid", "password", "pwd", "idnum", "byauthority", "pvalues", "firstlogindate", "billingrule", "status", "regdate", "lastlogindate", "memberid", "clientip", "updatetime", "bonus", "char_id", "sel_chk") VALUES ('username', '5f4dcc3b5aa765d61d8327deb882cf99', '5f4dcc3b5aa765d61d8327deb882cf99', '2', '0', '0', '2015-10-16 16:20:01', '0', '0', '2015-10-08 16:20:20+01', '2015-10-22 16:20:27+01', '2', '192.168.0.25', '2015-10-23 16:07:09', '0', '50000001', '0');
Match the Data To your Own like Username and Password that is (MD5) also your Char_id i.e 500000001.
After this add you Wan IP to FFAccount - worlds
Leave FFDB1 - serverstatus as your 192.168.0.xx or other lan ip (Do not change to Wan Ip)
Use my patcher on WorldServer101 and 102
View attachment 154109
Update you client connect.ini to wanip
edit:
Forward your ports on Home Router if standard 6543,5567,5568
hit start and enjoy
Cheers evestu tt1:
P.s Please Keep my Releases at Ragezone.
but i change wan ip do not ping 10021 portAre you sure that 192.168.0.40 is external ip?
Tapatalkkal küldve az én LG-D802 eszközömről
View attachment Test.log.0412.rarAre you sure that 192.168.0.40 is external ip?
Tapatalkkal küldve az én LG-D802 eszközömről
but i change wan ip do not ping 10021 port
View attachment 156552
This is change to wan ip ZoneServer log
Do not use same port on external and internal only for ZoneServer, after 30 minutes i'm reading tutorial from Eperty123 and evestu and the result is like this :
Eperty123 Session :
1. Install Centos x64
2. Disable SELinux if you have trouble with restorecon command also change language to [your lang].ISOxxx] see Eperty123 Config
3. Make DB and give permission to any user ex. eperty123 or what ever you want
4. disable firewall ( just for dev need, you can see port with netstat -tulpn and create iptables rule )
5. Import all database script (*.sql), you can follow Eperty123 tut's
6. Now you are done with one session and server ready to start but later.
Evestu Session :
1. Patch your WorldServer, i will explain this, evestu patch will replace defult IP to 127.0.0.1 and see Eperty123 tuts there is DEDEDE address, find that address replace with your converted ip in this case HEX IP needed use tools from Eperty And Evestu.
2. execute WorldServer and open the log file ( Test.xxxx) you can see WorldServer will reading IP from table serverstatus, change ip
in the database to your ip do not touch internal ip
3. Change IP inside World Table (FFAccount if i'm not wrong with this).
4. start again this time use ./start and open the log again, you can see the WorldServer still listen 0.0.0.0 ip, stop the server and open
the WorldServer with any Hex Editor again find 127.0.0.1 in Hex (7F000001) so many address inside WorldServer with the same address just update first one and the second one, save and exit upload again to you server, start the server again you can see with netstat -tulpn WorldServer will run twice with your ip, below is from my dev server :
tcp 0 0 192.168.36.128:5567 0.0.0.0:* LISTEN 1774/./WorldServer1
tcp 0 0 0.0.0.0:35648 0.0.0.0:* LISTEN 1803/./ZoneServer10
tcp 0 0 192.168.36.128:5568 0.0.0.0:* LISTEN 1788/./WorldServer1
tcp 0 0 0.0.0.0:18624 0.0.0.0:* LISTEN 1741/./TicketServer
tcp 0 0 192.168.36.128:5570 0.0.0.0:* LISTEN 1774/./WorldServer1
tcp 0 0 192.168.36.128:5571 0.0.0.0:* LISTEN 1788/./WorldServer1
tcp 0 0 192.168.36.128:10021 0.0.0.0:* LISTEN 1803/./ZoneServer10
tcp 0 0 0.0.0.0:7654 0.0.0.0:* LISTEN 1760/./MissionServe
tcp 0 0 0.0.0.0:6543 0.0.0.0:* LISTEN 1750/./LoginServer
tcp 0 0 192.168.36.128:10320 0.0.0.0:* LISTEN 1803/./ZoneServer10
this will work without 1 hour restart and you can manage this server to be online perfectly.
5. Change WorldServer port on Internal ip session with another port, no problem with ip you can use 127.0.0.1, coz this is only internal communication.
Remember to Hexing WorldServer and ZoneServer after you patch it with Evestu tools, sometime will work after patch and sometime won't work, to make it work perfectly you must find DEDEDE and 2 7F000001 in the first search and second search with your hex tools.
Sorry for my bad english, if you have trouble i can help remotely.
You must be registered to see links
now you can use that db config, and for hexing WorldServer you can try Offset 0023CB70 (DEDEDE), 0023CD60 - 0023CD70 (7F 00 00 01) also for ZoneServer 006A03C0, 006A0230 - 240 without evestu patch, with evestu patch you will found so many address with 7F000001.Yes they will not connect to your ip, lets see what i got from your log :
Cannot assign requested address 122.100.166.118:10021
403,2016/04/12 18:59:20,SOCKET 33: closed.
404,2016/04/12 18:59:20,[SJFramework.cc:111],ERROR: #Network# CSJFramework::InitNetwork -- Network Initial Error.
you can see ? you ZoneServer cannot communicate with WorldServer, i will give you my database set :
FFAccount database :
1010 518FF-CH1 122.100.166.118 5567 0 800 1 003.005.01.04 0 0 15 100
1020 518FF-CH2 122.100.166.118 5568 0 800 1 003.005.01.04 0 0 200 500
FFDB1 Database :
1021 ZoneServer 122.100.166.118 10022 127.0.0.1 10022 0 0
1011 ZoneServer 122.100.166.118 10021 127.0.0.1 10021 0 0
1010 WorldServer 122.100.166.118 5567 122.100.166.118 5570 0 0
1020 WorldServer 122.100.166.118 5568 122.100.166.118 5571 0 0
-2 MissionServer none -1 127.0.0.1 7654 1460438752 0
now you can use that db config, and for hexing WorldServer you can try Offset 0023CB70 (DEDEDE), 0023CD60 - 0023CD70 (7F 00 00 01) also for ZoneServer 006A03C0, 006A0230 - 240 without evestu patch, with evestu patch you will found so many address with 7F000001.
you ip 122.100.166.118 = 7A64A676
I think this is very clear and hope solving your problem, don't forget to edit your client connect.ini :
Server=122.100.166.118,6543
there you go complete step for you.
PS:
dont use this config for port forwarding, if you use port forwarding change to your local ip for all bold character
I'm not english... i dont uderstand