bugmldonkey, a multi-networks file-sharing client - Bugs: bug #1702, Connections to itself

 
 

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

bug #1702: Connections to itself

Submitter:  Invalid User ID <#12608>
Submitted:  Wed 13 Nov 2002 12:26:39 PM 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:  CVS / Self compiled
CPU type:  None

Tue 02 Dec 2003 06:25:08 PM UTC, comment #4: 

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
Sun 28 Sep 2003 12:57:48 PM UTC, comment #3: 

I see this behavior too (release-2-5-devel branch from yesterday), but I don't have the server activated. It also doesn't lists a private address, it lists the official address assigned to me by my provider (the adddress the client binds the donkey_port (4661 in my case) to).

I think mldonkey should look at the address and don't use it if it's the same address:port pair it uses.

Anonymous
Sun 28 Sep 2003 12:55:40 PM UTC, comment #2: 

I see this behavior too (release-2-5-devel branch from yesterday), but I don't have the server activated. It also doesn't lists a private address, it lists the official address assigned to me by my provider (the adddress the client binds the donkey_port (4661 in my case) to).

I think mldonkey should look at the address and don't use it if it's the same address:port pair it uses.

Anonymous
Tue 17 Dec 2002 01:42:39 PM UTC, comment #1: 

I saw the same behavior with the mld 2.01. I assume some malicious peer(s) injecting private IP addresses as servers and mld falls for it and connects to itself.

If you don't need the mld server just switch it off. You can do this by: stopping mld, disabling mldonkey server in download.ini ("enable_server = false") and re-starting mld again. When you have done this, the private IP addresses
still appear in the server list but mld can't connect to them.

Additionally you could black list the private IP addresses, so these private IP addresses also do not appear in the server list anymore.

Invalid User ID <#13852>
Wed 13 Nov 2002 12:26:39 PM UTC, original submission:  

When the core is looking for Server donkey-connections, it uses sometimes also itself as target and connects succesfully (?) to 127.0.0.1, even 127.0.0.2 or the 192.168.0 ip of my eth0.

As my system is running snort it catched yesterday
 % attacks method
===============================================
51.05 1478 BAD TRAFFIC same SRC/DST
       1478 192.168.0.102 -> 192.168.0.102

one in more Detail:

21:36:37.056961 192.168.0.102.42239 > 192.168.0.102.4662: S 1152749383:115274938
3(0) win 5840 <mss 1460,sackOK,timestamp 360802 0,nop,wscale 0> (DF) [tos 0x8]

Looks like a bug in some of the Network Code.

Any hint?
mldonkey cvs from 2002-11-09 on i386 debian unstable, nearly not all unstable ;-)

Invalid User ID <#12608>

 

(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.12