Because I am tired to see people having posted no less than 3289 times since more than seven years still asking questions to which they could easily find answers themselves, instead of keeping others busy holding their hands.

1 members found this post helpful.

please READ the wiki page that was posted in the FIRST post

from here
http://wiki.amule.org/wiki/Main_Page
there is a section on high id
http://wiki.amule.org/wiki/Get_HighID
on THAT PAGE
there is a link about firewalls -- mind you it is a bit ancient
http://wiki.amule.org/t/index.php?title=Firewall
fedora dropped the "core" in it's name 7 years ago

you also have to ask your self
"why is the wiki 7 years out of date "???????????
and why the last update on Sourceforge is from 2011
http://sourceforge.net/projects/amule/files/aMule/

and Emule is even more out of date
2010
http://sourceforge.net/projects/emule/files/



there is a reason i posted WARNINGS
even the original developers have left

1 members found this post helpful.

The level of understanding on how amule works shown in this topic does indicate that you should take the above warning very, very serious!

The bottomline is that you really shouldn't use the ed2k network anymore as it is bound to get your IP on nasty lists with the resulting actions. Have a look at usenet with something like sabnzbd instead. Far safer to use!

1 members found this post helpful.

I DID read those pages, but I could not get a hint as to why I am getting Low ID messages, which was the cause of my posting. Also, I don't have a firewall (not that I know), as I already stated.

Anyways, I don't intend to continue using amule in the future or any other program taht uses the ed2k network, as I made explicit some posts before. Thanks very much for the feedback.

FWIW - I have used aMule in the past and had some difficulty initially understanding how to not get the low ID message. The answer as John_VV pointed out is to have your internet access router forward the required ports to your machine. I had to do so on two different ISP provided routers and the method on each bore no resemblance to the other!

On one I was able to explicitly implement rules for port forwarding which was a little more work but made sense.

On the other I had to set up a DMZ with fewer specific options, which as I recall forwarded everything, although it was not really clear, and always seemed vague to me. In both cases I set up a firewall on the target machine and explicitly opened the desired ports when needed, and kept them closed at other times.

So, it is always necessary that the internet facing device (router) be set to forward the desired ports to the target machine. And it is always necessary that the target machine have those same ports opened. Neither of those is a setting withn aMule.

I know that is not a clear answer, but hope it provides some help or at least confirmation of what you need to do.