bugmldonkey, a multi-networks file-sharing client - Bugs: bug #2786, Black-listed of too fast...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #2786: Black-listed of too fast reconnections

Submitter:  Stephan Haller <hallibaby2>
Submitted:  Tue 11 Mar 2003 04:51:22 PM UTC
   
 
Category:  eDonkey-Plugin Severity:  3 - Normal
Item Group:  None Status:  None
Assigned to:  None Open/Closed:  Closed
Release:  2.00 Release:  2.04rc1
Operating System:  Linux Binaries Origin:  Binary from Savannah
CPU type:  None

Tue 02 Dec 2003 06:42:07 PM UTC, comment #2: 

This patch report is very old. If the bug still exists in current
versions please post a new bug report - spiralvoice

spiralvoice <spiralvoice>
Group administrator
Tue 18 Mar 2003 04:48:28 PM UTC, comment #1: 

I guess you know you're being banned because you're receiving warning messages from mldonkey peers ? (other clients ban you silenty AFAIK).
My hypothesis: some other mldonkey clients (or generally clients that connect to several servers at once) are known from several addresses, one highid and one or several lowids.
Since mldonkey only uses addresses (and not client hash) to identify peers, it can ask a peer faster than min_reask_delay.
Not very easy to fix, does it really happen with a high percentage of clients ?

Anonymous
Tue 11 Mar 2003 04:51:22 PM UTC, original submission:  

mlDonkey 2.04rc1 client will mostly black because of too fast reconnections which results in one hour bans. I'm using mostly the default values except of upload/download limits (which do not work anymore -last working version was 2.03-27 cvs).

Any values to check?

Greez
Stephan Haller

Stephan Haller <hallibaby2>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

 

Follows 1 latest change.

Date Changed by Updated Field Previous Value => Replaced by
2003-12-02 spiralvoice Open/ClosedOpen Closed

Back to the top

Powered by Savane 3.13-4b48.
Corresponding source code