Packet Parser|Tokenizer (unknown/unsupported packets)

Forum closed. All further discussion to be discussed at https://github.com/OpenKore/

Moderators: Moderators, Developers

Message
Author
iFive
Noob
Noob
Posts: 1
Joined: 13 Jan 2010, 12:17
Noob?: Yes

Re: Packet Parser|Tokenizer (unknown/unsupported packets)

#21 Post by iFive »

Hello!!

CAn Anyone help us on the error we encountered.

Unknown packet-07FF
Unknown packet-0008

How can we resolve this?

Thanks!

kLabMouse
Administrator
Administrator
Posts: 1301
Joined: 24 Apr 2008, 12:02

Re: Packet Parser|Tokenizer (unknown/unsupported packets)

#22 Post by kLabMouse »

iFive wrote:Hello!!

CAn Anyone help us on the error we encountered.

Unknown packet-07FF
Unknown packet-0008

How can we resolve this?

Thanks!
pRO?

go to DarkMoon forum.

Technology
Super Moderators
Super Moderators
Posts: 801
Joined: 06 May 2008, 12:47
Noob?: No

Re: Packet Parser|Tokenizer (unknown/unsupported packets)

#23 Post by Technology »

iFive wrote:Hello!!

CAn Anyone help us on the error we encountered.

Unknown packet-07FF
Unknown packet-0008

How can we resolve this?

Thanks!
you did not post the EXACT warnings,
because of the insufficient nature of the information that you have supplied we will NOT be able to determine the EXACT cause,
we can make assumptions but that would only give us a pool of hypothetical causes,
in other words, your report failed, so we simply CAN NOT help you. (not that we don't want to... we simply can't)

The template (see first post) is there for a reason, to help you to post the EXACT information we need, so better follow it...

But especially for you i will make an assumption,
with the accuracy of 99% I can tell you that the 2nd warning is caused by your own ignorance. you might want to extract the packet lengths of the latest client
One ST0 to rule them all? One PE viewer to find them!
One ST_kRO to bring them all and in the darkness bind them...

Mount Doom awaits us, fellowship of OpenKore!

Rheiyh
Noob
Noob
Posts: 6
Joined: 14 Jan 2010, 19:55
Noob?: No

Re: Packet Parser|Tokenizer (unknown/unsupported packets)

#24 Post by Rheiyh »

Server:Pro(Valhalla)
Servertype:openkore_ready
Packet: Packet Tokenizer: Unknown Switch 07FF & 02B9

*Tried Changing rev.packets and server.txt but still no effect, still same error.
Programs used: Openkore Packet Length Extractor, RO TOOLS

can anyone help? until now i havent resolved this. Thnx

Technology
Super Moderators
Super Moderators
Posts: 801
Joined: 06 May 2008, 12:47
Noob?: No

Re: Packet Parser|Tokenizer (unknown/unsupported packets)

#25 Post by Technology »

Rheiyh wrote:Server:Pro(Valhalla)
Servertype:openkore_ready
Packet: Packet Tokenizer: Unknown Switch 07FF & 02B9

*Tried Changing rev.packets and server.txt but still no effect, still same error.
Programs used: Openkore Packet Length Extractor, RO TOOLS

can anyone help? until now i havent resolved this. Thnx
post the extracted packet lengths in an attachment to your post

btw, wtf @ Servertype:openkore_ready
One ST0 to rule them all? One PE viewer to find them!
One ST_kRO to bring them all and in the darkness bind them...

Mount Doom awaits us, fellowship of OpenKore!

Rheiyh
Noob
Noob
Posts: 6
Joined: 14 Jan 2010, 19:55
Noob?: No

Re: Packet Parser|Tokenizer (unknown/unsupported packets)

#26 Post by Rheiyh »

sorry dude, stupid me..
server type: 22 port:6900

*heres the Recvpackets that i got from RO tools
Attachments
recvpackets-pro.txt.txt
recvpackets produced using RO TOOLS.
(8.34 KiB) Downloaded 1566 times

kali
OpenKore Monk
OpenKore Monk
Posts: 474
Joined: 04 Apr 2008, 10:10

Re: Packet Parser|Tokenizer (unknown/unsupported packets)

#27 Post by kali »

I remember when we wrote the error message that pops up, that you should post the errors.txt itself. Not because we wanted you to do a lot of work, but because we included in the error message a lot of the stuff we need to debug the error.

Unfortunately, my mind reading abilities still haven't evolved that much so yeah I'm a failure for not knowing what you meant :(
Got your topic trashed by a mod?

Trashing topics is one click, and moving a topic to its proper forum is a lot harder. You expend the least effort in deciding where to post, mods expend the least effort by trashing.

Have a nice day.

Technology
Super Moderators
Super Moderators
Posts: 801
Joined: 06 May 2008, 12:47
Noob?: No

Re: Packet Parser|Tokenizer (unknown/unsupported packets)

#28 Post by Technology »

Rheiyh wrote:sorry dude, stupid me..
server type: 22 port:6900

*heres the Recvpackets that i got from RO tools
like i thought, you don't have 07FF in it, so you had warning:
Packet Tokenizer: Unknown switch: 07FF
if you extracted the packet lengths yourself, you have extracted those of an old client, update your RO client and extract again.

02B9 -> this packet has been implemented in kore, its the hotkeys packet, you shouldn't be getting a warning with this packetswitch

@kali, yea, maybe we need warnings.txt or something because people don't know that it is important to post up the EXACT messages
One ST0 to rule them all? One PE viewer to find them!
One ST_kRO to bring them all and in the darkness bind them...

Mount Doom awaits us, fellowship of OpenKore!

benryu
Noob
Noob
Posts: 4
Joined: 17 Dec 2009, 20:14
Noob?: Yes

Re: Packet Parser|Tokenizer (unknown/unsupported packets)

#29 Post by benryu »

Hey i extracted the packets and still i get unknown packets.

Packet Parser: Unknow Switch: 043D
Packet Tokenizer: Unknown Switch: 016C

Details
Port 6900
Version 23
Server tpye 8_4
Master_version 14

Technology
Super Moderators
Super Moderators
Posts: 801
Joined: 06 May 2008, 12:47
Noob?: No

Re: Packet Parser|Tokenizer (unknown/unsupported packets)

#30 Post by Technology »

benryu wrote:Hey i extracted the packets and still i get unknown packets.

Packet Parser: Unknow Switch: 043D
Packet Tokenizer: Unknown Switch: 016C

Details
Port 6900
Version 23
Server tpye 8_4
Master_version 14
You are using JCV's packet extractor right?
There seem to be some problems with the packet extractor, i noticed the 016C one myself.
The recvpackets seems to have multiple entries of 016A due to some bug.
So 016C seems to be missing, but you can add it manually:
016C 43
for the other packetswitch: 043D, this packet isn't implemented in kore yet (it is the postskill delay packet and it was implemented in the kRO servertypes)
One ST0 to rule them all? One PE viewer to find them!
One ST_kRO to bring them all and in the darkness bind them...

Mount Doom awaits us, fellowship of OpenKore!

Locked