aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: Can change of Incoming directory cause low ID?  (Read 6542 times)

ngllgn

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 49
Can change of Incoming directory cause low ID?
« on: March 05, 2011, 11:34:51 AM »

Yesterday I reorganised the folders and files on my computer somewhat. This resulted in, among other things, the completed downloads folder being in a different place.

The incoming directory in aMule/Preferences used to be /Users/myname/Documents/aMule Downloads.

Before I reorganised the folders and files, aMule was working perfectly. When I reorganised the files, I did not change the incoming directory path. Today, I have a warning that I have received a low ID, that KAD is firewalled, and the two arrows are yellow.

So I have changed the incoming directory to /Users/myname/Downloads/aMule Downloads and saved that change. I still get the three errors. Any help would be appreciated. Many thanks.

PS I have not changed anything on the router, the Mac firewall settings, NAT, port forwarding or opening or anything else.
Logged

ngllgn

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 49
Re: Can change of Incoming directory cause low ID?
« Reply #1 on: March 05, 2011, 02:39:03 PM »

Quote
Incoming directory settings are totally unrelated to port settings.

That's what I supposed. Good to know.

Quote
1) Did you change the UDP/TCP port configuration in amule.conf?

No I didn't.

Quote
2) I am not a Mac user, but as you mentioned Mac I recall some thread where it is said that the Mac firewall stores a signature for each application. If you changed aMule's path, maybe its signature changed as well, and access is no more granted by the Mac firewall. It is worth checking.

So this must be the key. I went to System Preferences/Security/Firewall/Advanced and deleted aMule from the list of applications. Then I shut the computer down, rebooted, went to the same place and added aMule back in so that the line next to aMule again has a green light and reads 'Allow incoming connections'. No result. I guess you must be right that the computer is somehow remembering from before the version update, although why that would affect anything I don't know.
Logged

ngllgn

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 49
Re: Can change of Incoming directory cause low ID?
« Reply #2 on: March 05, 2011, 02:47:24 PM »

I forgot to add, and it may or may not be relevant, that an option in Security 'Automatically allow signed software to receive incoming corrections' is ticked.

Do I have anything to lose by deleting the aMule application from the computer (on the basis that the Mac firewall should not be able to find anything or remember anything on a reboot) and then reinstalling it?
Logged

ngllgn

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 49
Re: Can change of Incoming directory cause low ID?
« Reply #3 on: March 14, 2011, 04:12:27 PM »

So, I deleted
aMule application from Applications folder
aMule from the Mac's System Preferences/Security/Firewall/Advanced
aMule settings in the router's firewall

then

reinstalled aMule
reinstated aMule in the Mac's System Preferences
installed a new unused router from scratch and reset the TCP and UDP ports in the router for aMule

but still get a low ID and KAD firewalled.

I'm beginning to think I am going to have to give up on aMule altogether unless someone can help me troubleshoot this problem. This is a shame as I have been using it for a while and it has done me very well up until now.
Logged

ngllgn

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 49
Re: Can change of Incoming directory cause low ID?
« Reply #4 on: March 16, 2011, 06:46:43 PM »

I understand your frustration, personally I believe this is much more a firewall/port forwarding problem than something related to the aMule application itself.

Thank you so much for offering to help out.

Quote
Did you accidentally activate UPnP in connection preferences?  Please could you post aMule's log here (removing any personal data before) ?

No, I don't believe I did. I have attached an image of this preference selection, although I'm unsure, before posting it, whether the image will be seen correctly in this post.

Here is the log generated WITHOUT adding aMule to System Preferences/Security/Firewall/Advanced

2011-03-16 18:23:08: Starting aMule 2.2.6 using wxMac v2.8.10
2011-03-16 18:23:08: Creditfile loaded, 0 clients are known
2011-03-16 18:23:08: Loading IP-filters 'ipfilter.dat' and 'ipfilter_static.dat'.
2011-03-16 18:23:08: Loaded 0 IP-ranges from '/Users/myusername/Library/Application Support/aMule/ipfilter.dat'. 0 malformed lines were discarded.
2011-03-16 18:23:08: Loaded 0 IP-ranges from '/Users/myusername/Library/Application Support/aMule/ipfilter_static.dat'. 0 malformed lines were discarded.
2011-03-16 18:23:08: External connections disabled in config file
2011-03-16 18:23:08: Created Server UDP-Socket at port 54665
2011-03-16 18:23:08: Created Client UDP-Socket at port 54672

2011-03-16 18:23:08:  - This is aMule 2.2.6 using wxMac v2.8.10 based on eMule.
2011-03-16 18:23:08:    Running on Mac OS X (Darwin 10.6.0 i386)
2011-03-16 18:23:08:  - Visit http://www.amule.org to check if a new version is available.

