mldonkey-bugs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Mldonkey-bugs] [Bug #1893] cannot blacklist servers?


From: nobody
Subject: [Mldonkey-bugs] [Bug #1893] cannot blacklist servers?
Date: Mon, 16 Dec 2002 20:02:20 -0500

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

Changes by: Horschti <address@hidden>
Date: 2002-Dec-17 01:02 (GMT)

------------------ Additional Follow-up Comments ----------------------------
It seems that the black list is not applied against servers 
_already_ stored in servers.ini file. 
You may try the following: stop mldonkey, delete servers.ini 
and start mldonkey. After this mldonkey should not connect to 
a server in the black list anymore.



=================== BUG #1893: FULL BUG SNAPSHOT ===================


Submitted by: chutz                     Project: mldonkey, a free e-Donkey 
client
Submitted on: 2002-Dec-05 09:34
Category:  Core                         Severity:  5 - Major                    
Bug Group:  None                        Resolution:  None                       
Assigned to:  None                      Status:  Open                           
Release:  2.00                          Release:                                
Platform Version:  Linux i386-i686      Binaries Origin:  Downloaded from 
Savannah

Summary:  cannot blacklist servers?

Original Submission:  I saw that my mldonkey was connected to five donkey 
servers, four of which were 127.x.x.x.... I didn't see any reason why mldonkey 
should connect to my own PC four times, so I simply tried blacklisting the 
addresses.  I simply grepped for 127. in servers.ini, and printed "bs $1" on my 
screen. Then I telneted to port 4000 of localhost and pasted a looong list of 
commands like "bs 127.1.1.1". After one paste I was getting a lot of "done" 
messages, which I thought meant that all those local addresses were 
blacklisted. However, even though I am *sure* that 127.0.0.2 got blacklisted, 
and even though I disconnected it explicitely, I again got connected to it 
later. 

I am looking at the output of "vm" right now - I *am* connected to 127.0.0.1, 
127.226.26.216, 127.154.4.252, 127.68.74.180 and 127.237.2.212. I also look at 
the downloads.ini file: I have
server_black_list = [
 "127.226.26.216";
 "127.0.0.1";
 "127.154.4.252";
 "127.237.2.212";
  .... 
among others. Some of them I have several times (probably because I was 
blacklisting them every time I got connected to them). I don't have 
127.68.74.180, but this is not the point.

So... how does the blacklisting work, and does it work at all?

p.s. Binaries Origin: Downloaded from Savannah, but I actually downloaded 
http://savannah.nongnu.org/download/mldonkey/stable/mldonkey-2.00.sources.tar.gz
 and compiled that. This is not "compiled from CVS" or is it?

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

-------------------------------------------------------
Date: 2002-Dec-17 01:02             By: horschti
It seems that the black list is not applied against servers 
_already_ stored in servers.ini file. 
You may try the following: stop mldonkey, delete servers.ini 
and start mldonkey. After this mldonkey should not connect to 
a server in the black list anymore.


CC list is empty


No files currently attached


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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]