Gnutella Forums

Gnutella Forums (https://www.gnutellaforums.com/)
-   General Gnutella Development Discussion (https://www.gnutellaforums.com/general-gnutella-development-discussion/)
-   -   Payload descriptor codes (https://www.gnutellaforums.com/general-gnutella-development-discussion/11786-payload-descriptor-codes.html)

Unregistered May 26th, 2002 02:40 PM

Payload descriptor codes
 
As you know, packets have a payload descriptor so you can check to see what kind of package we are dealing with. So when I encounter a packet with an invalid descriptor (other than 0x00, 0x01, 0x80, 0x81 or 0x40) I assume for one reason or another the stream lost sync and I drop the connection. However, This occurs quite a lot, and I don't actually have the feeling that I'm loosing sync, but I think it are custom codes from other clients.
Could this be? If so, can I get a list of these custom codes (the known ones) somewhere so I can ignore the packet if it's one of these, and drop the connection if it is still another.

cultiv8r May 26th, 2002 03:32 PM

The only ones I believe might be used are 0x02 and 0x03, but those were only proposed and shouldn't actually be used. But when these "invalid" messages appear, what I would do is assume the payload is correct, read it but then drop it from further distribution. I'd also keep a counter for the occurence - if it happens too often within a short timespan, I'd consider the other client to be faulty and drop the connection.

Fisman May 26th, 2002 08:35 PM

also
 
30 is used for query routing

Cakkie May 26th, 2002 11:13 PM

Thanx, I think I'll go for the first one, to ust ignore a number of successive invalid packets, before dropping the connection.


All times are GMT -7. The time now is 06:20 AM.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2025, vBulletin Solutions, Inc.
SEO by vBSEO 3.6.0 ©2011, Crawlability, Inc.

Copyright © 2020 Gnutella Forums.
All Rights Reserved.