aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: global search behaves like local  (Read 3724 times)

oakfinger

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 3
global search behaves like local
« 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.
Logged

stefanero

  • Some Support
  • Developer
  • Hero Member
  • *****
  • Karma: 8
  • Offline Offline
  • Posts: 4235
Re: global search behaves like local
« Reply #1 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....
Logged
In its default setup, Windows XP on the Internet amounts to a car
parked in a bad part of town, with the doors unlocked, the key in
the ignition and a Post-It note on the dashboard saying, "Please
don't steal this."

oakfinger

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 3
Re: global search behaves like local
« Reply #2 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.
Logged

stefanero

  • Some Support
  • Developer
  • Hero Member
  • *****
  • Karma: 8
  • Offline Offline
  • Posts: 4235
Re: global search behaves like local
« Reply #3 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
Logged
In its default setup, Windows XP on the Internet amounts to a car
parked in a bad part of town, with the doors unlocked, the key in
the ignition and a Post-It note on the dashboard saying, "Please
don't steal this."

deltaHF

  • Evil Admin
  • Former Developer
  • Hero Member
  • *****
  • Karma: 6
  • Offline Offline
  • Posts: 3920
  • .. Legends may sleep, but they never die ..
    • http://www.amule.org
Re: global search behaves like local
« Reply #4 on: February 11, 2006, 08:09:38 PM »
well, be sure your udp port is open for amule also
Logged

oakfinger

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 3
please, excuse my verbosity
« Reply #5 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?
Logged

Kry

  • Ex-developer
  • Retired admin
  • Hero Member
  • *****
  • Karma: -665
  • Offline Offline
  • Posts: 5795
Re: global search behaves like local
« Reply #6 on: February 12, 2006, 05:12:32 PM »
If kad is firewalled, is because the UDP port is closed
Logged