Page 1 of 1

Malformed packets and Cannot parse Search Packets

PostPosted: 12 Feb 2013 18:07
by wombat6926
Has anyone noticed a lot of Malformed packets and "Cannot Parse" Search packet error messages?

Example:
[09:01:30] [G1] Shareaza produced search packet above but cannot parse it back!
[09:01:45] Received a malformatted query packet from 69.112.116.61, ignoring.

I am getting a lot of these messages.

I am running Shareaza 2.6.0.1 Debug 32bit (r9229 20121022) on windows 7.

Re: Malformed packets and Cannot parse Search Packets

PostPosted: 12 Feb 2013 18:08
by wombat6926
I am not sure if this is related to my query but I found this posting.

viewtopic.php?f=3&t=1327&p=8706&hilit=malformed+packets#p8706

Re: Malformed packets and Cannot parse Search Packets

PostPosted: 08 Mar 2013 21:20
by siavoshkc
The data is being sent over the network in form of small packets. Each protocol in Shareaza uses a number of packet types (to search for a file or ping for example). For each packet type there is a specified format like when you write a letter you start with the receiver's name then title after that content and at the end your signature. In Shareaza code there are packet factories which assemble packet payloads.

The first message is a self check to see if Shareaza is able to read and understand a packet created by itself. This checkpoint is to reveal bugs in packet factories. You are seeing it because you are using a debug build. It shows a bug in Shareaza code.

The second line means Shareaza has received a malformatted packet from the network. It can be because of a bug in or incompatibility with the end point servent.

Re: Malformed packets and Cannot parse Search Packets

PostPosted: 09 Mar 2013 17:49
by wombat6926
Thanks for your reply. I was using the 2.6.0 release but it crashed occasionally so I switched to the latest Debug build.