aMule Forum

English => aMule Help => Topic started by: oakfinger on February 11, 2006, 05:31:16 PM

Title: global search behaves like local
Post by: oakfinger on February 11, 2006, 05:31:16 PM

Whenever I use 'Global search', the progress bar moves as usually, but the only search results I get are the ones from the connected server. Any suggestions? In this forum there are threads about a similar problem with previous versions of aMule, but I couldn't glean anything helpful.
I'm with a default installation of aMule 2.1.0 and wxGTK 2.6.2 on Slackware 10.1. And if that is of any significance, aMule seems to use only port 4662.

Thank you for your time.

Title: Re: global search behaves like local
Post by: stefanero on February 11, 2006, 05:57:41 PM

well if you are connected to rb2 this might be true, since on rb2 are like 60% of the complete ed2k network

but maybe try to connect to a little smal server, you will definetly notice a difference....

Title: Re: global search behaves like local
Post by: oakfinger on February 11, 2006, 07:08:03 PM

Quote

Originally posted by stefanero
well if you are connected to rb2 this might be true, since on rb2 are like 60% of the complete ed2k network

but maybe try to connect to a little smal server, you will definetly notice a difference....

no, no, I've tried different servers, but the problem persists.

Title: Re: global search behaves like local
Post by: stefanero on February 11, 2006, 07:12:53 PM

well works here,

if I connect to a small server and search for knoppix I get 3results
with global I get more then 300 after a couple secs

Title: Re: global search behaves like local
Post by: deltaHF on February 11, 2006, 08:09:38 PM

well, be sure your udp port is open for amule also

Title: please, excuse my verbosity
Post by: oakfinger on February 12, 2006, 05:08:09 PM

Quote

Originally posted by deltaHF
well, be sure your udp port is open for amule also

How do I do that?

Or maybe I wasn't specific enough. I used to be with aMule-2.0.0rc8 and it worked fine, but for the last month 'search' wasn't returning any results, only a message that my client was too old and that I should upgrade it. And so I did - I tried versions 2.0.3 and 2.1.0, but there was this local-global problem. Now when I scan the amule UDP port with nmapfe (which always reports it as 'closed') aMule outputs this:
'MuleUDPSocket: Socket died. Recreating socket.
MuleUDPSocket: Shutting down Server UDP-Socket
MuleUDPSocket: Created Server UDP-Socket at port 4665'
I tried different ports and running aMule as root, but to no avail. Another thing is that, despite having a HighID, my kademlia status is firewalled.
Any clues?

Title: Re: global search behaves like local
Post by: Kry on February 12, 2006, 05:12:32 PM

If kad is firewalled, is because the UDP port is closed