heeeeeeeeelp!

I've created a small client, it does the following:

Connect to a servant somewhere [working fine]
Send "GNUTELLA CONNECT/0.4\n\n" [working fine]
Receive "GNUTELLA OK\n\n" [working fine]
Send "Ping msg", GUID is just 16 random numbers, followed by that a 0 (PING REQ), TTL=7, HOPS=0, and 4 zeroes (no length) [working fine]

I now get PONG reponse from lots of dudes! [working fine]

I send the following query:
"Query msg", GUID is just 16 random numbers
Then 128 (0x80 QUERY), TTL=7, HOPS=0, and 4 bytes: 6 0 0 0
Now comes the descriptor:
Two zeroes 0 (0 KBPS required), and then "mp3", 0

After this, I'm hoping to get lots of QUERY RESPONSES on this connection, but I get NOTHING

Why is this? I use Little Endian order for everything (except IP #),

thanks!

Due to various bugs in several clients (including ours) you will need to set the "minimum speed" to at least 56 (for 56kbps) in order to get most query replies.

I just tried setting the first two bytes of the QUERY to 56 00 (decimal) ... no response still!

Whats wrong? I've debugged the program and made sure that it really does output what I wrote in the first email!

thanks

I've noticed they close the connection right after sending Pong messages!! How come?

bad pong - or - you like a freeloader (sharing no files)?

... or if you mean after THEY send a pong, then they have no free slots available and feed you with alternative locations. Try v0.6 protocol, you get more status messages.

If you read my first email, I have specified exactly what I send and exactly what I get back!

Noone ever pings me, so I have not ponged anyone (and thus I have not specified to anyone how much I share!)

Thanks Pizza! That's helpful information, didn't read about it anywhere! Btw is the 0.6 specification found anywhere?

I'm very interested to find out more about Super Nodes and Super Peers, any info about that anywhere?

Btw, Yes other peers PONGED me!

see the FAQ thread, click on second link.

PizzaMan

PS: didn't got any email from you.

Sorry, I meant see first posting in this thread for full specification of data sent. Posting, not e-mail! :

Some servents block out mp3 and some other words. Otherwise, everyone would search for mp3 and we'd have thousands of query hits flying back and forth, flooding the network. I suggest trying some other words, ones that give some responses when you search for them on your other gnutella servents. I get responses when I search for mp3, but I know I'm not getting the responses I would if newer servents weren't blocking queries like that.

Here is how I send queries -

0-15: GUID 16 numbers [same as ping GUID]
16: 0x80
17: ttl 7
18: hops 0
19: querylength+3
20-22: all 0's
23-24: all 0's
25 through querylength+25 : query
26+querylength: 0

I had trouble initially. I develop on Unix (Linux). What I did was install gnut, a working Gnutella servent and then tcpdump so I could see how it was sending queries properly. Then I ran tcpdump on my program and saw where I had gone wrong and fixed it.

There's a Windows version of tcpdump called windump, although I haven't used it. Tcpdump (and probably windump or some other packet sniffer) is quite handy in helping debug many Gnutella problems.

__________________
Gnutizen - http://www.geocities.com/gnutizen

Unfortunately I dont think the problem is my query, since it is just like yours! I keep getting closed connection right after my query is sent!

If the connection is closed right after you sent the query request, the host you were connected to, could not read your query properly and dropped the connection because of an invalid gnutella message.

So the problem has to be your query.

__________________
Ich verabscheue euch wegen eurer Kleinkunst zutiefst.

Look at some source code for other clients, that should clear things up. Byte order is always a problem, and make sure you are sending out the correct bytes, you can screw up and send out the upper part of a word easily.