aMule Forum
English => aMule Help => Topic started by: nubtumbler on October 16, 2006, 10:29:29 PM
-
I ran into a problem with aMule. This was on a configuration that had been working flawlessly for months.
Upload and download stopped completely. AMule was still connected but had zero sources for all files. Global server searches worked but returned no results no matter what search terms I tried.
I was also having problems with Kad. About one week before aMule stopped getting sources, Kad had become unreliable. It would disconnect after only running for a few minutes. When it did connect, it was always firewalled even though my network config had not changed and my ports tested as open. Changing ports did not help. I could do nothing to bring Kad back to life.
I tested all of my networking equipment and reset my network connection. Everything seemed to be fine. I started aMule again. It could connect with any server but it never found sources. Zero sources for every file and no search results for any search. When kad would start it would be firewalled and disconnect in minutes.
I searched the web to see if the ed2k network was under some new attack. It seems that a router manufacturer has implemented special technology to identify and disrupt eMule and BT traffic. I also found that eMule has recently implemented protocol obfuscation to combat this blocking.
I downloaded eMule 0.47c onto a Windows machine. I ran eMule with and without protocol obfuscation. Without obfuscation it behaved just like aMule. With obfuscation, it ran normally, just as aMule had been running for the past year.
I'm posting to (hopefully) help anyone else who finds their aMule is suddenly not working.
One solution is to run eMule under Windows running on VMWare Player. VMWare Player is free and I think that it is even offered through the package managers on some distributions. You can also run eMule under WINE but I have read that it is not 100% stable.
It would be nice to call my ISP and tell them to fuck off but that just isn't an option for me. It seems there are many others around the world in a similar position.
I believe that Kry has plans to implement protocol obfuscation so this is only a temporary problem. Still, I miss my aMule.
-
i had such a problem too.
But this was in the time of any new hybrid edonkey version.
I think i solved it with deleting a .dat file. Then move all partially files out of the download folder.
Starting the donkey and exit it after one or more searches.
After this you move all files back to temp dir and start it again.
This (i think) was the way to get it fixed on a edonkey version.
But you can give it a try and tell me.
(sorry, but i really dont know anymore which file to delete, but i think this file isn't present on amule so that shoulndt be a problem ;) )