[Mldonkey-bugs] [Bug #2786] Black-listed of too fast reconnections

[nobody]

=================== BUG #2786: LATEST MODIFICATIONS ==================
http://savannah.nongnu.org/bugs/?func=detailbug&bug_id=2786&group_id=1409

Changes by: Anonymous user        Date: Tue 03/18/03 at 11:48

------------------ Additional Follow-up Comments ----------------------------
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 ?



=================== BUG #2786: FULL BUG SNAPSHOT ===================


Submitted by: hallibaby2              Project: mldonkey, a free e-Donkey client
Submitted on: Tue 03/11/03 at 11:51
Category:  eDonkey-plugin             Severity:  5 - Major                  
Bug Group:  None                      Resolution:  None                     
Assigned to:  None                    Status:  Open                         
Release:  2.00                        Release:  2.04rc1                     
Platform Version:  Linux i386-i686    Binaries Origin:  Downloaded from Savannah

Summary:  Black-listed of too fast reconnections

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

Follow-up Comments
*******************

-------------------------------------------------------
Date: Tue 03/18/03 at 11:48         By: None
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 ?


CC list is empty


No files currently attached


For detailed info, follow this link:
http://savannah.nongnu.org/bugs/?func=detailbug&bug_id=2786&group_id=1409