2011-03-16 18:23:08: Loaded 248 flag bitmaps.
2011-03-16 18:23:08: Loading server.met file: /Users/myusername/Library/Application Support/aMule/server.met
2011-03-16 18:23:08: 13 servers in server.met found
2011-03-16 18:23:08: No part files found
2011-03-16 18:23:08: Found 68 known shared files
2011-03-16 18:23:08: Connecting
2011-03-16 18:23:08: Connecting to Master Server 1 (83.233.30.55 - 83.233.30.55:4500) using protocol obfuscation.
2011-03-16 18:23:08: ThreadScheduler: Completed task 'AICH Syncronizing', 0 tasks remaining.
2011-03-16 18:23:08: Connected to Master Server 1 (83.233.30.55:4500)
2011-03-16 18:23:08: Connecting to !-= Porn Pit =-! (88.80.28.48 - 88.80.28.48:4321) using protocol obfuscation.
2011-03-16 18:23:08: Connected to !-= Porn Pit =-! (88.80.28.48:4321)
2011-03-16 18:23:09: Your copy of aMule is up to date.
2011-03-16 18:23:09: WARNING: Master Server 1 (83.233.30.55:4500) - NG : Your 54662 port is not reachable. Please review your network config.
2011-03-16 18:23:09: Connection established on: Master Server 1
2011-03-16 18:23:09: New clientid is 13265360
2011-03-16 18:23:09: WARNING: You have received Low-ID!
2011-03-16 18:23:09:    Most likely this is because you're behind a firewall or router.
2011-03-16 18:23:09:    For more information, please refer to http://wiki.amule.org

Here is the log generated WITH adding aMule to System Preferences/Security/Firewall/Advanced

2011-03-16 18:34:50: Connecting
2011-03-16 18:34:50: Connecting to Master Server 1 (83.233.30.55 - 83.233.30.55:4500) using protocol obfuscation.
2011-03-16 18:34:50: Connected to Master Server 1 (83.233.30.55:4500)
2011-03-16 18:34:51: Connecting to !-= Porn Pit =-! (88.80.28.48 - 88.80.28.48:4321) using protocol obfuscation.
2011-03-16 18:34:51: Connected to !-= Porn Pit =-! (88.80.28.48:4321)
2011-03-16 18:34:51: WARNING: Master Server 1 (83.233.30.55:4500) - NG : Your 54662 port is not reachable. Please review your network config.
2011-03-16 18:34:51: Connection established on: Master Server 1
2011-03-16 18:34:51: New clientid is 13322212
2011-03-16 18:34:51: WARNING: You have received Low-ID!
2011-03-16 18:34:51:    Most likely this is because you're behind a firewall or router.
2011-03-16 18:34:51:    For more information, please refer to http://wiki.amule.org

This second log looks better than the first log. By including both, I'm hoping someone far more knowledgeable (not difficult) than I, may get a clue.

I have also attached a picture of what I put into the router configuration page, and the error message I get EVERY time I try to manually confirm the port I wish to forward/open. I don't understand this message at all, as I followed exactly the same process for another torrent client, Transmission, and the correct port was opened and forwarded immediately.
Logged

ngllgn

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 49
Re: Can change of Incoming directory cause low ID?
« Reply #5 on: March 16, 2011, 06:48:46 PM »

I meant to add this image too.
Logged

Stu Redman

  • Administrator
  • Hero Member
  • *****
  • Karma: 214
  • Offline Offline
  • Posts: 3739
  • Engines screaming
Re: Can change of Incoming directory cause low ID?
« Reply #6 on: March 16, 2011, 10:45:32 PM »

Why 54663? And what is the heading above all the port fields? We don't know your router by heart.
Logged
The image of mother goddess, lying dormant in the eyes of the dead, the sheaf of the corn is broken, end the harvest, throw the dead on the pyre -- Iron Maiden, Isle of Avalon

ngllgn

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 49
Re: Can change of Incoming directory cause low ID?
« Reply #7 on: March 17, 2011, 11:34:48 AM »

Why 54663?


Why indeed? My typing error, now corrected.

Quote
And what is the heading above all the port fields? We don't know your router by heart.

Headings above port fields are source port start, source port end, destination port start and destination port end.

I have now been able to add the TCP port for each of the four port fields successfully. If I try immediately to add the UDP ports, the server always drops the connection, as per the error message in my previous post. The only way I have found to get round this is to close the router configuration page, reopen it, and then add one of the UDP ports, close the router configuration page again, reopen it and add the second UDP port. I hope this work-around may be useful for others with a Vodafone HG556a router, as this difficulty may well be a peculiarity of this router alone.

My only minor concern now is whether I need to worry about being connected to a server called 'Porn Pit'. This is the server link I am using http://gruk.org/server.met.gz and a fair number of the 13 servers shown have the word 'sex' in them. Might a different server link be better for me given that I am not interested in downloading files with sex in them, and if yes, where might I find that server link? Or does a server with the word 'sex' in its name not necessarily host more files of that kind than one without it? Sorry if this is off-topic here.

Thank you so much for your sorely tested patience.
Logged

Stu Redman

  • Administrator
  • Hero Member
  • *****
  • Karma: 214
  • Offline Offline
  • Posts: 3739
  • Engines screaming
Re: Can change of Incoming directory cause low ID?
« Reply #8 on: March 17, 2011, 08:26:07 PM »

So - do you get a high id now?

Servers have become kind of messy. I use only Kad. Anyway, if it's listed on gruk.org it should be ok, no matter what the name is.
Logged
The image of mother goddess, lying dormant in the eyes of the dead, the sheaf of the corn is broken, end the harvest, throw the dead on the pyre -- Iron Maiden, Isle of Avalon