Difference between revisions of "External Connections"
| Line 3: | Line 3: | ||
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). | 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]]. This version is a complete rewrite of the protocol and is '''NOT''' backwards compatible, so it is heavily suggested to | + | As of [[aMule]] 2.0.0-rc8, External Connections reached [[ECv2|version 2.0]]. 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:''' There are alternate ways of communicating with [[aMule]] although External Connections is the only ''bi-directional'' way. | + | '''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). |
| − | Other ways would be the [[Signature|Online Signature]] (outgoing direction) and [[ED2KLinks file]] (ingoing direction). | + | |
Revision as of 13:16, 9 December 2004
External Connections is the bi-directional way aMule has to communicate with external utilities, like the aMuleWeb and aMuleCMD. So, when a user is controlling aMule remotely, it is sending the commands through the External Conections port and aMule is reading them there (when controlling through a web browser, what is really happening is that aMuleWeb is getting the actions, interpreting them and sending the commands to the External Connection ports).
If both aMule and their utilities run on the same machine, there's no need to redirect the External Connections port in a Firewalled 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 version 2.0. 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 External Connections v2 can be reached here.
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 Online Signature (outgoing direction) and ED2KLinks file (ingoing direction).
