aMule Forum
English => aMule Help => Topic started by: Filya on October 17, 2005, 07:51:30 PM
-
Another strange behaviour...
aMule cannot connect to Kademlia, after several hours of running. I have HighID on ed2k and for sure no UDP ports are blocked except 466x. They are blocked also for TCP, so I use other ports and it works for ed2k.
What do I need to check to ensure it's not aMule problem? Or possibly, Kademlia has some specific requirements? e.g. port 4661 open?
If not, then, what am I doing wrong that makes aMule say I'm "firewalled" ?
-
Kademlia uses the same ports as ed2k: one TCP port of your choosing, one UDP at TCP+3, and another UDP port of your choosing. If your UDP ports really are available (open in your firewall and forwarded by your router), then I don't know what the problem is.
-
Originally posted by ken
Kademlia uses the same ports as ed2k: one TCP port of your choosing, one UDP at TCP+3, and another UDP port of your choosing. If your UDP ports really are available (open in your firewall and forwarded by your router), then I don't know what the problem is.
Thats strange. I'll check with ethereal, what is happening... BTW you mean that if I choose e.g. port 8000 for ed2k, then Kademlia will use the same TCP, 8000, and two UDPs 8003 and the one I set in preferences?
I mean - aMule listens to TCP 8000 and determines whether connecting client wish to use ed2k or Kademlia proto?
-
Yes, that's sort of correct. Kademlia is an extension of the ed2k protocol that aMule normally uses. Each message is tagged with protocol and opcode. There isn't a distinction between ed2k clients and Kad clients for most parts of the protocol (exchanging file data and information about files, etc.). For Kademlia-specific messages, they are tagged with Kademlia-specific protocol/opcode information.