| Hi xl,It has not caught on here in the States yet and the forum in France may have move that discusses the neat service but this may help.
John
»www.techinv.com/directconnect-edonkey-kazaa/
Direct Connect, EDonkey or KaZaA?
»bogmog.sourceforge.net/document_···oc_id=25
Filesharing with eDonkey 2000
In France
»www.edonkey2000-france.com/
New waiter
04.08.01 - The French waiter Rivendell .
IP:193.55.114.161 - Port:4661
OS: Linux Mandrake - max users: 800
Back to the German eDonkey2000 forum (load update: 17.02.2002)
D IE P ERFEKTE E INRICHTUNG D IT E D Onkey 2 ,000 S ERVERS v16.38
The eDonkey-2000 system exists only for well one year, but already well over 300.000 this system and about 100,000 user use user are constantly connected with the servers. I regret much, which reports do not continue to bring us in front in technical periodicals and Web publications so quite, because it lacks constantly server capacities around further user to take up to be able. Thus many new user only a lapidary "Can't connect tons keep: 80.0.71.239", instead of being able to use finally our "donkey".
In order I placed all information in this document, to past necessary for the server enterprise, users, who are content with the donkey, the way to the own eDonkey server something to facilitate, together. I hope, I did not forget anything, what straight THEY wanted to absolutely still know.
Do not let from the range of this guidance deter itself. The enterprise of a eDonkey-2000 of server becomes far simpler, than it lets the length of my guidance assume. Rather with each detail, each problem that is entered here in the enterprise to arise can, here - hopefully - is called. Thus no questions should remain open. Are described the system actually, the installation of the server on the different operating systems, the meaning of the individual parameters of the ini file. Tuning tips follow concerning computer achievement, range of the net binding and maximally possible achievement of the server.
Thus you get the maximum use for the user from your hardware, WITHOUT spending on it money unnecessarily.
First thoughts
What motivates those user to operate even eDonkey servers? Probably mainly the search for acknowledgment in the community and the desire for stabilization of the P2P of file sharing systems, which are still quite young. Then would be there probably also political motives (copyright/patent law). Such motives affected my decision anyhow considerably. One must hold oneself however before eyes, which the enterprise of a server for the operator is to be had not completely in vain: The server computer cannot be used usually any longer meaningfully for other things, since the system load is quite high. Most (in Germany) might probably use your DSL of Flatrate entrances for the server. Then it means if necessary to give oneself also times with reduced range with the "Websurfen" contently. Because depending upon size a eDonkey server needs nevertheless little range. There however "the donkey", like we it affectionately, for many a world view, a kind of of religion already nearly already became, shrink from we call no troubles and costs around him to support.
The legal side
Perhaps the question arises many whether they make themselves with the enterprise eDonkey servers punishable or could be sued otherwise somehow. Not only "Napster" sued by the organizations, those copyright defend and in such a way forced into the knees.
Disclaimer: It is completely clearly said here that I am not a lawyer! Everything that I can say to it have I past judgements in Germany and the USA inferred, as well as experiences of other server operators. Thus please does not sue me, if nevertheless annoyance in whatever form should always initiate itself.
So far is it like that that the enterprise of a file sharing index server does not offend "actually" against existing right. Since of the server no in copyright matters protected works are offered for the Download, appears also logical. Quibbling lawyers argued in the USA (in the procedure against Napster) before court, the enterprise of such a index server represent a "aid to the copyright break". As well known one finds on lake and before court in God hand, the exit of a procedure in Germany would be completely open according to my opinion. Contrary to companies such as Napster, which are legally easily open to attack by their central structure, the eDonkey servers are operated however exclusively by many autonomously acting, private net citizens. Each particular of them would have to be brought to an individual procedure before court. No enticing prospects for potential plaintiffs; -)
, the InterNet seemed to service Provider (ISP's) from organizations, which were written the penetration of copyright on their flag, was however already asked, to provide in the konreten case for omission. The ISP writes down its customer and "warned" it to offer shortly none ueheberrechtlich to cannons of works more for the Download. Otherwise nothing happens. It concerned in these concrete cases in addition, not over eDonkey server operators, but normal participants of Napster and Gnutella. I operate mean eDonkey servers now continuously since March 2001 and so far no annoyance got. Not even my ISP weighted over the violent Traffic.
EDonkey the 2000 system actually
The system conceived as a hybrid, consisting of the best concepts of the Napster and GNUTELLA projects, as well as own ideas. It is to unite the advantages of the systems in itself, whose disadvantages avoid however. If one regards the system concept more near, one will certainly come to the conclusion, which was reached this goal. OK, smaller Macken (e.g. pedantic IP address update with the server after the reallocation of a IP of the ISP, DynDNS lacking abilities (DN drinking solution) or the server IP regulation with the Client) exist still. But please it considers that the eDonkey system is a little older only than one year. Thus still larger updates line up.
Here is recognizable, who exchanges which information with whom. The connections of the servers are not drawn in among themselves: They convey among themselves in regular intervals the IP addresses of all to them well-known servers. Thus also a straight newly been added server has existing server immediately a data base all in the system, if it inquired with at least one server. File and user data do not convey the servers however among themselves. The necessary range would blow up otherwise each measure.
A Client needs the IP address (and the haven, if not the standard haven 4661 is used by the server) of a server, in order to connect itself with it. Since the server addresses can often and regularly change because of the frequent use of private Flatrates, this is simultaneous the largest weak point in the system. It can quite happen, which the Client a valid IP address of a server does not know. A Connect is then naturally impossible. In the meantime there are however different possibilities of determining valid server IP's. Many server operators with daily changing IP address have so-called Redirektoren furnished (DynIP/DynDNS/...), with their assistance from constant URL the pertinent IP address to determine leave themselves (e.g. "Little talk Corvette" servers: "lrc.dyndns.org"). During a DN drinking solution (e.g. by means of "ping lrc.dyndns.org") the DNS server calls the at present valid IP address (e.g." 217,5,78,72"). It can now directly in the Client be registered and the servers thereby be connectet. Also there are to web pages and forums also left to server address lists like e.g.. Maurices server list or the official server list . The most important goal of this at first sight complicates seeming procedure is to make the system as indisputable as possible. There is not no more SOME server operator (as with NAPSTER), that receives the system alive. EVERYONE can operate a server. If a server precipitates, the system remains nevertheless functionalable as a whole. Then evenly only the server is missing. On the other hand this procedure opens the possibility of using servers with dynamically assigned IP addresses. Hardly a user possesses a dedicated line with static, always same IP address. With the connection establishment by its InterNet service Provider (ISP) is assigned to the very most in each case for usually 24 hours a valid IP address. The sense of constant reallocations of the IP address on the part of the ISP is (one suspects it): Reduction of costs! Traffic costs money, much Traffic costs partly very much money. If however the IP address of an InterNet entrance changes every 24 hours, the customer cannot offer server services, which possibly bring a high (and for the ISP expensive) volume of data with itself. The visitors servers would not know, WHICH IP address of the servers possesses at present straight. which gives it (partial free) service as www.dyndns.org , thus because the 24 hours case of IP an good deal can as good be struck...
Needed hardware of a eDonkey server
As computers each computer about Pentium 100 can be used off. However it should have at least 128mb-ram, because the data must for fast search results completely in the RAM for the order. It is not possible to use a paging file on non removable disk since this would slow the search procedure down extremely. In order to be able to use computers with small achievement like the Pentium 100 specified here meaningfully as servers, it is necessary to limit the number of the Clients connected at the same time with the server meaningfully. After my experience a Pentium stands 100 under Linux (as recourcenschonenstes operating system) maximally 800 Clients. Beyond that it comes to computer blockades and package losses. Overloading are to be avoided absolutely, otherwise the use for the Clients is given no more. The computer "forgets" IP addresses of other servers (UDP package losses) and answers retrieval queries partly no longer. It applies here to find by attempts the correct mixture between arithmetic performance, RAM memory capacity and net entrance capacity.
Needed net binding
Those of TCP haven 4661, 4662 as well as the UDP haven 4665 are needed! Why did I write so largely? That always so gladly overlooked and afterwards is surprised all world, why the server does not function... If the net connection over a Firewall or a one rout with conversion to private IP addresses (network address translation, NAT, Masquerading) one leads, must necessary haven in rout approved and to the used private IP address the server computer become "gemapt". That rout, which makes the conversion, must thus know, to which private IP address it haven mentioned "reroute" must. A general guidance can due to the multiplicity of the systems existing at the market this-places on not to be given. But ask the guidance of the Routers, which routing software, and/or which Firewall used for rate pull. A tip at the edge: Windows XP possesses a package filter, which defeats the server function lastingly as basic adjustment, if it is not switched off (for necessary haven)! How that is made, I explain further down. |
