Jump to content

Dark Theme was set as default for all members. Please report any issues here.

  • 0
KaitoKid

How to support packet encryption in 2013-08-07a Ragexe

Question

Hey guys,

 

Need another help using packet encryption with client 2013-08-07a Ragexe

I'm getting another unsupported packet (packet 0x7f9f (0x02e5), 19 bytes received)

 

Here's the applied diff for the client:

 

  • @ Bug Fix
  • Always Call SelectKoreaClientInfo()
  • Cancel to Login Window
  • Custom Window Title
  • Disable 1rag1 type parameters
  • Disable HShield
  • Disable Hallucination Wavy Screen
  • Disable Nagle Algorithm
  • Disable Ragexe Filename Check
  • Enable /showname
  • Enable 64k Hairstyle
  • Enable DNS Support
  • Enable Mail Box for All langtypes
  • Enable Monster Tables
  • Enable Multiple GRFs
  • Enable Official Custom Fonts
  • Enable Title Bar Menu
  • Enforce Official Login Background
  • Extend Chat Box
  • Extend Chat Room Box
  • Extend PM Box
  • Fix Camera Angles
  • Fix Tetra Vortex
  • Ignore Missing File Error
  • Ignore Missing Pallete Error
  • Increase Attack Display
  • Increase Headgear ViewID
  • Increase Zoom Out 50%
  • Only First Login Background
  • Packet First Key Encryption [58AA359A]
  • Packet Second Key Encryption [55F86C1E]
  • Packet Third Key Encryption [3F094C49]
  • Cancel to Login Window

 

confbattleclient.conf

// Whether to enable the official packet obfuscation support (good vs WPE)// 0: disabled// 1: optional (not recommended) -- identifies whether it is required// 2: enabled (recommended)packet_obfuscation: 2

 

clientinfo.xml

<?xml version="1.0" encoding="euc-kr"?><clientinfo><servicetype>korea</servicetype><servertype>primary</servertype>   <connection>      <display>Xypher RO</display>      <balloon>Xypher Ragnarok Online</balloon>      <desc>Xypher Ragnarok Online</desc>      <address>127.0.0.1</address>      <port>6900</port>      <version>27/version>      <langtype>12</langtype>      <registrationweb>google.com</registrationweb>        <aid>            <admin>2000000</admin>			<admin>2000001</admin>			<admin>2000002</admin>        </aid>        <loading>            <image>loadingscreen01.jpg</image>        </loading>   </connection></clientinfo>

 

 

Any ideas why I'm getting the error? thanks

Share this post


Link to post
Share on other sites

14 answers to this question

Recommended Posts

  • 0

Packet First Key Encryption [58AA359A]

Packet Second Key Encryption [55F86C1E]

Packet Third Key Encryption [3F094C49]

Make sure you change those keys in SRC/map/packets.h and recompile

(Show packets.h if you have done it already)

Share this post


Link to post
Share on other sites
  • 0

Packet First Key Encryption [58AA359A]

Packet Second Key Encryption [55F86C1E]

Packet Third Key Encryption [3F094C49]

Make sure you change those keys in SRC/map/packets.h and recompile

(Show packets.h if you have done it already)

 

Did I did this right?

 

#if PACKETVER >= 20130807	packetKeys(0x58AA359A, 0x55F86C1E, 0x3F094C49); /* Thanks to Shakto */#endif

Share this post


Link to post
Share on other sites
  • 0

 

Packet First Key Encryption [58AA359A]

Packet Second Key Encryption [55F86C1E]

Packet Third Key Encryption [3F094C49]

Make sure you change those keys in SRC/map/packets.h and recompile

(Show packets.h if you have done it already)

 Did I did this right?

 

#if PACKETVER >= 20130807	packetKeys(0x58AA359A, 0x55F86C1E, 0x3F094C49); /* Thanks to Shakto */#endif
Yes, recompile now, and restart.

Share this post


Link to post
Share on other sites
  • 0

hi, all got same problem but with client 20141022

 

i was setting like @@Dastgir say

 

but still get error like this

 

