aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: OS X aMule still firewalled  (Read 7522 times)

snipper

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 1
OS X aMule still firewalled
« on: December 02, 2006, 10:19:25 PM »
Hi there. I knew eMule for Windows from friends, but being a Mac user I didn't give it much notice. Until I found out about aMule.

Of course I tried it, but I keep getting the (Kad: firewalled) message in the utter right lower corner. Of course I read whatever I could find online about this. I opened the NAT poorts in the router to my fixed intern IP. Also, I openend these in the OS X firewall. (TCP 4662, UDP 4672, 4665), but this doesn't help. I tried the 'porttester' and it shows up green 'OK', so I guess the NAT setting is fine

Must say that there is very little usefull info to be found about troubleshooting aMule, specificly for OS X (I volunteer to put something online about it, if I ever find out anything usefull). Is there anything else I can do?
Logged

lionel77

  • Provider of Mac builds, Forum Mod
  • Hero Member
  • *****
  • Karma: 4
  • Offline Offline
  • Posts: 1107
  • Mac OS X 10.4 (Power Mac G5)
Re: OS X aMule still firewalled
« Reply #1 on: December 03, 2006, 12:10:33 AM »
snipper,
kad sometimes takes a longer time to realize that it is not firewalled -- the most important part is that the connection tester tells you that the client tcp port is properly forwarded.

If your kad arrow does not switch to green after a day, you could try to reduce the maximum number of connections to something like 100 and the "Max number of connections / 5 secs" to 7 or so (this second setting is in preferences->core tweaks). Some routers choke more easily on connections than others and might drop some of the connections if they are overwhelmed. Reducing those settings will prevent this from happening.

Oh, and if you are running another p2p client on that computer/network, you can also try to disable that or to reduce the number of connections for that client.

In terms of helping, anything you could do would be highly appreciated. :)
It probably would be a good idea to do some work on the wiki. I just find myself often already a little overwhelmed with doing the support here on the forums that I hardly find time to work on the docs and the wiki.
Logged
Current aMule CVS builds for OS X can be found here.

fernanda37

  • Newbie
  • Karma: 1
  • Offline Offline
  • Posts: 1
RE: OS X aMule still firewalled
« Reply #2 on: January 22, 2007, 04:10:41 AM »
Hi,

I'm very new to aMule (having used eDonkey for years now)...and I'm experiencing the same problem you're having with the "Kad: firewalled" status.  I'm pretty much in the dark like you are, and also having read all the help that there is available for us Mac user out there.  With two exceptions - I don't even know how to use the "port tester" you mentioned!  And I'm not even sure I did redirect my ports correctly...on my Apple airport!  Could you tell me how to test my ports, please?

Thanks very much in advance!
Fernanda.
Logged

phoenix

  • Evil respawning bird from aMule Dev Team
  • Developer
  • Hero Member
  • *****
  • Karma: 44
  • Offline Offline
  • Posts: 2503
  • The last shadow you'll ever see
RE: OS X aMule still firewalled
« Reply #3 on: January 22, 2007, 10:23:18 PM »
Hi Fernanda,

To test your ports, go to this page:
http://www.amule.org/testport.php

Type the number of your TCP port. You can find this number in the preferences tab of aMule.

We have a wiki with lots of information here:
http://www.amule.org/wiki/index.php/

Good luck!
Logged

ngllgn

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 49
RE: OS X aMule still firewalled
« Reply #4 on: January 25, 2007, 12:15:36 PM »
Hello Snipper and Fernanda,

I'm also new to aMule and have no experience of other P2P progams other than Limewire. I have found that following the aMule set-up instructions to the letter led me to exactly the problems you are experiencing...to start with.

And then, somehow magically, the connection status improved steadily after a day or two, and everything (including KAD, which took the longest) became 'unfirewalled' without my having to do anything more, and I was given a high ID. So it may just be a question of patience.

Good luck.
Logged

ngllgn

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 49
RE: OS X aMule still firewalled
« Reply #5 on: January 27, 2007, 12:38:33 PM »
Phoenix

Is there a similar easy way to test UDP ports?

Thanks, Nick
Logged

wuischke

  • Developer
  • Hero Member
  • *****
  • Karma: 183
  • Offline Offline
  • Posts: 4292
RE: OS X aMule still firewalled
« Reply #6 on: January 27, 2007, 02:12:29 PM »
Quote
Originally posted by ngllgn
Phoenix

Is there a similar easy way to test UDP ports?

Thanks, Nick

No, there's none (at least I don't know one).

