aMule Forum
English => Multiplatform => Mac OSX => Topic started by: lars on February 14, 2009, 11:57:11 AM
-
Hello Everyone!
I'm new here - and hope to find help!
I've downloaded aMule 2.2.3 and installed it on my Intel Leopard 10.5.6 MacBook - but I can't stop it from getting a Low-ID!
I'm using a wireless Zyxel P-2602HW-D1A and I have port forwarded 43829 to 43830 - and used the 43829 at the Standard cilient TCP Port and the 43830 at the Extended client UDP Port.
I've a bootcamp-partition and installet eMule there, with the same ports - and it works fine (Hi-ID)!
Can anyone help my, please?
Thank you :-)
-
Thanx - but it wasn't that :-)
I kind of solved the problem, by deactivating the "Extended client UDP Port" and - as aMule suggested - the Kademlia network. It gave me a HI-ID.
Can anyone explain why? :-)
And can I get the Kademlia to work somehow?
Thank you
-
And can I get the Kademlia to work somehow?
Not without enabling the "Extended client UDP Port".
Can anyone explain why? :-)
Dunno. Strange, however.
-
I kind of solved the problem, by deactivating the "Extended client UDP Port" and - as aMule suggested - the Kademlia network. It gave me a HI-ID.
I can't believe aMule suggested you deactivate Kad.
-
I kind of solved the problem, by deactivating the "Extended client UDP Port" and - as aMule suggested - the Kademlia network. It gave me a HI-ID.
I can't believe aMule suggested you deactivate Kad.
You can try it out yourself: Choose "Extended client UDP Port" and press OK... :-)
But why on earth is "Extended client UDP Port" or Kad giving me a LO ID?
-
Well, it says "enable UDP port or disable Kad", but accepts the setting after all. It should rather grey out the UDP port box while Kad is enabled.
No idea why it should give you low id. I'm getting high even if I configure an unreachable UDP port.
-
Hi, guys, I seem to have no luck with a high id. Tried all suggested on the topic, nothing worked. Got mobile internet from vodafone. Could it be that? I have no wired net to test things, unfortunately. Tried even disabling firewalls(little snitch too) still didn't do the trick. Then I tried to turn them back on and even after replacing prefs in both firewalls, still no luck... :( Ty for suggestions in advance... Should I try v 2.2.2?
-
Uncheck the protocol obfuscation.
-
IT IS unchecked, doesn't do the trick... :(
-
Do you have a public internet IP with your connection? Most mobile connections share one public IP, i.e. it works just like a router - only you have no control about this router and hence you can't forward the ports.
-
It is highly possible that THAT is the answer... :(
Yet, how should I find out whether it is a public IP or otherwise? Is there a way to check this?
-
If your TCP port is 4662 then your extended UDP port is 4662 + 3 = 4665.
So I think you also have to forward this UDP port in your firewall.