You will find here usefull information about eDonkey/emule servers
Before starting a public server, there are a few important points to consider:
Bandwidth Requirements - The amount of TCP traffic generated can be largely controlled by the number of clients you allow to connect at once. The amount of UDP traffic however can be extremely large, and is less easily managed.
Lasting Traffic - Should you decide to take your server down at some point, the traffic will not stop immediately. It will slowly decrease over time. As such, creating a public server is a long term commitment
System Requirements - The hardware requirements vary greatly depending on how many users are connected.
Legislation - According to the laws that existing in some countries, it can be legally contestable to put online eServer without filtering the indexation of copyrighted or illicit files. A eServer works just like Google does but it seem that you can be exposed to legal attacks by running it.
The last version of the eserver is 17.15 and the linux binaries are available through the edonkey
network. it's a closed source but free software.
How to download it :
Use a client software to download the server binary. You can use the following link to get a 32bits linux version running under 2.6 kernel. (Search the donkey to find the 64bits version)
MD4 hash and URI of x86 version : 4AB8DD96842359D91125B85D7EBDB953
How to install it :
Exctract the gzipped binary in a directory of your choice, then
$ gzip -d lugdunum-eserver-17.15-i686-linux.nptl.gz
$ chmod 755 lugdunum-eserver-17.15-i686-linux.nptl
$ ln -s lugdunum-eserver-17.15-i686-linux.nptl eserver
$ wget -O ipfilter.srv ipfilter.srv
$ wget -N ip-to-country.csv.zip
$ unzip ip-to-country.csv.zip
Clients IP Filter :
Please keep in mind that if you use ipfilter.dat, you should take care of frequent updates of this file.
$ wget -N ipfilter.zip
$ unzip ipfilter.zip
The eserver needs a configuration file, called donkey.ini, that should be located in the current directory.
This configuration file is compatible with the original dserver, take a look at the MetaMachine page
The bare minimum donkey.ini file should contains :
name=my server name
desc=the desc of my server
thisIP=18.104.22.168 # The IP of my server
port=4232 # the TCP port (default is 4661, but it is wise to choose another value)
To run the eserver, you can use the screen command, because the eserver has a text console, where commands may be entered.
The server cannot run as a service (daemon).
To let it restarts automatically in case of a failure, use a shell script like this one :
# script.sh file
ulimit -n 1000000
When the script.sh file is ready, just do a "chmod +x script.sh" once to make it executable.
Then to start the eserver :
screen -d -m ./script.sh
To take control of it, type :
When the server starts up it looks for a donkey.ini file in its directory. If it doesn't find this file then it carries on with the default settings.
The donkey.ini file is just a text file that sets various configuration options of the eDonkey2000 server.
List of flags and what they mean:
You can list all the available parameters and their current values by issuing this eserver command : print