Print

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

[fcardone]

Hello -

I have noticed that when aMule starts transferring from MLDonkey 0.3.0 clients the transfer locks to 0.0 kb/s - actually not so - it transferred about 6 or 8 bytes overnight ;-) Your bug or MLDonkey's? This does not prevent, of course, the download to acquire normal speed when connecting to other clients.

[Hinnerk]

Others found out, too:
http://www.amule.org/amule/thread.php?threadid=3045&sid=

Perhaps blocking certain IPs may help

Code: [Select]

shit:038.113.000.000 - 038.113.255.255
shit:038.115.000.000 - 038.115.255.255
shit:038.117.000.000 - 038.117.255.255
shit:038.118.000.000 - 038.118.255.255
shit:038.119.000.000 - 038.119.255.255
shit:065.019.175.000 - 065.019.175.255
shit:066.117.000.000 - 066.117.255.255
shit:066.054.000.000 - 066.054.255.255
shit:207.234.000.000 - 207.234.255.255
I converted this list with ipblacklist_convert (http://ftp.berlios.de/pub/mldonkey/pango/goodies/ipblacklist_convert),
z.B. ipblacklist_convert -peerguardian ipfilterlist.txt -iptables ipfilterlist.sh

The created shellskript looks like this:

Code: [Select]

#!/bin/bash

# Create special MLDONKEY chain
iptables -t filter -N MLDONKEY
iptables -t filter -F MLDONKEY

# Create the logdrop chain to log & drop a packet
iptables -t filter -N MLDONKEY_LOGDROP
iptables -t filter -F MLDONKEY_LOGDROP
iptables -t filter -A MLDONKEY_LOGDROP -j LOG --log-prefix "MLDONKEY"
iptables -t filter -A MLDONKEY_LOGDROP -j DROP

# Jump to the special MLD chain at the end of the INPUT chain (commented out)
#iptables -t nat -A INPUT -j MLDONKEY

# List of ip ranges to ban
iptables -t filter -I INPUT 1 -s 38.113.0.0/16 -j MLDONKEY_LOGDROP
iptables -t filter -I INPUT 1 -s 38.115.0.0/16 -j MLDONKEY_LOGDROP
iptables -t filter -I INPUT 1 -s 38.117.0.0/16 -j MLDONKEY_LOGDROP
iptables -t filter -I INPUT 1 -s 38.118.0.0/15 -j MLDONKEY_LOGDROP
iptables -t filter -I INPUT 1 -s 65.19.175.0/24 -j MLDONKEY_LOGDROP
iptables -t filter -I INPUT 1 -s 66.54.0.0/16 -j MLDONKEY_LOGDROP
iptables -t filter -I INPUT 1 -s 66.117.0.0/16 -j MLDONKEY_LOGDROP
iptables -t filter -I INPUT 1 -s 207.234.0.0/16 -j MLDONKEY_LOGDROP

[fcardone]

Hello -

what you suggest is IP blocking at the firewall level. In my case, I will use an ipfilter.dat within aMule and hope it works -

however, that does not prevent the problem. IMHO the developers, if they are reading this (are you one? ;-)  ) should implement something that either:

1) checks whether a download is staying constant at the 0.0kb/s level, and then stop the download and ban the client

- or -

2) fix aMule so that this no longer happens.

But thanks anyway!

FLAVIO

[Jacobo221]

This is a known issue on some MLdonkeys. They upload 6 bytes and stop. This is considered as leeching and those clients will be banned. There's a big discussion about those clients on the p2p community since it seems they might be non-free as beer clients (that is, clients which ppl must pay to have them) or clients which are there to upload 6 bytes of corrupted data to completly brake that chunk so that you have to download the chunk again.
Work is on progress ;-)
Greetings!