aMule Forum
English => aMule Help => Topic started by: vlakki on January 06, 2007, 12:06:10 PM
-
Hi everyone =)
Here is the situation.
I've installed aMule 2.1.3 on Mandriva 2007 and managed the router to translate interested ports to help aMule to get High ID and Kademlia network connection. All of it is successfully done and work.
Than I went to this link http://www.amule.org/wiki/index.php/Migrate_from_eMule_to_aMule for migration procedure (Thanx to morph), moved all emule's files from /config directory to ~/.aMule (BTW, I didn't find Category.ini file...) moved the statistics.ini file content to amule.conf section [Statistics].
Finally I run aMule with $ amuled -of command on server and used $ amulegui --verbose command to manage it from my win workstation and got connected to both networks with High ID and Kad (Ok) status.
And the question.
I started both the aMule 2.1.3 on linux and eMule 0.47c on my workstation to investigate the connection behavior (they both have Dnky srv2 High ID and Kad network opened). And I found aMule get at least twice less sources than eMule do. Why it is so? Can anyone give me advice on problem?
Forgot to say - ipfilter.dat file I renamed to ipfilter.dat.back and Max sources per file is 300 and Connection Limit was set to 300 Max connections.
-
I think the answer is that I should give the aMule more time to see all the sources.
But I still wonder how they both can have a different number (sometimes more and sometimes less) of sources for the same link since they both have a connection to the same server and Kad ok status...
Another interesting behavior of amuled (or amulegui) - when I get a remote connection to a client through amulegui I can see Kad status sometimes changes from Ok to Firewalled or Off statuses and gets back durind a day =))
-
I can concur on your findings: It takes amuled a bit more time than eMule to retrieve the sources. But always it is just a matter of time before they are roughly equal. My guess is that eMule and amuled simply use slightly different algorithms to seize, allocate and display the sources.
As for the Kad firewalled, this is because Kad issues a udp ping every hour, sometimes it does not receive the answer back within the allocated time and it shows a "firewallled" message. Normally it will receive the answer within the same second, and then it shows "Kad OK". You will notice this sequence a lot in the logfile, always on the same minute of the hour, the same minute you started the daemon. There is something written about this by Kry somewhere else on the forum.