Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[JohnGH]

I've noticed that I can get multiple entries for the same user in a list

e.g. two or more entries for the same user under the same file in the Downloads list.
If you check all their details like the IP, port, Userhash and User ID they are the same...

If you send both of them a message they come up in the same window on the Messages page.

If you mark one entry as being a friend only that one is marked, not the others.

Are clients not checked for user hash, IP:port etc when being added to a list
or is this just a bug?

This is aMule CVS Snapshot: Thu Jun  2 07:01:24 CEST 2005 - but I first noticed it in an older version (I was running the May 11 build before and I think it was happening in that, but I have tried two other recent versions so I'm not certain it was that one)

It is possible that it is happening when a user on a static IP address looses their connection and then comes back again.

The client I've attached a picture of is on LowID and connected to the same server as me (Razorback 2) and their Secure Ident says "Verified - OK"

After I made this picture the one I was transferring from dissapeared.

Later I tried to "View Files" on the first in the list, it went "Connecting via server" then changed that entry for the client to have a friend icon (it had just had a donkey up to then), then connected to the remote user and started downloading again. I think that because I had initiated the connection by asking to contact that client to view files it re-used their details, but if the client had been offered to me by the server it might have added a 3rd again.

As I write there are now 3 entries for the user in the "Clients" list with 3 different "Download status" values; "Unknown", "Connecting via server" and "Transferring",
even though there are only 2 in the Downloads list.

[skolnick]

You sure the userhash is the same for all the users? because as you probably know, username means nothing, userhash is the important thing. If you are sure the userhash is the same for all suspicious users, then this could be a bug, because AFAIK, same userhash users should be banned by aMule.

Regards.

[JohnGH]

Damn, sorry, I should have taken a screenshot of the "Clients" screen too.

Yes, before writing that I checked by clicking "Show Details" on each of the 3 client lines, and the 32 char hex string was the same for each of them.

I'm certain now that what I was seeing was a client with a flakey connection (evidenced by the fact that the download speed was not good, and it kept drying up and dying (like more than 15-20 times on the same 9MB chunk) and then after a few minutes appearing again, and very quickly letting me resume downloading. The reason there were 3 entries was that it was a client and 2 ghosts.