QNAP Systems, Inc. - Network Attached Storage (NAS)



MLDonkey (eMule/eDonkey) Installation & Setup

"Why use a PC?
When you can do it all just on a NAS!"

MLDonkey on QNAPWhat is MLDonkey (eMule/eDonkey)?

MLDonkey is a door to the eMule world (also known as eDonkey), a multi-network, multi-platform open source P2P application used to exchange big files on the Internet and present most features of the basic Windows donkey client and additionally supports Overnet, Fasttrack, DirectConnect P2P (based on HUBs) and BT protocol. Below is the installation guide for MLDonkey on QNAP NAS via QPKG software package and a basic usage to get you started right away.

So how does it work on QNAP?

Take a look at the scenario below.

Let's get started!

Install MLDonkey via QPKG

Go to 'Application' > 'QPKG' and click 'Get QPKG' to get a list of currently available software packages. Choose the link that matches your NAS model to download the appropriate mldonkey.qpkg file.

Once downloaded first unzip the file archive then go to 'Application' -> 'QPKG' and install the mldonkey.qpkg file the same way as if you were updating the system firmware.

Upon successful installation you should see a QPKG entry like the screen below. Now click 'Enable' to start the MLDonkey service. Once you see the status becomes 'Enabled' you may continue to the next step. Please note that the default username and password for MLDonkey is admin/admin.

Before you start using MLDonkey you will have to forward 2 ports for incoming connections from other clients in order to gain better connection rate. QNAP has default this port to 15000 (TCP) and 15004 (UDP), and users should ensure forwarding both ports on your router to the internal IP address of your NAS that's running the MLDonkey. If you are unsure whether or not these ports are forwarded properly you may go to this site and enter your WAN IP to test them.

Download, Install & Configure Sancho

Download the latest stable version (0.9.4-59) for:

  • Windows(XP, Vista, Requires Java Virtual Machine)
  • MacOSX - Carbon (10.3+, Requires Java Virtual Machine)
  • Linux - GTK (Requires Java Virtual Machine)
The guide below will be based on Windows installation

Once downloaded double-click the setup file and install as normal Windows software installation. After successful installation start the program and first of all you will be taken through a few steps for configuration. Now you should see a setup screen like the one on the bottom left. Click 'Next' to continue and 'Next' again to skip the 'Core settings'. Next configure the required settings by entering the NAS IP, port number (4001 by default), username and password (default username/password is admin / admin) and click on 'Make current selection the default' to save your settings. Click on 'Connect' to proceed.

If you can see the NAS IP address at the top you are now connected to the MLDonkey.

Now go to the 'Servers' tab, you need to first connect to some servers if it did not do it for you automatically.

You may now fire some searches and start filling up your 'Transfer' list.

If you reach this step successfully, Congratulations! You've just turned your NAS into eMule/eDonkey downloader! You may shut down your PCs at any time for the same purpose.

External Resources & Links

Remote Access & Router Configurations

MLDonkey supports several P2P networks and in order to participate in these networks the NAS needs to be reachable on one or more TCP/UDP ports by other peers. The default network (eMule/eDonkey2000) of MLDonkey listens on TCP port 15000 and UDP port 15004 for the incoming connections and you are required to forward these ports on your router before you can start downloading files. The port settings can be changed in Sancho as illustrated below:

Go to 'Tools' > 'Preferences' then from the pop-up window go to 'Networks' > 'Donkey' > 'ED2K-port'. (Note that the UDP port will be TCP port + 4)

Refer to the table below for the complete list of service ports in MLDonkey

Network Type MLDonkey default Configuration file
eDonkey2000 TCP 15000 donkey.ini
eDonkey2000 UDP 15004 (TCP port + 4) donkey.ini
Kad TCP 6419 (eMule) donkey.ini, Kademlia section
Kad1 UDP 6429 (eMule) donkey.ini, Kademlia section
Overnet TCP 4662 donkey.ini, Overnet section
Overnet UDP No default donkey.ini, Overnet section
Gnutella TCP 6346 gnutella.ini
Gnutella UDP (??) Same as TCP gnutella.ini
Gnutella2 TCP No default gnutella2.ini
Gnutella2 UDP Same as TCP gnutella2.ini
BT TCP 6881 BT.ini
FastTrack TCP 1214 fasttrack.ini
OpenNapster TCP 6699 opennap.ini
DirectConnect TCP 1412 directconnect.ini
Direct Connect UDP Same as TCP directconnect.ini
Soulseek TCP 2234 soulseek.ini

If you wish to use Sancho to monitor and control MLDonkey from a remote location you will need to forward TCP port 4001 and change the value of 'allow_ip' to the WAN IP of the location you will be connect from or simply fill up '' to accept all connections. Both settings can be changed in Sancho as illustrated below:

To change the port used for remote connection, go to 'Tools' > 'Preferences' then from the pop-up window go to 'Interfaces' > 'gui_port'. To change the allowed IP go to the first configuration option at the top says 'allowed_ips'. That's all to set up before you can connect while you are away from home.

Release date: 2013-04-25
Was it helpful?
Thank you for your feedback.
Thank you for your feedback. If you have any question, please contact support@qnap.com
25% of people think it helps.