What I guess how the TCP-test works (TCP handshaking): The tester programm sends an 'Syn' package to your TCP port. aMule answers giving an 'Syn+Ack' package followed by another 'Ack' package by the tester.

'Ack' means acknowledgment of the received package. By reveiving this package the tester program knows, that it could reach your TCP port and that you are able to send as well.

Now, there's no such thing for UDP. Packages are not acknowledged. This is faster as the sender doesn't have to wait for acknowledgment answers, but by default less secure.
Logged

phoenix

  • Evil respawning bird from aMule Dev Team
  • Developer
  • Hero Member
  • *****
  • Karma: 44
  • Offline Offline
  • Posts: 2503
  • The last shadow you'll ever see
Re: OS X aMule still firewalled
« Reply #7 on: January 27, 2007, 03:05:13 PM »
I guess it could be done by someone with some web scripting experience. You just have to find the right message of the protocol in order to obtain an answer.
Logged

ngllgn

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 49
RE: OS X aMule still firewalled
« Reply #8 on: January 27, 2007, 08:35:39 PM »
Thanks wuischke and phoenix for the explanation and advice. Scripts particularly and protocols are beyond me at this stage, but I may learn about them one day.

A thought occurs to me that perhaps getting a good KAD connection might depend on one's 'credit rating', related to what one has uploaded or shared in the past. Is this the case? If it were so, it would explain why new users of aMule, and the KAD servers in particular, get frustrated to start with.

Nick
Logged

zaque

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 15
  • Live in Rochester, NY. Love to cook, and garden. I also make my own wine and some beer. I recently graduated with a degree in Agriculture, but am doing electrical work right now. I'm gay and single.
    • http://Yahoo
Firewalled
« Reply #9 on: January 30, 2007, 01:56:03 AM »
Snipper mentioned: " Also, I openend these in the OS X firewall. (TCP 4662, UDP 4672, 4665)"  Do I have to do this and if so how.  I'm rather computer illiterate.

I'm having the same problem of yellow arrows on the globe and it saying:  Kad Firewalled.  I've got the Router ports open all three of them.  I've tested and its giving me the message:

Error: TCP port 4662 is unavailable. Make sure your firewall or router is allowing/forwarding this TCP service port and your ED2K client is running (i.e. aMule, eMule).
Detailed Error Message
TCP Error 110 Connection refused

Explanation
The connection timed out, meaning the port is being blocked or incorrectly forwarded by a firewall or your computer is turned off :)

I'm trying to get a High id.

Thanks for all the help.

Rich
Logged

wuischke

  • Developer
  • Hero Member
  • *****
  • Karma: 183
  • Offline Offline
  • Posts: 4292
Re: OS X aMule still firewalled
« Reply #10 on: January 30, 2007, 10:01:14 AM »
Hi zaque!

Was aMule running while you did the test?
Logged

zaque

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 15
  • Live in Rochester, NY. Love to cook, and garden. I also make my own wine and some beer. I recently graduated with a degree in Agriculture, but am doing electrical work right now. I'm gay and single.
    • http://Yahoo
firewalled
« Reply #11 on: January 31, 2007, 12:12:11 AM »
Yes aMule was running.

I just solved my problem and It was simple, but the info was hidden in the forums.  Posted by:  lionel77  

Also, if you are running any firewall software (e.g., OS X's built-in firewall, which you can control via System Preferences->Sharing->Firewall) on your computer, you need to open the above ports there as well.


This has only been explained once that I've seen in the Forums.  It may help a lot of others

When in Firewall select other, For TCP  insert 4662; for UTP insert 4665  4672; in description type aMule; select make changes button, and close the windows.  

I restarted my computer and aMule was green.

Thanks all.
« Last Edit: January 31, 2007, 12:48:07 AM by zaque »
Logged

milo

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 1
Re: OS X aMule still firewalled
« Reply #12 on: September 11, 2007, 11:30:18 AM »
Hello everybody, it's the first time I've been using aMule (adunanza version) and I'm having trouble with the firewall settings.

I'm on mac osx 10.3.9 and in the firewall setting window have no UTP line to insert port number in, just TCP. At present I put all port numbers in the TCP line that reads 4662, 4665, 4672 but I guess it's wrong.

also, I'm on a wireless network using airport and don't know how to configure its settings either.

i've done the test port and it obviously stated the port was unavailable just as happened to zaque, but I had already inserted the TCP port number in the firewall setting window.

all in all, I don't know what else to do... aMule is running but downloads are scarce  :-[
pls help....
thanx!
milo
Logged