External Connections - Revision history

Vollstrecker: Corrected last correction

2008-08-03T10:57:25Z

Corrected last correction

Vollstrecker: Corrected Spelling of English in language selection

2008-08-02T09:38:55Z

Corrected Spelling of English in language selection

Vollstrecker: Removed Version Tag

2008-06-29T08:56:27Z

Removed Version Tag

Festor at 14:11, 26 June 2008

2008-06-26T14:11:58Z

Festor at 14:11, 26 June 2008

2008-06-26T14:11:44Z

Vollstrecker: Added Version Tag

2008-01-18T12:06:12Z

Added Version Tag

Vollstrecker: Language Link and Typos

2007-09-02T07:37:18Z

Language Link and Typos

Colin: reorg, grammar & spelling

2006-12-20T01:20:33Z

reorg, grammar & spelling

84.9.233.187 at 17:29, 22 November 2006

2006-11-22T17:29:37Z

216.27.163.181 at 02:45, 13 June 2006

2006-06-13T02:45:51Z

← Older revision		Revision as of 10:57, 3 August 2008
Line 1:		Line 1:
−	<center>'''~~EnglishCorrected Spelling of~~ English ~~in language selection~~''' \| [[External_Connections-de\|Deutsch]]</center>	+	<center>'''English''' \| [[External_Connections-de\|Deutsch]]</center>

	''''External Connections''' (EC) is a bi-directional interface [[aMule]] uses to communicate with external utilities, specifically:		''''External Connections''' (EC) is a bi-directional interface [[aMule]] uses to communicate with external utilities, specifically:

← Older revision		Revision as of 09:38, 2 August 2008
Line 1:		Line 1:
−	<center>'''~~Englisch~~''' \| [[External_Connections-de\|Deutsch]]</center>	+	<center>'''EnglishCorrected Spelling of English in language selection''' \| [[External_Connections-de\|Deutsch]]</center>

	''''External Connections''' (EC) is a bi-directional interface [[aMule]] uses to communicate with external utilities, specifically:		''''External Connections''' (EC) is a bi-directional interface [[aMule]] uses to communicate with external utilities, specifically:

← Older revision		Revision as of 08:56, 29 June 2008
Line 20:		Line 20:

	For more information on the EC protocol, see [[ECv2\|External Connections v2]].		For more information on the EC protocol, see [[ECv2\|External Connections v2]].
−
−	~~== Version ==~~
−	~~Created by "Unknown User" on 21.07.04 at 20:51<br>~~
−	~~Updated by Vollstrecker on 18.01.08 at 13:04~~

@@ Line 13: / Line 13: @@
 The [[Firewall]] article has instructions on how to do this.
-As of December 2006, aMule CVS has experimental code enabling [[Universal Plug and Play]] (uPnP), which enables you to configure the ports on a uPnP-compatible router automatically. This functionality should soon be available in a general release.
+As of December 2006, aMule SVN has experimental code enabling [[Universal Plug and Play]] (uPnP), which enables you to configure the ports on a uPnP-compatible router automatically. This functionality should soon be available in a general release.
 '''NOTE for [[aMule_SVN|SVN]] users:''' It is very important that the aMuleWeb, aMuleCMD, and aMuleGUI you use are built from the same daily CVS tarball as aMule; mixing versions you are liable to experience crashes. For official releases, the developers take extra care that the worst that happens when you mix versions is a message "Invalid protocol version".

@@ Line 15: / Line 15: @@
 As of December 2006, aMule CVS has experimental code enabling [[Universal Plug and Play]] (uPnP), which enables you to configure the ports on a uPnP-compatible router automatically. This functionality should soon be available in a general release.
-'''NOTE for [[aMule_CVS|CVS]] users:''' It is very important that the aMuleWeb, aMuleCMD, and aMuleGUI you use are built from the same daily CVS tarball as aMule; mixing versions you are liable to experience crashes. For official releases, the developers take extra care that the worst that happens when you mix versions is a message "Invalid protocol version".
+'''NOTE for [[aMule_SVN|SVN]] users:''' It is very important that the aMuleWeb, aMuleCMD, and aMuleGUI you use are built from the same daily CVS tarball as aMule; mixing versions you are liable to experience crashes. For official releases, the developers take extra care that the worst that happens when you mix versions is a message "Invalid protocol version".
 '''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).

@@ Line 1: / Line 1: @@
-''''External Connections''' (EC)  is a bi-directional interface [[aMule]] uses to communicate with external utilities, specifically:
+<center>'''Englisch''' | [[External_Connections-de|Deutsch]]</center>
 * [[aMuleWeb]]
@@ Line 13: / Line 15: @@
 As of December 2006, aMule CVS has experimental code enabling [[Universal plug and play]] (uPnP), which enables you to configure the ports on a uPnP-compatible router automatically. This functionality should soon be available in a general release.
-'''NOTE for [[aMule_CVS|CVS]] users:''' It is very important that the aMuleWeb, aMuleCMD, and aMuleGUI you use are built from the same daily CVS tarball as aMule; mixing versions you are liable to experience crashes. For official releases, the developers take extra care that the worst that happens when you mix versions is a message "Invalid protocol version."
+'''NOTE for [[aMule_CVS|CVS]] users:''' It is very important that the aMuleWeb, aMuleCMD, and aMuleGUI you use are built from the same daily CVS tarball as aMule; mixing versions you are liable to experience crashes. For official releases, the developers take extra care that the worst that happens when you mix versions is a message "Invalid protocol version".
 '''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).
 For more information on the EC protocol, see [[ECv2|External Connections v2]].

@@ Line 1: / Line 1: @@
-External Connections is the ''bi-directional'' way [[aMule]] has to communicate with external utilities, specifically:
+''''External Connections''' (EC)  is a bi-directional interface [[aMule]] uses to communicate with external utilities, specifically:
 * [[aMuleWeb]]
@@ Line 5: / Line 5: @@
 * [[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.
+When a user is using one of these programs, it is sending the commands via 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).
+Unless [[aMule]] and the external utilities are used on the same machine, you may need to configure your firewall and/or router to manage the ports properly, ie, open them to incoming traffic.
-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]].
+The [[Firewall]] article has instructions on how to do this.
-'''NOTE:''' You can create the value for the needed ''ECPassword'' like this:
+As of December 2006, aMule CVS has experimental code enabling [[Universal plug and play]] (uPnP), which enables you to configure the ports on a uPnP-compatible router automatically. This functionality should soon be available in a general release.
-−
-<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.
+For more information on the EC protocol, see [[ECv2|External Connections v2]].

← Older revision		Revision as of 17:29, 22 November 2006
Line 1:		Line 1:
−	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 Connections 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 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).		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).

← Older revision		Revision as of 02:45, 13 June 2006
Line 6:		Line 6:

	'''NOTE:''' You can create the value for the needed ''ECPassword'' like this:		'''NOTE:''' You can create the value for the needed ''ECPassword'' like this:
−	$ echo -n yourpasswordhere \| md5sum \| cut -d ' ' -f 1	+
		+	<code>$ echo -n yourpasswordhere \| md5sum \| cut -d ' ' -f 1</code>