For a while, there has been this fake client problem on the ed2k network, usually these clients identify themselves as old mldonkey or edonkeyhybrid clients, who send corrupt blocks.
mlDonkey is unaffected by them if you enable banning unreliable clients. Amule, it seems is vulnerable to them.
Basically, these clients get stuck at transferring, at 0 bytes/sec, holding that chunk up for ages.
But I thought AICH fixed this problem? In the preferences, AICH trusts every hash is not sellected. Do I have to enable it? (Even though it says Not Recommended?). What does this actually do?
--
boutros [fileheaven][CHN][KOR][FIN][MVGroup] running aMule 2.0.0rc6 (uptime 66h50m)
On Razorback 2 [195.245.244.243:4661] with High ID
Down: 76.1 Up: 12.0 (4629 clients waiting)
Down (Session/Total) 14142.70MB/40.71GB
Up (Session/Total) 2818.30MB/10.85GB