hi there,

for my sins I'm doing some work on gnutella network for my masters thesis which involves implementing a rough client.

At the moment I'm analysing the communications between gnucleus on my machine and the outside world and having a few problems decoding whats going on ...

the byte data looks as follows after i split it up - it was all in one frame so here's my interpretation of 164 bytes in total

07 9D 0C 0E 7D AB 9F 4E B5 E4 00 C4 5A 70 D0 5D --> ID
00 --> PING
01
00
00 00 00 00 --> payload size

i take it this is another header now:
36 10 33 82 34 75 18 42 A2 26 B3 AB A2 A4 21 A0
30 --> WHAT IS THIS?
01
00
06 00 00 00 --> payload 6 bytes
00 00 00 01 00 02

and another:
EF 57 F9 93 90 6F A3 48 A4 7A ED 3A 1C 36 93 35
30 --> WHAT IS THIS?
01
00
59 00 00 00 --> payload 59 bytes

<another 59 bytes>

can anyone put me out of my misery and explain to me what that 0x30 is doing there or even if im barking up the right tree here with the way im "decoding" this?

thanks in advance

ben

Vendor Message see: http://groups.yahoo.com/group/the_gd...vendor_msg.txt

I think an older client uses 30 instead of 31/32

thanks for your reply. what im confused about is that i thought that byte was used to define the function of the packet 00 for PING, 01 for PONG, 80, 81 etc.

do you mean that there was a 0x30 function in the older clients?

i'm fairly sure that the client i connected to was one of the newer limewire servents.

im sorry if this is a stupid question, im just starting out and my brain's bleeding from analysing packets ...

thanks

ben

Is the data you provided above complete (-59 bytes)?

Is this from the limewire client or the gnucleus?

Can you post the remaining 59 bytes?

hi, thanks for the reply. I've attached my breakdown of the session.

apollo is running gnucleus, the servent is running morpheus (not limewire, my mistake, sorry).

Attached Files

conversation_gnucleus_morpheus.txt (8.3 KB, 351 views)

Duh, I don't know what I was thinking...

Query Routing Protocol
http://www.limewire.com/developer/qu...%20routing.htm

ok - this looks technical! I'll wade through this over the next couple of days .. !

thanks for your time, i really appreciate the help

cheers

ben