aMule Forum
English => aMule Help => Topic started by: Janni on August 13, 2004, 11:19:01 PM
-
Dear readers,
When a file is complete, the transfered file size if often 3x or more the completed file size. Is that normal?
Hugs,
Janni
-
hi,
no its not.. tell us more about your system.. make a screenshot but remove the file names
greets
-
I am using Fedora Core 2 and have 384MB ram and using a shared 4Mbit connection with 140 other people.
In the prefs. have I only changed the bandwidth and download path from the default settings.
At the moment am I sharing 1kb/s in upload to see if that helps, but I don't think it does.
Screenshot here :D
http://www.heko.dk/~maj/Screenshot.png
Love,
Janni
-
okey thx :)
the screenshot looks ok. but try to don't use auto priority and set the files to prio normal
greets
-
I have done that now :)
If you look at file 2,8,12 they will be far over 3x the file size. Could it have something to do with the network I am on? E.g. the firewall that drops some of my packes?
Hugs,
Janni
-
ah sorry.. didn't look at the real file size :baby:
could it be u have many mldonkeys around in your queue ?
-
What can mldonkey users do?
Can I limit it?
Hugs,
Janni
-
there are some fake mldonkey clients around which send u corrupted parts..
copy and save it as i.e mld ->
#!/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
chmod the mld file to 755 and do as root:
./mld
will save u from the faked mldonkey clients
greets
-
WOW! Thanks!, :)
I have started in right away :D
I once read something about super compressed packets. Have that something to do with this?
Lots of love,
Janni :D