Installation

Install mldonkey:

apt-get install mldonkey-server

I saw this:

*** WARNING: ucf was run from a maintainer script that uses debconf, but
             the script did not pass –debconf-ok to ucf. The maintainer
             script should be fixed to not stop debconf before calling ucf,
             and pass it this parameter. For now, ucf will revert to using
             old-style, non-debconf prompting. Ugh!


         Please inform the package maintainer about this problem. 

It didn’t seem critical, so I continued.

Initial Rejection

The install went okay, but when I try to access it through telnet, I get this:

$ telnet localhost 4000
Trying 127.0.0.1…
Connected to localhost.
Escape character is ‘^]’.
Telnet connection from 127.0.0.1 rejected (see allowed_ips setting)
Connection closed by foreign host.

This was fixed by a simple restart:

sudo /etc/init.d/mldonkey-server restart

Then, I got this:

$ telnet localhost 4000
Trying 127.0.0.1…
Connected to localhost.
Escape character is ‘^]’.
Welcome to MLDonkey 2.9.5
Welcome on mldonkey command-line


Use ? for help

MLdonkey command-line:
>

Note About Configuration Files

After some research, I found that the allowed_ips is a parameter in a file called download.ini. There was no /etc/mldonkey. Instead, I did a lot of digging and found /etc/default/mldonkey-server, which has a value called MLDONKEY_DIR which was set to /var/lib/mldonkey. So, the file I needed was at /var/lib/mldonkey/downloads.ini. However, do not touch this file. The system is designed to be configured through telnet or the web interface. When I changed these files directly, the file would revert to the old values.

Changing allowed_ips

So I just went to the telnet prompt and changed the allowed_ips value directly:

$ telnet localhost 4000
Trying 127.0.0.1…
Connected to localhost.
Escape character is ‘^]’.
Welcome to MLDonkey 2.9.5
Welcome on mldonkey command-line


Use ? for help

MLdonkey command-line:
> set allowed_ips 192.168.0.0/24
option allowed_ips value changed

Then, the web interface became available to the entire network at http://my-machine:4080