Funny, I just installed kfurge firmware, and nothing more. mldonkey and sancho work w/o problems, I had download speeds of 300-340 Kbytes/sec on good torrents with 3mbit conection... no need to do anything to firewall and such.
Thks v much to K Forge for the enhanced firmware. Finally, this white brick is beginning to live up to its promises. Need help from anybody who has successfully gotten MLMonkey & SanCho to work properly. After installation,
I have done the following as mentioned in this forum but am still unable to get downloading speeds more than >2KB per sec.
i. reconfigured BT Client port to 48888
ii. port forwarded, under NAT Setting - Virtual Server to port range & local port 488888, using local IP 192.168.1.1, for both TCP & UDP protocols
iii. use telnet to set iptables as stated in the forum
iptables -I FORWARD -p tcp --dport 48888 -j ACCEPT
iptables -t nat -I PREROUTING -i eth1 -p tcp --dport 48888 -j DNAT --to-destination 192.168.1.1
iv. inside Windows FireWall, opened up both incoming & outgoing rules for SaCho to have full access to TCP & UDP protocols
Pls advise what else I could do to get reasonable speeds. The torrents I selected has more than 1000 peers & 500 seeds. Thks v much.
rdgs
ray
Funny, I just installed kfurge firmware, and nothing more. mldonkey and sancho work w/o problems, I had download speeds of 300-340 Kbytes/sec on good torrents with 3mbit conection... no need to do anything to firewall and such.
before run mldonkey open ports in iptables
like this
iptables -I INPUT 1 -p tcp --dport 3400-j ACCEPT
change 3400 to ur port for mldonkey
u can save this in script
look my script for mldonkey
#opt/bin/bash
iptables -I INPUT 1 -p tcp --dport 15639 -j ACCEPT
iptables -I INPUT 2 -p tcp --dport 6882 -j ACCEPT
iptables -I INPUT 3 -p udp --dport 18962 -j ACCEPT
iptables -I INPUT 4 -p udp --dport 15643 -j ACCEPT
mkdir -p /shares/MYVOLUME1/.mldonkey/
chown mldonkey.users /shares/MYVOLUME1/.mldonkey/
sh -c "
HOME=/shares/MYVOLUME1/ TMPDIR=/shares/MYVOLUME1/.mldonkey/tmp \
/opt/bin/mlnet.byte -allowed_ips '127.0.0.0/8 192.168.1.255' &"
click on Help+ porttest
for check
open ports or not.
see ur ports in options
Help+/Port Test, it looks like TCP/UDP failed.
I'll try your suggestions above.
use this script with ur ports
You really don't want, or need, to do any of this. Sancho and your PC do not do the downloading, the router does. You only need to insert an accept rule into the INPUT table. The MLDonkey startup scripts already do this for you.
Follow the directions here for changing the port if the default does not work for you:
http://wl700g.homelinux.net/drupal/?q=node/190
- K.C.
Thks v much, Sonic for yr advise. I tried to do the above and then, the port test but get the following result.
BitTorrent Porttest finished 0m 2s ago Port test failure, Can't connecto to 205.156.14.44 on 48888.
The above IP setting is different from the MLDonkey client IP of 205.156.14.40. Are the two IPs supposed to be the same?
Or are both supposed to be the router's IP address of 192.168.1.1?
Also, noticed that u've opened UDP ports in yr scripts? Are these the Donkey client TCP & UDP ports, since my port nos are different from what you stated in the script?
Finally, how & where do I save the script to? Appreciate yr kind advise pls.
Thks v much.
Thks v much, K Furge. I did an "iptables --flush" to clear the previous settings. And followed yr advise to "nvram" set the BT client port, then "nvram commit" and then "reboot"ed the router.
Am still getting the following negative results:
i. downloading speeds <3KB per sec, on torrents with v gd seeds & peers, and I'm on v fast broadband
ii. Low ID messages when I go to Sancho's "Console"
iii. port test within ML Donkey still fails, the IP address stated is different from the ML Donkey client IP address
Appreciate yr advise on the above pls. Thks v much.
rdgs
Yes, they must be the same. I don't know why they would be different unless you have another device further upstream doing something strange.
The router actually has two addresses. The WAN address, which is on the internet side, and the LAN address on your network side. The 192.x.x.x is the address on the LAN side. The 205.156.14.40 is the address on the WAN side.
- K.C.
Thks v much, K Furge. Within ML Donkey, I forced the IP client address to be the same as the Wl 700GE WAN IP address. The port test IP adddress is still different from the WL 700GE WAN IP address. Am however, getting better speeds of abt 10-20KB /s for downloads. 3 additional questions to seek yr advise pls.
i. Is this configuration correct, since the port test still fails? Or should I be doing something else eg port forwarding etc? Why is ML Donkey unable to find the correct WAN IP address & port test IP address?
ii. After successfully downloading a BT file as a test, tried to delete the shared torrent & move the downloaded file. However, get a unauthorized permission message inside Windows. My Windows user ID is different from the default "admin" user ML Donkey ID? How can I easily move/delete files in the ML Donkey directory? Tried to create the same Widnows user ID & password in ML Donkey but still doesn't work.
iii. Read up more on ML Donkey. Apparently, there's a new version 2.9.3. Also, ML Donkey does not support BT DHT trackers. Hence, may explain the slower speeds. What can we do abt this?
Appreciate & thks v much for anybody's help on the above pls.
Hm hm, been using torrents since I flashed the router, and getting OK speeds, up to 350kb/s... then I started searching mldonkey and it kinda works, but I always get LOW ID on all servers I connect to.
Did port test, and got
BitTorrent
Port test OK!
Testing IP: *.net.upc.cz (78.102.44.*)
Starting TCP connection test...
TCP test failed! UDP test will not be performed.
Connection test finished.
So it seems torents are fine, but mldonkey isn't and that explains low speed and LOW ID.
Any clues? I've been reading on LOW ID and it seems to be connectivity issue, as stated here:
http://forum.emule-project.net/index...7&#entry312587
OK, i have it figured out... :-)
my IPtable was like this:
We can clearly see that 6882 is accepting on TCP, as specified in iptables_mldonkey.sh located in /opt/etc/init.kc.Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
1944 112K DROP all -- * * 0.0.0.0/0 0.0.0.0/0 state INVALID
7992K 2644M ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED
4494 306K ACCEPT all -- lo * 0.0.0.0/0 0.0.0.0/0 state NEW
395K 155M ACCEPT all -- br0 * 0.0.0.0/0 0.0.0.0/0 state NEW
7174 430K ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:22
162K 8053K ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:6882
3204 1051K ACCEPT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp spt:67 dpt:68
2 108 ACCEPT tcp -- * * 0.0.0.0/0 192.168.1.1 tcp dpt:8081
20 968 ACCEPT tcp -- * * 0.0.0.0/0 78.102.44.147 tcp dpt:21
524K 26M DROP all -- * * 0.0.0.0/0 0.0.0.0/0
So... from mldonkey web config, I found out that it is using following ports:
This means, that kfurge is opening ONLY port 6882, that is used for TORRENTS, and that's why torrents work.Network Port Type
BitTorrent 6882 client_port TCP
BitTorrent 6881 tracker_port TCP
Core 4080 http_port
Core 4000 telnet_port
Core 4001 gui_port
Donkey 6891 client_port TCP
Donkey 6895 client_port UDP
Donkey 20286 overnet_port TCP+UDP
Now, it is listing another 4 ports, 1 for torrent (but who cares if it's working) and 2 for mldonkey: 6891 on TCP and 6895 on UDP.
Now, if I do:
and then again list my iptables withiptables -I INPUT 6 -p tcp --dport 6881 -j ACCEPT
iptables -I INPUT 7 -p tcp --dport 6891 -j ACCEPT
iptables -I INPUT 8 -p udp --dport 6895 -j ACCEPT
iptables -L INPUT -nv
i now get:
See? they're there... and automatically I got HIGH ID in mldonkey!!!! (sancho)[root@WL700gE ~]$ iptables -L INPUT -nv
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
1947 112K DROP all -- * * 0.0.0.0/0 0.0.0.0/0 state INVALID
8000K 2650M ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED
4495 306K ACCEPT all -- lo * 0.0.0.0/0 0.0.0.0/0 state NEW
395K 155M ACCEPT all -- br0 * 0.0.0.0/0 0.0.0.0/0 state NEW
7174 430K ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:22
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:6881
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:6891
0 0 ACCEPT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:6895
162K 8060K ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:6882
3206 1052K ACCEPT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp spt:67 dpt:68
2 108 ACCEPT tcp -- * * 0.0.0.0/0 192.168.1.1 tcp dpt:8081
20 968 ACCEPT tcp -- * * 0.0.0.0/0 78.102.44.147 tcp dpt:21
525K 26M DROP all -- * * 0.0.0.0/0 0.0.0.0/0
Yes... do it as root....
D.
Thks v much. The downloads seem to be faster now. Can achieve speeds as high as 16 KB / s. However, the BT port test still fails. Donkey TCP & UDP tests are working fine now. Any ideas how I can resolve this? The BT client detected by ML Donkey is still different from the port test IP??? Anyone pls help!
rdgs