aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: Firewalled KAD, seems to be software trouble (perhaps Leopard incompatibility?)  (Read 3052 times)

Lackbeard

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 2

Hello there, fellow mulers. I hope you can help me with a problem.

Recently, I seem to have been unable to sustain my Kad un-firewalled status in aMule OSX. When I connect, the pattern is always the same: First I get high id and un-firewalled status (two green arrows). Then after a while, my download rates drop markedly, and then after a few hours, the Kad status turns to firewalled. The high id stays there though (first arrow stays green).

If I close and reopen aMule at this point, or simply disconnect from the server, choose another one and reconnect, the cycle repeats: Fine download rates, two green arrows, but only for a while.

The pattern I get testing with the web port tester ( http://www.amule.org/testport.php ) is consistently this:

* First few minutes after starting aMule -> web test -> instant "success".
* Been running aMule for a while -> web test -> some ten seconds lag -> then "connection refused".
* No running aMule client -> web test -> instant "connection refused".

In other words, the web port test corresponds with my download rates and (with some lag) the Kad firewalled state (second arrow). It doesn't correspond with my server high id status (first arrow).

I have tried various ports and port ranges, and I don't think the problem is bad NAT setup. My router is a D-Link DI-824VUP+. I'm using aMule 2.1.3 stable on OSX Leopard 10.5.1.

What could cause such behaviour? Any good ideas?

Best regards,
Lack
Logged

d1g1tal

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 2

the same problem here, my amule 2.1.3 was running under OSX 10.4 without any problems and after i upgraded to leopard im getting only low id and firewalled connect signs.
the router port forwarding is still set to be working so thats not the problem.

any suggestions?
Logged

Kry

  • Ex-developer
  • Retired admin
  • Hero Member
  • *****
  • Karma: -665
  • Offline Offline
  • Posts: 5795

Check Leopard's firewall?
Logged

d1g1tal

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 2

thanks, so simple but it works :)
Logged

Lackbeard

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 2

Not for me, it doesn't. My Leopard firewall setting has been "allow all incoming connections" all the way.

My firewall settings:
sudo ipfw list
65535 allow ip from any to any
Logged

jb680

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 1

I too have LowID only  since upgrading to Leopard.  Any solution yet?
Thanks.
Logged

donmas

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 1

After I changed the default ports (TCP and UDP), my KAD started being shown as firewalled too. After deleting the nodes.dat from /Users/[username]/Library/Application\ Support/aMule and restarting amule, KAD was connected again... strange.
Logged