[Mldonkey-bugs] [bugs #9686] Hammering GWebCaches

[anonymous]

This mail is an automated notification from the bugs tracker
 of the project: mldonkey, a multi-networks file-sharing client.




/**************************************************************************/
[bugs #9686] Full Item Snapshot:

URL: <http://savannah.nongnu.org/bugs/?func=detailitem&item_id=9686>
Project: mldonkey, a multi-networks file-sharing client
Submitted by: 0
On: Sun 07/18/2004 at 20:44

Category:  Gnutella/G2-Plugin
Severity:  5 - Average
Item Group:  Program malfunction
Resolution:  None
Assigned to:  None
Status:  Open
Release:  2-5-16
Release:  
Platform Version:  None
Binaries Origin:  CVS / Self compiled
CPU type:  None


Summary:  Hammering GWebCaches

Original Submission:  I've seen MLDK 2.5-4 and 2.5-16 sending over 1200 
hostfile requests a day with an interval of about a minute. This is *far* too 
frequent and too much. You must apply a reasonable hardlimit e.g., 10 request 
per hour and maybe 50 over a day. Of course not for a *single* GWC but in 
total. The usual policy is to contact a single GWC not more than *once* per 
hour.
A possible reason is that the ISP blocks the Gnutella protocol but doesn't 
block GWC requests since the latter are "normal" HTTP requests. Of course any 
other malfunction/bug/problem which causes the impossibility to connect to 
other Gnutella peers could cause the same problem i.e., running out of cached 
peer addresses.
If a user cannot connect to the Gnutella network, he just can't. Hammering GWCs 
for more addresses won't help anyone but actually harm the network.

christianbiere at gmx dot de











For detailed info, follow this link:
<http://savannah.nongnu.org/bugs/?func=detailitem&item_id=9686>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/