aMule Forum
English => Multiplatform => Mac OSX => Topic started by: Mars_Comet on December 16, 2006, 07:40:58 AM
-
Hello, I recently installed teh Amule with no complications, however, I'm getting "Low ID" when i start the program, so my download speed is usually close to none. :)
Reading the Faqs and with the help of portforward.com I opened the 4662 port in both my computer and my router, I restarted my computer, and I keep getting Low-ID.
Is there anything I forgot to do in order to avoid this?
Thanks for your replies, I hope you can help me. :))
-
Maybe this is helpful:
You need to forward the ports that aMule uses in your router. Take a look at http://portforward.com/routers.htm, that page has detailed step-by-step instructions for pretty much every router on the market.
aMule uses three ports (see Preferences->Connection) that need to be forwarded:
- a client TCP port
- a client UDP port (this is the above port +3)
- and an eMule extended UDP port
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.
You can use the connection tester (http://www.amule.org/testport.php) to check whether the client TCP port can be reached from the outside, that is, whether it is forwarded properly in your router and not blocked by any firewall software.
Good luck. :)
-
Ok, I opened 3 different ports:
TCP 4662
UDP 4672
UDP 4665
my Mac firewall is offline, and my router says these ports are opened, but i STill get this message from the port test:
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 111 Connection refused
My aMule is running, so I don't really know what to do now... :)
-
Opening the ports is not sufficient, you have to forward them to you local IP as well. See portforward.com for more information.
-
Lionel, is there an UPnP enabled version of aMule for Mac? Would be interesting to test it in a different platform.
-
Yes, I opened the ports via portforward.com, So i Guess i am forwarding them too. there is no step-by-step with the Amule application, so I used the Default Guide about my router.
I did exactly what the guide said, opening and forarding the 3 ports. And it is still not working.
what else can I do? :)
-
Originally posted by phoenix
Lionel, is there an UPnP enabled version of aMule for Mac? Would be interesting to test it in a different platform.
Yes there is -- I'm running r7010 on my machine as we speak. Problem is, that version suffers from the issues that I posted recently on the testing forum: the shuffled category icons & labels in the preferences and the absence of graphs on the statistics page. So I'm not sure I feel comfortable releasing that version into the wild.
-
Well, there's a local Mac OS X firewall as well, but it is usually disabled.
-
Yeah, My Mac Os firewall is disabled.
-
OK, then I know only one way:
Delete all port forwarding, delete the static IP for your Mac.
Reset the static IP and re-forward the ports.
This usually helps...usually...
-
Ok, can you tell me how to delete my static IP? Also won't it affect other things on my mac?
-
Well, delete is the wrong word: Set it to another ip address or activate dhcp and then reset it to your old ip. My wrong.
-
Originally posted by lionel77
Originally posted by phoenix
Lionel, is there an UPnP enabled version of aMule for Mac? Would be interesting to test it in a different platform.
Yes there is -- I'm running r7010 on my machine as we speak. Problem is, that version suffers from the issues that I posted recently on the testing forum: the shuffled category icons & labels in the preferences and the absence of graphs on the statistics page. So I'm not sure I feel comfortable releasing that version into the wild.
KEN HELP!
(maybe he has super-hearing :D )
-
Hi
just been reading through these posts and im having the same problem only i've just done the connection test and its saying 4662 is availible but im still getting low id, i've disabled the firewall on my computer and the bt home hub but its still saying low id, even limewire and frostwire are saying firewall up, i've gone into bt hub manager and added emule to the games and sharing applications, is emule the same ports as amule? because amule wasn't on the list.
been trying to sort this out for over a month now! its driving me crazy. any ideas ?
-
Dear Mars Comet,
Although they aren't supposed to (at least in the US), some ISPs block or throttle down certain ports to discourage p2p users. (See http://www.amule.org/wiki/index.php/Extended_client_UDP_port).
If this is the cause of your trouble, you can avoid such ISP interference by selecting port numbers other than the defaults. (I use 5992 and 5995, for example.) They can be changed in Preferences --> Connection.
Whatever numbers you choose, be sure they are not reserved for other connections you currently use or may wish to use in the future. (http://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers)
And, of course, don't forget to change your firewall and router settings to accomodate your new settings.
============
To tinkerbellarulez:
Yes, eMule and aMule use the same default ports. Limewire, FrostWire and Bearshare use different ones as their defaults: 6346 and 6347. You might wish to try the same suggestion I offered to Mars Comet above for both applications.
============
To both:
Other than the reason I mentioned at the beginning, I can't come up with any other causes, unless there's something you don't know about (such as your ISP putting you behind a proxy server). It sounds as though you have performed all the necessary tests and tweaks to get aMule up and running with a High ID.
Best of luck.
-
i also tried everything except for the last suggestion (which is the deletion of static ip, etc cuz I dont know how to do it. help!). the emule on my desktop is workin but the amule here on my new mac isnt.
for the other users, were the last suggestion helpful? please update asap.
merci!
-
solved it. sorry.
-
Is there anyplace I can check if the ports are open or not without Amule being opened?
Edit: Changed my Amule ports to TCP 5556, UDP 6669, UDP 5559, and I'm still getting Low-ID.
I have forwarded now the 6 ports with no success... I dont now how to check if those ports are really forwarded, the port tester at the wiki says my emule isnt on, while it is...
-
Mars_Comet,
To check what ports are in use by aMule, do a "netstat -ntualp | grep amule".
-
Can you tell me how to do that?
Thanks :)
-
You need to open a console and type the command I gave you. On kde you can for example execute "run" on the programs menu, and type "konsole".
-
On the Mac, you run the Terminal application found in Applications > Utilities. Then type the command and press return.
However, the command that phoenix suggested doesn't work on Mac OS X. The version of netstat is different. Here's a command that produces similar output:
lsof -ani -c amule | grep -v -- '->'
-
I have encountered the same problem as Mars Comet but with this difference: I have been running aMule for 3 months without any problems with Low Identity, or anything else for that matter. Since sometime last week, I began experiencing the same things Mars Comet described. I have tried every suggestion made here without success. I even tried disconnecting Airport & accessing the internet via Ethernet, but to no avail. Using the Terminal, I was able to determine that aMule was running, yet the port test at the wiki help pages tells me ED2K is not running. Is a BIG puzzlement...........
PS-- The only changes I've made to the Mac since starting to use aMule have been the Software Updates sent out by Apple. In both cases they were Security Updates. Might this be a factor ? I also notice the following in the Status Report from time to time:
"Status Text
ServerUDP: Received invalid packet, protocol (0xad) and opcode (0xa3)"
What's up with that ???
-
Dear Elmo,
The invalid UDP packet is a commonly seen error which is normally of interest only to aMule developers who are in the process of debugging, and is of no consequence to the general user.
In this case, however, it tells us that at least aMule is working well enough to notice UDP packets -- although the one it complained about could be from just about anywhere and any source -- not necessarily an aMule server or client.
There is another way besides the port test mentioned in the wiki to verify your ports are working. As before, run your Ethernet cable directly into the modem and disable OS X's internal firewall and any other firewall applications. Start aMule. A company called Gibson Research Corporation has an online service called "Shields Up!" to probe ports. It's intended for PCs to use in their never-ending battle with hackers, but will serve the occasional Mac user well enough. ;)
Once on the GRC page, scoot to the bottom and click 'Proceed." Safari will complain it's a non-secure form (it may even complain twice). If you don't trust GRC -- or my suggestion to use them, for that matter -- to access your computer without your firewall on, then Google around a bit to see what the rest of the world thinks of the service.
On the page which appears after clicking on 'proceed,' type the range of ports you're using into the text-entry box (surrounded by the light blue border) and click on "User specified Custom Port Probe." Unlike most tests, you want to fail this one -- that is, to have solicited TCP packets accepted and aMule's primary TCP port seen as open. The more things in RED, the better.
If you are successful, then work your way backwards checking your ports while examining your settings for your Airport, and your firewalls.
Neither of Apple's Security updates have done anything to affect aMule's ability to connect.
-
Elmo, it sounds like your ISP has implemented some sort of filtering to prevent P2P traffic from making it to your Mac. It might be based on the port numbers aMule uses, in which case you can bypass it by changing the ports. More likely, though, is that it's based on the contents of the packets. In that case, there are only two solutions: switch ISPs, or wait for protocol obfuscation to be implemented in aMule.
-
I have a slightly different problem. I too have a low ID. I have disabled the firewall on my Mac G5 1.8 dual processor PPC. I'm using OS X 10.4.8 and aMule 2.1.3
From my computer I go to a Netgear Switch FS 108 then to my Sun Rocket VOIP "gizmo" then to my Roadrunner internet "modem".
aMule also tells me it is firewalled. The test tells me the port 4662 is not available, etc. What do I do? I don't know how to configure port forwarding as there seems to be nothing written on it. I can't find it in apple.com either.
Both Sun Rocket and Roadrunner technicians say they don't block or restrict ports.
I'd apreciate any help anyone can give me. I've spent hours trying to figure this out. Sorry I'm rather computer illiterate.
http://forum.amule.org/images/bunfirlite/smilies/baby.gif
Rich
I after I wrote this plugged my computer directly into the ISP modem; no VOIP box or switch inbetween, and I get the same message that it's firewalled. and I still show low ID.
-
Ok, I found what the problem was, My router wasn't correctly forwarding the ports.. I changed my router and the firewall worked correctly and now I don't get Low-ID...
Thanks everyone for the help! :D
-
I'm not using a router.
I'm using a switch which allows everything through unhindered. It has no port forwarding. I do have a VOIP "modem" and my ISP modem infront of the switch though. Both claim they are not restricting any signals to or from any ports.
I also have switched to CVS from 2.1.3 same results Low ID.
Thanks,
Rich