aMule Forum

English => en_Bugs => Topic started by: lostinthecity on May 21, 2005, 01:51:17 AM

Title: aMule 2.0.0/2.0.1 is crashing my ADSL router
Post by: lostinthecity on May 21, 2005, 01:51:17 AM
I'm running aMule on Mac OS X Tiger and connect to the internet through a Safecom ADSL router. Both aMule 2.0.0 and 2.0.1 crash the router and disconnect me from the internet after they've been running for about twenty minutes, causing me to have to reset it before I can get back online. I've tried reducing the 'max connections' and 'max new connections / 5 secs' settings as recommended in other posts, but my router is still disconnecting me from the internet when aMule is running regardless of how low these values are set at.

I've reverted back to using 2.0.0rc8, which works perfectly for days on end even with 'max connections' set to 1500 and 'max new connections / 5 secs' set to 20, so this definitely seems to be an issue that's being caused by 2.0.0 onwards.  Can anyone offer any suggestions?

Thanks!
Title: RE: aMule 2.0.0/2.0.1 is crashing my ADSL router
Post by: JohnGH on June 03, 2005, 02:23:15 PM
Have you seen this post?

http://forum.amule.org/thread.php?threadid=5665&sid=

I have been having the same problem, much to my flatmates' disgusts!
Title: Re: aMule 2.0.0/2.0.1 is crashing my ADSL router
Post by: stefanero on June 03, 2005, 03:28:28 PM
most often the problem is the max connection / 5sec under aMule-tweaks setting

if this setting is to high, cheap routers like dlink for example will crash. never heard of your router but ok.
I would check taht if I where you, and back in the rc8 times, when you say it did not crash, thing is taht rc8 had a lot of buggy connections, which might have effected your router different
in the 2.0.0 and 2.0.1 those buggy connections are now fixed, which increases the network traffic, and becuase of this increased traffic your router might crash
Title: Re: aMule 2.0.0/2.0.1 is crashing my ADSL router
Post by: skolnick on June 03, 2005, 06:39:10 PM
I had exact same problem. Problem was my cablemodem was faulty. Changing it for a new one solved the problem.

Regards.