bugmldonkey, a multi-networks file-sharing client - Bugs: bug #1893, cannot blacklist servers?

 
 

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

bug #1893: cannot blacklist servers?

Submitter:  Invalid User ID <#13431>
Submitted:  Thu 05 Dec 2002 09:34:00 AM UTC
   
 
Category:  Core Severity:  3 - Normal
Item Group:  None Status:  None
Assigned to:  None Open/Closed:  Closed
Release:  2.00 Release: 
Operating System:  Linux Binaries Origin:  Binary from Savannah
CPU type:  None

Tue 02 Dec 2003 06:29:18 PM UTC, comment #3: 

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 17 Dec 2002 01:03:03 AM UTC, comment #2: 

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.

Invalid User ID <#13852>
Tue 17 Dec 2002 01:02:19 AM UTC, comment #1: 

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.

Invalid User ID <#13852>
Thu 05 Dec 2002 09:34:00 AM UTC, 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?

Invalid User ID <#13431>

 

(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