mldonkey, a multi-networks file-sharing client - Bugs: bug #13025, packet from kad port goes to...
You are not allowed to post comments on this tracker with your current authentication level.
bug #13025: packet from kad port goes to edonkey port in the same host
Submitter: | Laurento Frittella <mrfree> | ||
Submitted: | Sun 08 May 2005 02:36:37 PM UTC | ||
Category: | eDonkey-Plugin | Severity: | 3 - Normal |
Item Group: | Program malfunction | Status: | Invalid |
Assigned to: | None | Open/Closed: | Closed |
Release: | 2.5.30.15 | Release: | |
Operating System: | Linux | Binaries Origin: | CVS / Self compiled |
CPU type: | Intel x86 |
Mon 09 May 2005 07:12:07 PM UTC, comment #1: |
Amorphous <amorphous> |
Sun 08 May 2005 02:36:37 PM UTC, original submission:
Using snort (as prelude sensor) on my home-server running mldonkey-2.5.30.15 it reports:
|
Laurento Frittella <mrfree> |
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.
Follow 2 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2005-05-19 | spiralvoice | Open/Closed | Open | Closed | |
2005-05-09 | amorphous | Status | None | Invalid |
Powered by Savane 3.13-4b48.
Corresponding source code
yep, that's normal behaviour. if it is implemented correctly it knows by checking the client identifier (aka hash) that it connected to itself.