MLDonkey for DNS-323

Getting the D-Link DNS-323 2-Bay Network Attached Storage Enclosure

FAQ

The FAQ for setting up MLDonkey can be found here.

You can optimize your MLDonkey by following this guide

Sample setting file(s)
Sample downloads.ini file: Download file guide
file_completed_cmd example: Download file guide
mlnet-alternative Download file guide

Various compiled versions
2.8.5: download
2.8.7: download blog entry
2.8.7 (new): download blog entry
2.8.7 (lite): download blog entry
2.8.7 (new+gd): download blog entry
2.8.7 (lite+gd): download blog entry
2.9.0 (edonkey,bittorrent,filetp,gdlib): download blog entry
2.9.0 (bittorrent,filetp,gdlib): download blog entry
2.9.1 (edonkey,bittorrent,filetp,gdlib): download blog entry
2.9.1 (bittorrent,filetp,gdlib): download blog entry
2.9.1 (edonkey,bittorrent,filetp,directconnect,gnutella,g2,fasttrack,gdlib): download blog entry
2.9.2 (edonkey,bittorrent,filetp,gdlib): download blog entry
2.9.2 (bittorrent,filetp,gdlib): download blog entry
2.9.2 (edonkey,bittorrent,filetp,directconnect,gnutella,g2,fasttrack,gdlib): download blog entry
2.9.2 (bittorrent,filetp,gdlib)+funplug: download blog entry

2.9.3 (bittorrent,filetp,gdlib)+funplug: download blog entry
2.9.3 (edonkey,bittorrent,filetp,gdlib): download blog entry
2.9.3 (edonkey,bittorrent,filetp,gnutella,g2,fasttrack,gdlib): download blog entry

2.9.5 (bittorrent,filetp,gdlib)+funplug: download
2.9.5 (edonkey,bittorrent,filetp,gdlib): download
2.9.5 (edonkey,bittorrent,filetp,gnutella,g2,fasttrack,gdlib): download

2.9.6: blog entry and download (*compiled for ffp 0.5)
2.9.6: patched max_bt_uploaders bug (*compiled for ffp 0.5)

2.9.7: blog entry and download (*compiled for ffp 0.5)

3.0.0: blog entry and download (*compiled for ffp 0.5)

3.0.1: blog entry and download (*compiled for ffp 0.5)

3.0.2: blog entry and download (*compiled for ffp 0.5)

3.0.4: blog entry and download (*compiled for ffp 0.5)

MLDonkey is another client that supports a few Peer-to-Peer protocols (bittorrent, edonkey, …). Best of all, this bittorrent client has got a web interface for you to administrate the bittorrent client without the need to telnet in! So it makes torrenting easier. Wish that it was a desktop application instead? Use sancho to remotely administrate your bittorrent or edonkey download.

The file above is MLDonkey compiled for use on my DNS-323. I don’t provide support for the compiled application. I compiled it for my own use and feel that others might find it useful, hence I am sharing it here. I do welcome pointers on the shell script (mlnet.sh).

The script (mlnet.sh) included will attempt to do a symbolic link of the actual working directory (/.mldonkey) to the harddisk (/mnt/HD_a2/mldonkey) in DNS-323. Please refer to the support pages of MLDonkey for stuffs pertaining to it (e.g. configurations, usage). The quick start guide on their homepage is a nice start.

I have only enabled edonkey, bittorrent, http and ftp download features in this binary so don’t bother trying out other supported protocols. The libraries required ate static linked (during compilation) hence it wont require additional configuration on the DNS-323. Maybe this is the factor that has contributed to the large binary size.

If you do encounter “segmentation fault” after a few runs (which I hope you don’t). Back up your configurations (*.ini), downloads and file you think you would need before running the following commands (without mlnet running).

/ # rm -rf /mnt/HD_a2/mldonkey
/ # rm -rf /.mldonkey

Pre-requisites
You should be using the telnet daemon from the another telnet daemon post

Installation Instructions
Download and extract the contents of the archive to /mnt/HD_a2/. The location of the extracted files should look like the following

/mnt/HD_a2/mlnet.sh
/mnt/HD_a2/lnx_bin/mlnet

The next step would be giving the files permission to execute

/ # chmod a+x /mnt/HD_a2/mlnet.sh
/ # chmod a+x /mnt/HD_a2/lnx_bin/mlnet

The last step would be running the application by typing the following commands

/ # mkdir /mnt/HD_a2/mldonkey
/ # mkdir -p /mnt/HD_a2/lnx_bin/logs
/ # /mnt/HD_a2/mlnet.sh

In the future after a reboot of the NAS, you might wish to start MLDonkey again by issuing the following command

/ # /mnt/HD_a2/mlnet.sh

Your mlnet should be running in the background by now. You can do a simple check by using the ps command.

Next we shall do the initial setup of mldonkey by doing telneting to the administration port.

/ # telnet 127.0.0.1 4000
Trying 127.0.0.1…
Connected to 127.0.0.1.
Escape character is ‘^]’.
Welcome to MLDonkey 2.8.5
Welcome on mldonkey command-line

Use ? for help

MLdonkey command-line:
> auth admin “”
Full access enabled

MLdonkey command-line:
> passwd newpasswd
Password of user admin changed

MLdonkey command-line:
> set allowed_ips “127.0.0.1 255.255.255.255”
option allowed_ips value changed

MLdonkey command-line:
> save
options and sources saved

MLdonkey command-line:
> exit

Next try going to the web administration port 4080 of mldonkey using your web browser.

Hint
You can use peerguardian format blocklist for MLD. If you don’t know what peerguardian is all about. Surf on to peerguardian.

To set up ip blocking feature of MLD, you can refer to here

Thanks to the following for treating shadowandy to Starbucks:
Cipo_Italy, Matthias Dangers, Kevin Rennie, Jaime Mateos, Marc Scheurer, David Bagshaw

 

Treat shadowandy!

If these step-by-step guides have been very helpful to you and saved you a lot of time, please consider treating shadowandy to a cup of Starbucks.