External Connections

2006-11-22T17:29:37Z

84.9.233.187:

External Connections is the ''bi-directional'' way [[aMule]] has to communicate with external utilities, specifically:

* [[aMuleWeb]]
* [[aMuleCMD]]
* [[aMuleGUI]]

So, when a user is using one of these programs, it is sending the commands through the External Connections port and [[aMule]] is reading them there.

If both [[aMule]] and their utilities run on the same machine, there's no need to redirect the External Connections port in a [[Firewall]]ed environment (NAT network with a router, etc...). If you had to connect to the External Connections port from somewhere out of the network, it would be necessary to configure the router/[[Firewall]]/etc properly to accept connections through the External Connection port (this would happen, for example, connecting through [[aMuleCMD]] from somewhere outside the network).

As of [[aMule]] 2.0.0-rc8, External Connections reached [[ECv2|version 2.0]] (*cough*). This version is a complete rewrite of the protocol and is '''NOT''' backwards compatible, so it is heavily suggested to upgrade to both a server (that is, [[aMule]]) and [[client]] supporting it. Information about [[ECv2|External Connections v2]] can be reached [[ECv2|here]].

'''NOTE:''' You can create the value for the needed ''ECPassword'' like this:

<code>$ echo -n yourpasswordhere | md5sum | cut -d ' ' -f 1</code>

'''NOTE:''' There are alternate ways of communicating with [[aMule]] although External Connections is the only ''bi-directional'' way. Other ways of communication with [[aMule]] would be the [[Signature|Online Signature]] (outgoing direction) and [[ED2KLinks file]] (ingoing direction).

'''NOTE for [[aMule_CVS|CVS]] users:''' It is very important to use a server (i.e. [[aMule]] or aMuled) and a client ([[aMuleWeb]], [[aMuleCMD]]) from the '''same''' [[aMule_CVS|CVS tarball]]. As development goes on, there are binary incompatibilities between versions, and - in the case of [[aMule_CVS|CVS versions]] - they might cause crashes, burn your house, feed your dog, donate all your hardware to [[aMule]] [[aMule_devs|developers]], etc. Before you'd fall into total despair, extreme care is taken by developers that this cannot happen between '''releases'''! If you're using a server and a client from different releases (not [[aMule_CVS|CVS tarballs]], relases!), most likely you will only get a message "Invalid protocol version." And that's all.

AMule Project FAQ - User contributions [en]

External Connections