Packet Obfuscation disconnect char, able to login

[callyyprain 0]

Use latest Hercules. 

 

Packet Ob-: 2

Tried 20140205 and 20150513, Local fine but WAN access prompt failed to connect to server and

 

[status]: Request for connection of ##### (ip: 118.100.130.###).

[Notice]: Authentication accepted (account: #####, id: 2000009, ip: 118.100.130.###)

[status]: Connection of the account '#####' accepted.

[info]: Closed connection from '118.100.130.###'.

 

 

Packet Ob-: 1 

Tried 20140205 and 20150513, success.

 

Question: How to solve above issue when Enabled Packet obfuscation?

[Samuel 83]

When you enable packet ob, you need to diff your client with the keys for that client which you can look in src/map/packets.h

[callyyprain 0]

Hi Samuel, is that possible, be done with NEMO? It's been years I never manual diff. lol

 

Currently I set it to 1 cuz 0 will also deny all login.

[Ridley 295]

When you enable packet ob, you need to diff your client with the keys for that client which you can look in src/map/packets.h

 

Hi Samuel, is that possible, be done with NEMO? It's been years I never manual diff. lol

 

Currently I set it to 1 cuz 0 will also deny all login.

 

The client has it's keys set by default, if you change them you need to set them. You have 3 options.

1. Disable Packet Obfruscation in both, your client and your server config

2. Keep the Packet Obfruscation on both enabled

3. Use the Diff Samuel mentioned to set custom keys

 

From what you wrote it sounds like you had the obfruscation enabeld on your server, but diffed the client to disable them

[callyyprain 0]

Hi Riddley, I NEMO-ed Ragexe both 20140205 and 20150513 with recommended and some minor changes (Title, menu bar, official stuff, etc) but I did not disable PacketObs though.

 

I do not know which is the option to enable it, or is NEMO capable enabling it?

 

+----------------------------------------------------------------------+

8 Custom Window Title

9 Disable 1rag1 type parameters (Recommended)

13 Disable Ragexe Filename Check (Recommended)

15 Disable HShield (Recommended)

17 Enable Official Custom Fonts

19 Enable Title Bar Menu

23 Enable /who command (Recommended)

24 Fix Camera Angles (Recommended)

33 Always Call SelectKoreaClientInfo() (Recommended)

34 Enable /showname (Recommended)

35 Read Data Folder First

36 Read msgstringtable.txt (Recommended)

37 Read questid2display.txt (Recommended)

38 Remove Gravity Ads (Recommended)

39 Remove Gravity Logo (Recommended)

40 Restore Login Window (Recommended)

41 Disable Nagle Algorithm (Recommended)

43 Always Use Email for Char Deletion

44 Translate Client (Recommended)

46 Use Normal Guild Brackets (Recommended)

47 Use Ragnarok Icon

48 Use Plain Text Descriptions (Recommended)

49 Enable Multiple GRFs (Recommended)

50 Skip License Screen

53 Use Ascii on All LangTypes (Recommended)

63 Use Official Cloth Palettes

64 @ Bug Fix (Recommended)

65 Load Custom lua file instead of iteminfo*.lub (Recommended)

73 Remove Hourly Announce (Recommended)

74 Increase Screenshot Quality

76 Enforce Official Login Background

84 Remove Serial Display (Recommended)

85 Show Cancel To Service Select

88 Allow space in guild name

90 Enable DNS Support (Recommended)

91 Disconnect to Login Window

97 Cancel to Login Window (Recommended)

103 Disable Auto follow

209 Enable Mail Box for All LangTypes

213 Disable Help Message on Login (Recommended)

215 Increase Map Quality

218 Show Exp Numbers

225 Show Register Button

+----------------------------------------------------------------------+

[Hafflex 0]

By default it is enabled, unless you use a diffed exe and it was being disabled by that person.

 

It's: Disable Packet Encryption below Disable Nagle Algorithm.

[hemagx 69]

This is not a packet obfuscation issue, you will see a packet error if it was.

probably some bad network configure.

[Aurora 4]

 

When you enable packet ob, you need to diff your client with the keys for that client which you can look in src/map/packets.h

 

Hi Samuel, is that possible, be done with NEMO? It's been years I never manual diff. lol

 

Currently I set it to 1 cuz 0 will also deny all login.

 

The client has it's keys set by default, if you change them you need to set them. You have 3 options.

1. Disable Packet Obfruscation in both, your client and your server config

2. Keep the Packet Obfruscation on both enabled

3. Use the Diff Samuel mentioned to set custom keys

 

From what you wrote it sounds like you had the obfruscation enabeld on your server, but diffed the client to disable them

Hello Ridley, does this mean if I use the client with no broken keys based on the website(which I forgot) and enabled packet obfuscation on both client and the server without changing anything in the packets, packet obfuscation would work? Unless I want to use custom keys then I need to diff the client with it and put it as well on src(which I cannot make it to work after several times)

[Ridley 295]

 

 

 

 

When you enable packet ob, you need to diff your client with the keys for that client which you can look in src/map/packets.h

>

Hi Samuel, is that possible, be done with NEMO? It's been years I never manual diff. lol

 

Currently I set it to 1 cuz 0 will also deny all login.ockquote>

The client has it's keys set by default, if you change them you need to set them. You have 3 options.

1. Disable Packet Obfruscation in both, your client and your server config

2. Keep the Packet Obfruscation on both enabled

3. Use the Diff Samuel mentioned to set custom keys

 

From what you wrote it sounds like you had the obfruscation enabeld on your server, but diffed the client to disable them

>

Hello Ridley, does this mean if I use the client with no broken keys based on the website(which I forgot) and enabled packet obfuscation on both client and the server without changing anything in the packets, packet obfuscation would work? Unless I want to use custom keys then I need to diff the client with it and put it as well on src(which I cannot make it to work after several times)

If using the client with default keys there is no edit needed. It is enabled on server by default, and the server knows the client is using by default (ofc you need to set your clientversion in mmo.h)

[Aurora 4]

 

 

 

When you enable packet ob, you need to diff your client with the keys for that client which you can look in src/map/packets.h

 

> 

Hi Samuel, is that possible, be done with NEMO? It's been years I never manual diff. lol

 

Currently I set it to 1 cuz 0 will also deny all login.

ockquote>  

The client has it's keys set by default, if you change them you need to set them. You have 3 options.

1. Disable Packet Obfruscation in both, your client and your server config

2. Keep the Packet Obfruscation on both enabled

3. Use the Diff Samuel mentioned to set custom keys

 

From what you wrote it sounds like you had the obfruscation enabeld on your server, but diffed the client to disable themlockquote> Hello Ridley, does this mean if I use the client with no broken keys based on the website(which I forgot) and enabled packet obfuscation on both client and the server without changing anything in the packets, packet obfuscation would work? Unless I want to use custom keys then I need to diff the client with it and put it as well on src(which I cannot make it to work after several times)

 

 

 

If using the client with default keys there is no edit needed. It is enabled on server by default, and the server knows the client is using by default (ofc you need to set your clientversion in mmo.h)

Alright, thanks! Will test this later

Edited October 13, 2016 by Aurora

[callyyprain 0]

I got Ragexe from themon and Ossi. I think both non-diff exe? Then NEMO-ed as per previous reply. I couldn't find 'Packet Obs' option.

 

Hi Hemagx,

I was on Debian, set nameserver 8.8.8.8 and 8.8.4.4 in resolv.conf

Set static then

IP Add...

Netmask...

Network...

broadcast...

gateway..

 

Then ifdown and ifup, ifconfig check working fine. I even able to setup 1 RE 1 PRE and bind to same NIC IP. 192.168.X.X.

 

Please enlighten me if you could, I couldn't find any suspicious stuff. It only happens to WAN client. LAN is fine.

 

Network.conf is

client{ "WAN NO-IP:subnetmask", "local IP:subnetmask" }

server connect { "local IP:subnetmask"}

trusted {"local IP:subnetmask"}

 

 

UPDATE: Today my WAN friend connect with (20140205) packet obs enabled, working fine. Oh dear! What happen. Last 2days I must set it to 1 (optional).

Edited October 13, 2016 by callyyprain