Difference between revisions of "External Connections"

From AMule Project FAQ
Jump to: navigation, search
 
(Good job. See if you agree with this modifications and PLEASE, register ;))
Line 1: Line 1:
''Note: Since there's no info at all about this, I'll write what I think External Connections are. I'm no expert so I may be wrong, so take the following with a grain of salt. If some experts thinks this info is right, then please remove this comment (and if it's not, please correct it and remove the comment anyway! ;-) ).''
+
External connections are the 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).
  
External connections are the way aMule has to communicate with external utilities, like the webserver. So, when an user is controlling aMule remotely with a web browser, he's not talking directly with aMule, but with another program (amuleweb in this case) that is who really listens at port 4711. This program then talks with aMule using the external connections mechanism.
+
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 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).
 
+
Since usually 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.).
+

Revision as of 22:42, 21 July 2004

External connections are the 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 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).