[Warning]: clif_parse: Received unsupported packet (packet 0x21dd (0x73c1), 19 b
ytes received), disconnecting session #3.

 

My Setting

 

Packet.h

#if PACKETVER >= 20141022
    packetKeys(0x290551EA,0x2B952C75,0x2D67669B); /* YomRawr */
#endif

client.conf

 

 // 0: disabled
// 1: optional (not recommended) -- identifies whether it is required
// 2: enabled (recommended)
packet_obfuscation: 2

 

please tell me how to fix this

Edited by melv0

Share this post


Link to post
Share on other sites
  • 0

hi, all got same problem but with client 20141022 i was setting like @@Dastgir say but still get error like this [Warning]: clif_parse: Received unsupported packet (packet 0x21dd (0x73c1), 19 b

ytes received), disconnecting session #3. My Setting Packet.h

#if PACKETVER >= 20141022

    packetKeys(0x290551EA,0x2B952C75,0x2D67669B); /* YomRawr */

#endif

client.conf

 

 // 0: disabled

// 1: optional (not recommended) -- identifies whether it is required

// 2: enabled (recommended)

packet_obfuscation: 2

 please tell me how to fix this
The error message shows that packet was encrypted, but with a wrong key, double check the packet key input by NEMO(shouldn't contain 0x on NEMO), also, have you recompiled the server?

Share this post


Link to post
Share on other sites
  • 0

do you mean when i input key on nemo should be like this

 

packet 1 [290551EA]

packet 2 [2B952C75]

packet 3 [2D67669B]

 

 

without 0x??

Edited by melv0

Share this post


Link to post
Share on other sites
  • 0

do you mean when i input key on nemo should be like this

 

packet 1 [290551EA]

packet 2 [2B952C75]

packet 3 [2D67669B]

 

 

without 0x??

Yes, exactly

Share this post


Link to post
Share on other sites
  • 0

 

do you mean when i input key on nemo should be like this

 

packet 1 [290551EA]

packet 2 [2B952C75]

packet 3 [2D67669B]

 

 

without 0x??

Yes, exactly

but when i input packet key without 0x i got error " Packet Frist Key Encryption: Patch Cancelled - Key Not Changed"

how about that?

i must use 0x but when I used it, the number shown is less a digit from the original. Example i copy this key 0x290551ea on nemo but in nemo show like this 0290551e??

 

what must i do??

Share this post


Link to post
Share on other sites
  • 0

 

 

do you mean when i input key on nemo should be like this

 

packet 1 [290551EA]

packet 2 [2B952C75]

packet 3 [2D67669B]

 

 

without 0x??

Yes, exactly
but when i input packet key without 0x i got error " Packet Frist Key Encryption: Patch Cancelled - Key Not Changed"how about that?i must use 0x but when I used it, the number shown is less a digit from the original. Example i copy this key 0x290551ea on nemo but in nemo show like this 0290551e?? what must i do??
You should not use those 3 patches unless you want to modify the packet keys to some custom.

Just diff without those and it will work fine(I just saw those are default 20141022 packet keys)

Those Patches are for custom packet keys...

Share this post


Link to post
Share on other sites
  • 0

i try what u say i didn't diff that patches

 

but when i login stuck on loading screen 3%??

 

 

@edit

 

sorry my mystake on grf

 

Thanks A loot @datsgir



one question more...

 

splash.dll working on this client? (20141022)

Edited by melv0

Share this post


Link to post
Share on other sites
  • 0

old bump @Dastgir

hello sir, old bump request, figuring out client 2015-11-04a ragexe with latest git. and i believe packetkeys transfer to src/map/packet_keys_main.h

 

clientinfo = korea and primary 


Packet First Key Encryption [325ADCCA]
Packet Second Key Encryption [10A8A9AF]
Packet Third Key Encryption [3403EC37]

 

ps. i try to change different keys but same result, i did hundred of recheck in nemo also

 

 

Yellow: can't connect to server

Red: can't create character to server.

 

EDIT: FIXED.
when i try different client that dosn't support doram it works perfectly.
 

Untitled.png

Edited by wOni
fixed

Share this post


Link to post
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.   Restore formatting

  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.

Loading...

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.