On 4 Feb 2006, [EMAIL PROTECTED] wrote: > I have a number of CLOSE_WAITs from a node.
[snip] > Is there any debug in GTKG that I can use to determine why I might > be trying to talk to this host? I guess I will leave the tcpdump > running to see what type of communication takes place that these the > CLOSE_WAIT state. The node is trying to download a file from my machine. $ grep 69.120.111.63 * dmesh:http://69.120.111.63:25002/uri-res/N2R?urn:sha1:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 2006-02-04T18:12:15Z $ grep XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX * dmesh:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX dmesh:http://69.120.111.63:25002/uri-res/N2R?urn:sha1:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 2006-02-04T18:12:15Z sha1_cache:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 21340995 1022849548 /home/mp3/Language/french/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.mp3 I would guess that it has grabbed a chunk and then abruptly closed the connection. The tcpdump output has stopped and the CLOSE_WAITS have cleared. I guess the best things to do is "tcpdump -i iface host ip" and examine the traffic? tia, Bill Pringlemeir. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Gtk-gnutella-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
