AMule Project FAQ - User contributions [en]

AMuleWeb PHP

2006-10-16T16:46:12Z

199.203.130.250:

== aMuleWeb PHP manual ==
By Froenchenko Leonid lfroen@gmail.com [[User:Lfroen|Lfroen]]

== Introduction ==

[[aMuleWeb]] is an add-on program, used together with [[aMule]] and serves as webserver, allowing user to control aMule through browser interface. aMuleWeb works very similar to regular and wide-known webservers such as Apache[http://www.apache.org] - set of HTML pages stored on server side (called "template"). Those pages contains embedded server-side script, which is running when user requests the page. Resulting page is returned to user.

The scripting language, [[aMuleWeb]] using is very similar to widely known "PHP", developed and distributed by Zend company [http://www.zend.com]. Since aMuleWeb implementation is differ from original PHP, I will call it "aMuleWeb PHP" for reader convenience. "The PHP" language, will be referred as "real PHP" or just "PHP" to make difference between the two.

== Conventions ==
Language elements, reserved words are marked bold: '''keyword'''.

== Core language constructs ==
aMuleWeb PHP have same basic language elements as real PHP version 5. Several things supported or implemented differently:
OO constructs (classes) may pass syntax check, but they are not supported in any way.
'''include''' construct is parse-time directive (in contrary to PHP, where you can do it in run-time and check result of "include" operation)
There's no '''list''' at all.

=== Variables ===
There's scalar (referred as $var) and array (referred as @var) variables. Similarly to real PHP all variables are local, unless defined otherwise.
Variables, marked as '''global''' must be declated ''before'' this definition. Example:

$a = 1;

function foo()
{
global $a;
}

References to variable and to array members are fully supported:
$a = &$b;
$c = &$c[5];

*Notes:
**Reference of variable by name like $$var is not supported.
**Integer variables are 64-bit unsigned integers
**Variable substitution inside of "" is not supported.

==== Predefined global variables ====
Similarly to real PHP, there's set of special, or predefined variables, which have special meaning. Those variables may indicate input received from user, or they may control script execution.

=== Operators ===
All PHP operators supported. Implicit type conversion is supported too, as common in scripting languages. This way 1 + "2" = 3.
Arrays are converted to integer in "Perl style" i.e. in case array variable is used in integer context, number of members is taken as value.
*Prefix and postfix ++ and -- are not distinguished (prefix form used)

=== Subroutines ===
'''function''' construct is fully supported. In contrary to regular PHP function must be defined prior calling. It is error to do otherwise. Functions can be recursive, thou.
Real PHP allows to omit parameters for function calls (default parameters). aMuleWeb PHP does not support this conventions, which mean that all parameters must be present when function is called. This is not an error, and parameters will receive predefined values when omit: 0 for numbers, "" (empty string) for strings.
Parameters can be references or arrays with usual meaning.
*Function can return value but not reference.

== Library ==
PHP language is known to have huge library of useful subroutines. Those subroutines are used to perform various tasks, varying from simple string manipulation to complex databases and OS binding. aMuleWeb PHP on the other hand, have very limited library.
There's several reasons behind this fact. First of all, it is out of question to completely re-create PHP library, given it's size and complexity. Second, and most important, it's not really needed. aMuleWeb PHP is built to serve very specific application, and used to create very specific kind of pages. It will not be used to create e-commerce site or webmail. List below summarize supported functions:

*var_dump($var): [http://www.zend.com/manual/function.var-dump.php]
*strlen($string):[http://www.zend.com/manual/function.strlen.php]
*usort($var): [http://www.zend.com/manual/function.usort.php]

== aMule binding ==
The whole purpose of [[aMuleWeb]] control [[aMule]]. Script provide convinient way to access underlying aMule datastructure for both queries and actions.

== Authentication ==
Real PHP have wide range of authentication and session management possibilities. In aMuleWeb PHP, status is different. Both authentication and session management are not part of scripting language. Instead, they are implemented as part of in webserver itself, and running invisibly for script engine.

AMuleWeb PHP

2006-10-16T16:45:34Z

199.203.130.250:

== aMuleWeb PHP manual ==
By Froenchenko Leonid lfroen@gmail.com [[User:Lfroen|Lfroen]]

== Introduction ==

[[aMuleWeb]] is an add-on program, used together with [[aMule]] and serves as webserver, allowing user to control aMule through browser interface. aMuleWeb works very similar to regular and wide-known webservers such as Apache[http://www.apache.org] - set of HTML pages stored on server side (called "template"). Those pages contains embedded server-side script, which is running when user requests the page. Resulting page is returned to user.

The scripting language, [[aMuleWeb]] using is very similar to widely known "PHP", developed and distributed by Zend company [http://www.zend.com]. Since aMuleWeb implementation is differ from original PHP, I will call it "aMuleWeb PHP" for reader convenience. "The PHP" language, will be referred as "real PHP" or just "PHP" to make difference between the two.

== Conventions ==
Language elements, reserved words are marked bold: '''keyword'''.

== Core language constructs ==
aMuleWeb PHP have same basic language elements as real PHP version 5. Several things supported or implemented differently:
OO constructs (classes) may pass syntax check, but they are not supported in any way.
'''include''' construct is parse-time directive (in contrary to PHP, where you can do it in run-time and check result of "include" operation)
There's no '''list''' at all.

=== Variables ===
There's scalar (referred as $var) and array (referred as @var) variables. Similarly to real PHP all variables are local, unless defined otherwise.
Variables, marked as '''global''' must be declated ''before'' this definition. Example:

$a = 1;

function foo()
{
global $a;
}

References to variable and to array members are fully supported:
$a = &$b;
$c = &$c[5];

*Notes:
**Reference of variable by name like $$var is not supported.
**Integer variables are 64-bit unsigned integers
**Variable substitution inside of "" is not supported.

==== Predefined global variables ====
Similarly to real PHP, there's set of special, or predefined variables, which have special meaning. Those variables may indicate input received from user, or they may control script execution.

=== Operators ===
All PHP operators supported. Implicit type conversion is supported too, as common in scripting languages. This way 1 + "2" = 3.
Arrays are converted to integer in "Perl style" i.e. in case array variable is used in integer context, number of members is taken as value.
*Prefix and postfix ++ and -- are not distinguished (prefix form used)

=== Subroutines ===
'''function''' construct is fully supported. In contrary to regular PHP function must be defined prior calling. It is error to do otherwise. Functions can be recursive, thou.
Real PHP allows to omit parameters for function calls (default parameters). aMuleWeb PHP does not support this conventions, which mean that all parameters must be present when function is called. This is not an error, and parameters will receive predefined values when omit: 0 for numbers, "" (empty string) for strings.
Parameters can be references or arrays with usual meaning.
*Function can return value but not reference.

=== Library ===
PHP language is known to have huge library of useful subroutines. Those subroutines are used to perform various tasks, varying from simple string manipulation to complex databases and OS binding. aMuleWeb PHP on the other hand, have very limited library.
There's several reasons behind this fact. First of all, it is out of question to completely re-create PHP library, given it's size and complexity. Second, and most important, it's not really needed. aMuleWeb PHP is built to serve very specific application, and used to create very specific kind of pages. It will not be used to create e-commerce site or webmail. List below summarize supported functions:

*var_dump($var): [http://www.zend.com/manual/function.var-dump.php]
*strlen($string):[http://www.zend.com/manual/function.strlen.php]
*usort($var): [http://www.zend.com/manual/function.usort.php]

=== aMule binding ===
The whole purpose of [[aMuleWeb]] control [[aMule]]. Script provide convinient way to access underlying aMule datastructure for both queries and actions.

=== Authentication ===
Real PHP have wide range of authentication and session management possibilities. In aMuleWeb PHP, status is different. Both authentication and session management are not part of scripting language. Instead, they are implemented as part of in webserver itself, and running invisibly for script engine.

AMuleWeb PHP

2006-10-16T16:44:32Z

199.203.130.250:

== aMuleWeb PHP manual ==
By Froenchenko Leonid lfroen@gmail.com [[User:Lfroen|Lfroen]]

== Introduction ==

[[aMuleWeb]] is an add-on program, used together with [[aMule]] and serves as webserver, allowing user to control aMule through browser interface. aMuleWeb works very similar to regular and wide-known webservers such as Apache[http://www.apache.org] - set of HTML pages stored on server side (called "template"). Those pages contains embedded server-side script, which is running when user requests the page. Resulting page is returned to user.

The scripting language, [[aMuleWeb]] using is very similar to widely known "PHP", developed and distributed by Zend company [http://www.zend.com]. Since aMuleWeb implementation is differ from original PHP, I will call it "aMuleWeb PHP" for reader convenience. "The PHP" language, will be referred as "real PHP" or just "PHP" to make difference between the two.

== Conventions ==
Language elements, reserved words are marked bold: '''keyword'''.

== Core language constructs ==
aMuleWeb PHP have same basic language elements as real PHP version 5. Several things supported or implemented differently:
OO constructs (classes) may pass syntax check, but they are not supported in any way.
'''include''' construct is parse-time directive (in contrary to PHP, where you can do it in run-time and check result of "include" operation)
There's no '''list''' at all.

==== Variables ===
There's scalar (referred as $var) and array (referred as @var) variables. Similarly to real PHP all variables are local, unless defined otherwise.
Variables, marked as '''global''' must be declated ''before'' this definition. Example:

$a = 1;

function foo()
{
global $a;
}

References to variable and to array members are fully supported:
$a = &$b;
$c = &$c[5];

*Notes:
**Reference of variable by name like $$var is not supported.
**Integer variables are 64-bit unsigned integers
**Variable substitution inside of "" is not supported.

==== Predefined global variables ====
Similarly to real PHP, there's set of special, or predefined variables, which have special meaning. Those variables may indicate input received from user, or they may control script execution.

=== Operators ===
All PHP operators supported. Implicit type conversion is supported too, as common in scripting languages. This way 1 + "2" = 3.
Arrays are converted to integer in "Perl style" i.e. in case array variable is used in integer context, number of members is taken as value.
*Prefix and postfix ++ and -- are not distinguished (prefix form used)

=== Subroutines ===
'''function''' construct is fully supported. In contrary to regular PHP function must be defined prior calling. It is error to do otherwise. Functions can be recursive, thou.
Real PHP allows to omit parameters for function calls (default parameters). aMuleWeb PHP does not support this conventions, which mean that all parameters must be present when function is called. This is not an error, and parameters will receive predefined values when omit: 0 for numbers, "" (empty string) for strings.
Parameters can be references or arrays with usual meaning.
*Function can return value but not reference.

=== Library ===
PHP language is known to have huge library of useful subroutines. Those subroutines are used to perform various tasks, varying from simple string manipulation to complex databases and OS binding. aMuleWeb PHP on the other hand, have very limited library.
There's several reasons behind this fact. First of all, it is out of question to completely re-create PHP library, given it's size and complexity. Second, and most important, it's not really needed. aMuleWeb PHP is built to serve very specific application, and used to create very specific kind of pages. It will not be used to create e-commerce site or webmail. List below summarize supported functions:

*var_dump($var): [http://www.zend.com/manual/function.var-dump.php]
*strlen($string):[http://www.zend.com/manual/function.strlen.php]
*usort($var): [http://www.zend.com/manual/function.usort.php]

=== aMule binding ===
The whole purpose of [[aMuleWeb]] control [[aMule]]. Script provide convinient way to access underlying aMule datastructure for both queries and actions.

=== Authentication ===
Real PHP have wide range of authentication and session management possibilities. In aMuleWeb PHP, status is different. Both authentication and session management are not part of scripting language. Instead, they are implemented as part of in webserver itself, and running invisibly for script engine.

AMuleWeb PHP

2006-10-16T15:00:15Z

199.203.130.250:

= aMuleWeb PHP manual =
By Froenchenko Leonid lfroen@gmail.com [[User:Lfroen|Lfroen]]

=== Introduction ===

[[aMuleWeb]] is an add-on program, used together with [[aMule]] and serves as webserver, allowing user to control aMule through browser interface. aMuleWeb works very similar to regular and wide-known webservers such as Apache[http://www.apache.org] - set of HTML pages stored on server side (called "template"). Those pages contains embedded server-side script, which is running when user requests the page. Resulting page is returned to user.

The scripting language, [[aMuleWeb]] using is very similar to widely known "PHP", developed and distributed by Zend company [http://www.zend.com]. Since aMuleWeb implementation is differ from original PHP, I will call it "aMuleWeb PHP" for reader convenience. "The PHP" language, will be referred as "real PHP" or just "PHP" to make difference between the two.

=== Conventions ===
Language elements, reserved words are marked bold: '''keyword'''.

=== Core language constructs ===
aMuleWeb PHP have same basic language elements as real PHP version 5. Several things supported or implemented differently:
OO constructs (classes) may pass syntax check, but they are not supported in any way.
'''include''' construct is parse-time directive (in contrary to PHP, where you can do it in run-time and check result of "include" operation)
There's no '''list''' at all.

==== Variables ====
There's scalar (referred as $var) and array (referred as @var) variables. Similarly to real PHP all variables are local, unless defined otherwise.
Variables, marked as '''global''' must be declated ''before'' this definition. Example:

$a = 1;

function foo()
{
global $a;
}

References to variable and to array members are fully supported:
$a = &$b;
$c = &$c[5];

*Notes:
**Reference of variable by name like $$var is not supported.
**Integer variables are 64-bit unsigned integers
**Variable substitution inside of "" is not supported.

==== Predefined global variables ====
Similarly to real PHP, there's set of special, or predefined variables, which have special meaning. Those variables may indicate input received from user, or they may control script execution.

==== Operators ====
All PHP operators supported. Implicit type conversion is supported too, as common in scripting languages. This way 1 + "2" = 3.
Arrays are converted to integer in "Perl style" i.e. in case array variable is used in integer context, number of members is taken as value.
*Prefix and postfix ++ and -- are not distinguished (prefix form used)

==== Subroutines ====
'''function''' construct is fully supported. In contrary to regular PHP function must be defined prior calling. It is error to do otherwise. Functions can be recursive, thou.
Real PHP allows to omit parameters for function calls (default parameters). aMuleWeb PHP does not support this conventions, which mean that all parameters must be present when function is called. This is not an error, and parameters will receive predefined values when omit: 0 for numbers, "" (empty string) for strings.
Parameters can be references or arrays with usual meaning.
*Function can return value but not reference.

=== Library ===
PHP language is known to have huge library of useful subroutines. Those subroutines are used to perform various tasks, varying from simple string manipulation to complex databases and OS binding. aMuleWeb PHP on the other hand, have very limited library.
There's several reasons behind this fact. First of all, it is out of question to completely re-create PHP library, given it's size and complexity. Second, and most important, it's not really needed. aMuleWeb PHP is built to serve very specific application, and used to create very specific kind of pages. It will not be used to create e-commerce site or webmail. List below summarize supported functions:

*var_dump($var): [http://www.zend.com/manual/function.var-dump.php]
*strlen($string):[http://www.zend.com/manual/function.strlen.php]
*usort($var): [http://www.zend.com/manual/function.usort.php]

=== aMule binding ===
The whole purpose of [[aMuleWeb]] control [[aMule]]. Script provide convinient way to access underlying aMule datastructure for both queries and actions.

=== Authentication ===
Real PHP have wide range of authentication and session management possibilities. In aMuleWeb PHP, status is different. Both authentication and session management are not part of scripting language. Instead, they are implemented as part of in webserver itself, and running invisibly for script engine.

AMuleWeb

2006-10-16T07:23:45Z

199.203.130.250:

== Description ==

aMuleWeb is a utility that listens for [http://www.w3.org/MarkUp HTTP] connections at port 4711 (by default, although it can be changed through '''Preferences''') and allows remote users to control [[aMule]] using just a web browser.

[[aMule]] itself doesn't support listening to [http://www.w3.org/MarkUp HTTP] connections, so the external utility aMuleWeb is used. This utility listens for remote connections, and once the link between aMuleWeb and the remote user is established, it connects to the [[aMule]] main program using the [[External Connections]] mechanism.

== Compiling aMuleWeb ==

[[Compile]] [[aMule]] normally, just add ''--enable-amuleweb'' when running ''configure''.

== Setting up aMuleWeb with [[aMule]] ==

=== aMuleWeb with [[aMule]] 2.0.0 or later ===

*For users running the monotlithic [[aMule]] application:
**Go to "Preferences"->"Remote Controls" (in [[aMule]]) and...
***Enable "Accept External Connections".
***Enable "Use TCP ports instead of unix local sockets" (This option doesn't exist since version 2.1.0)
***Enter a password for [[External Connections]]. If you don't do this, aMuleWeb will not communicate with [[aMule]].
::'''NOTE:''' When you change your aMuleWeb and [[External Connections]] ports here, make sure to restart [[aMule]].

*For users running the [[aMule|aMule daemon]]:
**Shutdown [[aMule|aMuled]] if it is still running.
**Run ''amuleweb -w'' to generate ''~/.aMule/remote.conf'' and edit it for these options. It previously were on ''~/.aMule/amule.conf'', but the lines are still on this file, so edit both if in doubt.
***''[ExternalConnect]'' <- Section header
***''AcceptExternalConnections=1'' <-- To enable [[aMule]] listening for [[External Connections]].
***''ECUseTCPPort=1'' <-- To use the [http://www.faqs.org/faqs/internet/tcp-ip/resource-list TCP] port. Very important since [http://www.unix.org Unix] sockets are disabled.
***''ECPassword=ca3c365274907c6fd527068788e14639'' <-- To find the MD5 string for your password, do:
:::''$ echo -n yourpasswordhere | md5sum | cut -d ' ' -f 1''
:::''ca3c365274907c6fd527068788e14639''
**If you get ''FATAL ERROR: Cannot find template: default'' it's because you didn't run ''make install''. If you don't want to install aMule, copy the ''src/webserver/default/'' directory into ''~/.aMule/webserver/'' (create it if needed). If you want any other template (probably ''php-default''), copy it too. Then go back to the previous step.
**Restart [[aMule|aMule]]

'''NOTE:''' Every password must be md5sum,also webserver one/s. aMule embedded webserver works without remote.conf,you just need to edit ''amule.conf''. A good trick if you have somewhere an X server is to configure amule using the GUI and then copy the ''amule.conf'' configuration file where you want to run the daemon.

Thanks to [[User:Stefanero|Stefanero]], from who I shamelessly stole a lot from his tutorial.

'''NOTE:''' aMuleWeb uses cookies to hold session id. Make sure that cookies are enabled in your browser.

=== aMuleWeb with [[aMule]] pre-2.0.0 final ===

Please check [[Webserver-old|this page]] for archived instructions (educational purposes!).

== Connecting to aMuleWeb ==

To run aMuleWeb run '''''amuleweb''''' on a terminal.

Once aMuleWeb is running, open a web browser and connect to:

''http://host:port''

where ''host'' stands for your host's name (try with ''localhost'') and port stands for the aMuleWeb port ('''NOT''' the [[External Connections]] port).

For example: ''http://localhost:4711''

''Shakraw''

== Standard ports ==

The ports can be set to anything, but this are the most used (the standard ones):

*[[External Connections]]: 4712
*amuleweb: 4711

Make sure you do not confuse with what each of them is.

== Template (skin) location ==

aMuleWeb looks for its files in a number of places:
*In your home directory: ''$HOME/.aMule/webserver/''[skin name]''/''
*And at it's install location, in this order (by default, ''/usr/local/share/amule/webserver'' if you compiled [[aMule]], or ''/usr/share/amule/webserver'' if you installed it from a package).

Default template name is 'default'.

If, '''after installing''' [[aMule]], aMuleWeb refuses to run because of not being able to load template:
*Please report this situation to us, and then
*Create the directories ''webserver/default'' in the ''.aMule'' subdirectory of your home directory, and copy the contents of the ''src/webserver'' directory there from the [[aMule]] tarball (I mean to ''$HOME/.aMule/webserver/default'').

'''[[User:GonoszTopi|GonoszTopi]]'''

== How to start [[aMuled|aMule Daemon]] and aMuleWeb with your computer ==

The best way to start both the processes aMule Daemon and aMuleWeb with your server is to add a shell script ''/etc/init.d/amule'' like this:

PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
DAEMON=/usr/bin/amuled
WEB=/usr/bin/amuleweb
NAME=amuled
DESC=amuled
RUNAMULE=no
USER=youramuleuser

test -x $DAEMON || exit 0

# Include amule defaults if available
if [ -f /etc/default/amule ] ; then
. /etc/default/amule
fi

if [ "$RUNAMULE" != "yes" ];then
echo "Amule not to be started. Edit /etc/default/amule first."
exit 1
fi

set -e

case "$1" in
start)
echo -n "Starting $DESC: "
su $USER -c "$DAEMON -f"
sleep 20
su $USER -c "$WEB --quiet &"
echo "$NAME."
;;
stop)
echo -n "Stopping $DESC: "
killall --quiet --ignore-case $WEB
killall --quiet --ignore-case $DAEMON
echo "$NAME."
;;
restart|force-reload)
echo -n "Restarting $DESC: "
killall --quiet --ignore-case $WEB
killall --quiet --ignore-case $DAEMON
sleep 1
su $USER -c "$DAEMON -f"
sleep 20
su $USER -c "$WEB --quiet &"
echo "$NAME."
;;
*)
N=/etc/init.d/$NAME
echo "Usage: $N {start|stop|restart|force-reload}" >&2
exit 1
;;
esac

exit 0

Then just set that script to be run at start up. On [[Debian]] this would be doen with the following command:

update-rc.d amule defaults

Then, for the deamons to start you just have to create a file ''/etc/default/amule'' which contains a single line:

RUNAMULE=yes

That's it!

== Where to report problems and questions? ==

For Problems or Questions just report on http://forum.amule.org forum or join [[IRC]] channel [irc://irc.freenode.net/amule #amule] at [irc://irc.freenode.net irc.freenode.net]

== Other sources of information ==

Read the aMuleWeb man page, which is available in English, French, German, Hungarian and Spanish.

For further information read the [[FAQ_webserver|aMuleWeb FAQ]].

AMuleWeb

2006-01-02T06:41:49Z

199.203.130.250:

== Description ==

aMuleWeb is a utility that listens for [http://www.w3.org/MarkUp HTTP] connections at port 4711 (by default, although it can be changed through '''Preferences''') and allows remote users to control [[aMule]] using just a web browser.

[[aMule]] itself doesn't support listening to [http://www.w3.org/MarkUp HTTP] connections, so the external utility aMuleWeb is used. This utility listens for remote connections, and once the link between aMuleWeb and the remote user is established, it connects to the [[aMule]] main program using the [[External Connections]] mechanism.

== Compiling aMuleWeb ==

[[Compile]] [[aMule]] normally, just add ''--enable-amuleweb'' when running ''configure''.

== Setting up aMuleWeb with [[aMule]] ==

=== aMuleWeb with [[aMule]] 2.0.0 or later ===

*For users running the monotlithic [[aMule]] application:
**Go to "Preferences"->"Remote Controls" (in [[aMule]]) and...
***Enable "Accept External Connections".
***Enable "Use TCP ports instead of unix local sockets" (This option doesn't exist since version 2.1.0)
***Enter a password for [[External Connections]]. If you don't do this, aMuleWeb will not communicate with [[aMule]].
::'''NOTE:''' When you change your aMuleWeb and [[External Connections]] ports here, make sure to restart [[aMule]].

*For users running the [[aMule|aMule daemon]]:
**Shutdown [[aMule|aMuled]] if it is still running.
**Run ''amuleweb -w'' to generate ''~/.aMule/remote.conf'' and edit it for these options. It previously were on ''~/.aMule/amule.conf'', but the lines are still on this file, so edit both if in doubt.
***''[ExternalConnect]'' <- Section header
***''AcceptExternalConnections=1'' <-- To enable [[aMule]] listening for [[External Connections]].
***''ECUseTCPPort=1'' <-- To use the [http://www.faqs.org/faqs/internet/tcp-ip/resource-list TCP] port. Very important since [http://www.unix.org Unix] sockets are disabled.
***''ECPassword=ca3c365274907c6fd527068788e14639'' <-- To find the MD5 string for your password, do:
:::''$ echo -n yourpasswordhere | md5sum | cut -d ' ' -f 1''
:::''ca3c365274907c6fd527068788e14639''
**If you get ''FATAL ERROR: Cannot find template: default'' it's because you didn't run ''make install''. If you don't want to install aMule, copy the ''src/webserver/default/'' directory into ''~/.aMule/webserver/'' (create it if needed). If you want any other template (probably ''php-default''), copy it too. Then go back to the previous step.
**Restart [[aMule|aMuled]]

'''NOTE:''' In [[aMule]] version 2.0.0 and later you don't need to do any copy/link of [[aMuleWeb|webserver]] files.

'''NOTE2:''' Every password must be md5sum,also webserver one/s. aMule embedded webserver works without remote.conf,you just need to edit ''amule.conf''. A good trick if you have somewhere an X server is to configure amule using the GUI and then copy the ''amule.conf'' configuration file where you want to run the daemon.

Thanks to [[User:Stefanero|Stefanero]], from who I shamelessly stole a lot from his tutorial.

'''NOTE3:''' aMuleWeb uses cookies to hold session id. Make sure that cookies are enabled in your browser.

=== aMuleWeb with [[aMule]] pre-2.0.0 final ===

Please check [[Webserver-old|this page]] for archived instructions (educational purposes!).

== Connecting to aMuleWeb ==

To run aMuleWeb run '''''amuleweb''''' on a terminal.

Once aMuleWeb is running, open a web browser and connect to:

''http://host:port''

where ''host'' stands for your host's name (try with ''localhost'') and port stands for the aMuleWeb port ('''NOT''' the [[External Connections]] port).

For example: ''http://localhost:4711''

''Shakraw''

== Standard ports ==

The ports can be set to anything, but this are the most used (the standard ones):

*[[External Connections]]: 4712
*amuleweb: 4711

Make sure you do not confuse with what each of them is.

== Skin support ==

aMuleWeb now looks for its files in a number of places:
*In your home directory: ''$HOME/.aMule/webserver/''[skin name]''/''
*And at it's install location, in this order (by default, ''/usr/local/share/amule/webserver'' if you compiled [[aMule]], or ''/usr/share/amule/webserver'' if you installed it from a package).

Default skin (template) name is 'default'.

If, '''after installing''' [[aMule]], aMuleWeb refuses to run because of not being able to load template:
*Please report this situation to us, and then
*Create the directories ''webserver/default'' in the ''.aMule'' subdirectory of your home directory, and copy the contents of the ''src/webserver'' directory there from the [[aMule]] tarball (I mean to ''$HOME/.aMule/webserver/default'').

'''[[User:GonoszTopi|GonoszTopi]]'''

== How to start [[aMule Daemon|aMuled]] and aMuleWeb with your computer ==

The best way to start both the processes aMule Daemon and aMuleWeb with your server is to add a shell script ''/etc/init.d/amule'' like this:

PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
DAEMON=/usr/bin/amuled
WEB=/usr/bin/amuleweb
NAME=amuled
DESC=amuled
RUNAMULE=no

test -x $DAEMON || exit 0

# Include amule defaults if available
if [ -f /etc/default/amule ] ; then
. /etc/default/amule
fi

if [ "$RUNAMULE" != "yes" ];then
echo "Amule not to be started. Edit /etc/default/amule first."
exit 1
fi

set -e

case "$1" in
start)
echo -n "Starting $DESC: "
su youramuleuser -c "$DAEMON -f"
su youramuleuser -c "$WEB --quiet &"
echo "$NAME."
;;
stop)
echo -n "Stopping $DESC: "
killall --quiet --ignore-case $WEB
killall --quiet --ignore-case $DAEMON
echo "$NAME."
;;
restart|force-reload)
echo -n "Restarting $DESC: "
killall --quiet --ignore-case $WEB
killall --quiet --ignore-case $DAEMON
sleep 1
su youramuleuser -c "$DAEMON -f"
su youramuleuser -c "$WEB --quiet &"
echo "$NAME."
;;
*)
N=/etc/init.d/$NAME
echo "Usage: $N {start|stop|restart|force-reload}" >&2
exit 1
;;
esac

exit 0

Then just set that script to be run at start up. On [[Debian]] this would be doen with the following command:

ln -s /etc/init.d/amule /etc/rc2.d/S61amule

Then, for the deamons to start you just have to create a file ''/etc/default/amule'' which contains a single line:

RUNAMULE=yes

That's it!

== Where to report problems and questions? ==

For Problems or Questions just report on http://forum.amule.org forum or join [[IRC]] channel [irc://irc.freenode.net/amule #amule] at [irc://irc.freenode.net irc.freenode.net]

== Other sources of information ==

Read the aMuleWeb man page, which is available in English, French, German, Hungarian and Spanish.

For further information read the [[FAQ_webserver|aMuleWeb FAQ]].

FAQ network

2005-03-01T15:13:14Z

199.203.130.250:

= Network speed: what you should know before asking questions =
by Froenchenko Leonid, lfroen@gmail.com

== Preface ==
The purpose of this document is to clarify different issues regarding network
speed that pops up from time to time in amule forum. Generally speaking, there're several reasons for questions about "amule network":

* Speed reported by amule doesn't match provider given rate
* Poor performance of amule itself or another network application on the same computer
* What are key factors influencing network performance while amule is running

Intended audience for this document are users who want to get better understanding of network functionality in general and in practical implication to amule functionality.

This page, however, is not to be seen as comprehensive general purpose "Network
FAQ".

== Network speed - how much is it? ==
While talking about network speed, people are using "bps" units, which mean
"bits per second". The reason for ''bit'' rather that ''byte'' is pretty
much historical, but also have engineering motivation behind.

This motivation comes from the fact, that not all networks in the world are transferring bytes.

There's also convention to use capital "B" in "Bps" when speed is marked
in "bytes per second". However, this convention is not widely accepted. Particularly, organizations like IETF and IEEE are stick to original "bps".

== Prefixes ==
Since their invention, networks made quite a progress, and now we have networks
that transfers thousands and millions bits and more bits per second. For marking those speeds, prefixes ''"kilo"'', ''"mega"'', ''"giga"'', ''"tera"'' etc. are used.

It is a common mistake to think that values with those prefixes are the same as in computer science, i.e. powers of 2. The truth is that, for historical reasons, prefixes in networking have a decimal base, and not a binary one.

<table cellpadding="2" cellspacing="2" border="1" width="100%"
title="Table 1">
<tr>
<th valign="middle" title="Table 1" align="center"
bgcolor="#33ff33">Prefix</th>
<th valign="middle" align="center" bgcolor="#33ff33">meaning in computers</th>
<th valign="middle" title="Table 1" align="center"
bgcolor="#33ff33">meaning in networks</th>
<th valign="middle" align="center" bgcolor="#33ff33">difference, %%</th>
</tr>
<tr>
<td valign="top">K (kilo)</td>
<td valign="top">2^10 = 1024</td>
<td valign="top">10^3 = 1000</td>
<td valign="top">2%</td>
</tr>
<tr>
<td valign="top">M (mega)</td>
<td valign="top">2^20 = 1,048,576</td>
<td valign="top">10^6 = 1,000,000</td>
<td valign="top">5%</td>
</tr>
<tr>
<td valign="top">G (giga)</td>
<td valign="top">2^30 = 1,073,741,624</td>
<td valign="top">10^9 = 1,000,000,000</td>
<td valign="top">7%</td>
</tr>
<tr>
<td valign="top">T (tera)</td>
<td valign="top">2^40 = 1,099,511,627,776</td>
<td valign="top">10^12 = 1,000,000,000,000</td>
<td valign="top">9%</td>
</tr>
</table>

As you can see from the table above the error in calculation is about 5% when the prefix is incorrectly interpreted. Please note that the speed your provider tells you is "speed in network", i.e. calculated on decimal base.

For example when your provider tells you that your link is "ADSL 256/128" you
should understand that he means 256000/128000 bps. Which means, that the speed of your connection is 32000/16000 bps.

== Protocol overhead - what is it about ==
When amule is running, it constantly "talks" with other clients and servers.
This data exchange is needed to identify itself, request information about
available sources and files, perform searches and so on.

Since this information has no use for the user itself, it's called "overhead" i.e. inevitable addition to the data you actually want to upload or download.

aMule calls this "''connection overhead''". However, the number amule presents, includes only the size of the actual data that amule itself is sending to the network stack. Later, this data is sent down to the net with more overhead - now of network protocols. How much is it - lets see that in the next section.

== Network overhead ==
First of all - we're talking about IPv4 network. Once upon a time, there
was only one type of IP network. Now there are two - IP version 4, the old
we all know; and IP version 6 - the new protocol made to fix the limitations of IPv4.

ED2K protocol by design, is unable to talk over IPv6 network, so users who have it (in Japan and China for example) will not be able to connect "as is". Using IPv4 means, that each packet (TCP, UDP, ICMP) will have IPv4 header.

The minimum size of this header is 20 bytes. Header can have optional parts (each 4 bytes) and it's up to your provider - for example my adds 1 option dword. <-- WTF?

When talking to other thing on ed2k network, amule uses the widely known TCP protocol. UDP is also used, but on a much smaller scale. As the reader might know, TCP is a reliable protocol, i.e. it's guaranteed that data which sent from one side will arrive on the other or an error will be reported.

In order to achieve this, TCP send its own data in addition to the actual transfer. This data includes TCP client initial negotiation, checksums, sequence numbers and acknowledgments. All this is in the ''TCP header'' which is added to each packet sent. The size of this header is 20 bytes minimum.

While being small overhead for large bulk transfer, it can take significant part of bandwidth when small amounts of data are being exchanged. This is exactly what happens on source discovery part of amule.

Our client is trying to establish a connection and negotiate with a large number of other clients. Doing this, amule opens new TCP connections ''all the time''. The amount of those connections is controlled by the ''"Maximum number of connections in 5 seconds"'' setting in the preferences.

A typical number is about 100. Each TCP connection results in at least 3 packets traveling the net - one is a SYN packet, i.e. connection request, and one an ACK or a RST when the connection is accepted or refused, and SYN+ACK to establish the session.

There's more overhead of DNS queries when an address is resolved, retries when a host doesn't reply and so on.

=== On low level ===
After passing TCP and IP layers packets go down to the network interface
driver. The kind of this driver depends on the way your computer is connected to the internet. For simplicity sake we will assume that this computer is connected to the ISP directly, i.e. you have no LAN (or switch or router) between.

Common setups that I'm aware of:

* Analog modem, connected to telephone line (ISDN modem falls in this category too)
* Cable modem, connected through ethernet, ISP gives you an IP address through DHCP
* Cable modem, connected through ethernet, ISP requires you to configure PPPoE or PPTP tunnel
* ADSL modem, connected through ethernet. You must have a PPPoE or PPTP tunnel
* Variation of above - modem connected to PC by USB.

In each of above setups there are different protocols in use, and different headers added to transmitted packets. But there's one important thing to note: ''ethernet frames traveling between cable/ADSL modem and PC, and don't reach the ISP''.

And consequently they are not counted in rate calculations. PPPoE and
PPTP headers, on the contrary ''do reach the ISP''. Whether or not
your particular provider includes them in rate calculations I obviously have
no idea about. For this reason I will exclude those headers from my calculations.

If you think that your ISP includes it, add 4 bytes to the size of each packet.

=== Example ===
Let's see how much network overhead we have on a typical network. Our connection is a cable modem connected via an ethernet link to a PC directly (no router between them).

In this setup we have IPv4 packets sent over ethernet.

Lets say we have 10 new connections opened each second, and all are being accepted (successfully established TCP session). This alone sums up to (I'm counting data going up - from my computer to the net):

''10 connection * 2 packets * (20 bytes of TCP + 20 bytes of IPv4) = 800 bytes of overhead.''

This means that we are starting with 1.16*8 Kbps of "''invisible"''
overhead caused by the very way the network works. Now, let's assume that
after each connection is established our amule sends something to the other side and waits to receive an answer.

''Total of 800 bytes + 800 bytes = 1600 bytes per second = 6400 bps = 6.4 Kbps''

What we have here is 6.4 Kbps of network overhead alone. Taking into account
that amule has other data to send (uploads) and it is not the only network
application running we will have the following picture:

Most likely the link to your provider is not that fast. aMule will ''try'' to open 10 connections per second and will ''try'' to upload on the specified speed.

Your operating system will share all available bandwidth between those and between amule and other network applications (browser for example). Actual results will vary depending on specific OS settings.

== ACK bottleneck ==
In all calculations above there was one assumption - zero download. But downloading is what amule was built for. So let's examine how the overhead
above affects your downloading speed. The answer is in TCP protocol.

When TCP is sending data, it requires that the other side acknowledge the reception. So if client A is sending data to client B by TCP, B has to send a special ACK packets to A which tells B "ok, I got it". If, however, A doesn't receive the ACK packets in time, he will assume that either packet is lost.

So, without going deeply into TCP specification: ''if B fails to send ACK to A, as a result A will transmit slower''.

Now let's see the situation in aMule. We saw in the previous chapter, that the uplink stream is congested by connection requests and uploads. As a result, there's a good chance that ACK packets for a file we are downloading ''will not be sent on time''.

The remote party will notice this and slow down. This is one more reason why the upstream should better not be too congested.

== Is there anything I can do? ==
OK, now that you understood why your network is so slow while amule is
running you will maybe look for a way to fix this. The answer in 2 words: "rate limit".

The first thing you should do is to assign realistic rate limits in amule
itself. If you have a uplink rate of 128 Kbps don't set amules upload limit to
16 (kilobytes per second) just because 128/8 = 16.

A better, but far more complicated solution is to use the QoS and packet scheduling services of your OS. For example, you can give a higher priority to ACK packets to solve the above mentioned "ACK bottleneck" problem.

The QoS topic, however, is beyond scope of this article.

== Router (switch, home network): is there any difference? ==
When the cable coming from your ISP is connected to some switching or routing
device, which in turn is connected to several PC's, bandwidth is shared between
them.

So, having N computers connected, an ideal device would simply provide
each one of them with 1/N of the total bandwidth. The situation may vary in real life, and your particular device may have different idea about fairness.

Since you're not going to have the hardware specs of your router chipset the only advice here is "try and see yourself".

== Multiple links ==
Until now, we talked about computers that are connected to the network through
single interface. While being most frequent, this is not mandatory. A user
may choose to connect via 2 (or more links) provided by different ISP's.
There're 2 reasons for this decision that I know about: link redundancy and
load balancing.

=== Link redundancy ===
In a case of link redundancy second link becomes operational when primary
link fails. This can be done automatically, or by explicit user command.
When this setup used, amule along with other network applications must be
restarted when links are being switched. This will allow to bind new address,
reconnect to server and receive new id. If amule is connected via  NAT
enabled router (it doesn't matter if you have low or high id), and links
are switched on the router, restart not needed.

=== Load balancing ===
This is far more complicated case. Both (all) links are simultaneously active,
and traffic is being distributed between them. The problem is that amule
bind all interfaces on the system i.e. 0.0.0.0. But, on ed2k
your id is your IP address, and you can not have 2. 
So, being short: that problem is that amule does not explicitly choose source
address for outgoing tcp connections. Note, that it doesn't
matter on which interface it listening. This is exactly opposite
from server applications line ftp or www server. When client
tries to connect to server he discover its address by resolving DNS. Resolver
reply will contain all IP addresses of specified host, and client should
try them all. Server, in turn, may choose not to listen on
one of them and thus prevent client from using this interface. In our case
amule is a client, and ed2k server discover its address from
source IP in connection request. That's where ed2k server will try to connect.
If connection succeed - client assigned high id, if not - low. The rest you
know.
The only solution in this situation (until amule will have an ability to
bind specific address) is to use amule on your "primary" link. 
You can, however, cause linux to send packet through interface of your choice.
But, most probably they will be dropped by ISP router as "spoofed" because
they source IP address doesn't match the address ISP assigned to that interface.

FAQ network

2005-02-27T13:21:04Z

199.203.130.250:

<h1>Network speed: what you should know before asking questions</h1>
by Froenchenko Leonid, <a href="lfroen@gmail.com">lfroen@gmail.com</a> 

<h2>Preface</h2>
The purpose of this document is to clarify different issues regarding network
speed that pops up from time to time in amule forum. Generally speaking, there're several reasons for questions about "amule & network":
<ul>
<li>Speed reported by amule doesn't match provider given rate</li>
<li>Pour performance of amule itself or another network application on same computer</li>
<li>What are key factors influencing network performance while amule is running
</li>
</ul>
Intended audience for this document are users who want to get better understanding of network functionality in general and in practical implication to amule functionality. 
This page, however, is not to be seen as comprehensive general purpose "Network
FAQ". 

<h2>Network speed - how match is it ?</h2>
While talking about network speed, people are using "bps" units, which mean
"bit per second". The reason for bit rather that byte is pretty
match historical, but also have engineering motivation behind. This motivation
comes from the fact, that not all networks in the world are transferring bytes. 
There's also convention to use capital "B" in "Bps" when speed is marked
in "bytes per second". However, this convention is not widely accepted. Particularly, organizations like IETF and IEEE are stick to original "bps". 

<h3>Prefixes</h3>
Since invention, networks made quite a progress, and now we have networks
that transfers thousand and millions bits more bits per second. For marking
those speeds, prefixes "kilo", "mega", "giga", "tera"
etc. are used. It is common mistake to think that values of those prefixes are same as in computer science, i.e. powers of 2. The truth is, that for historical reasons, prefixes in networking have decimal base, and not binary.

<table cellpadding="2" cellspacing="2" border="1" width="100%"
title="Table 1">
<tr>
<th valign="middle" title="Table 1" align="center"
bgcolor="#33ff33">Prefix 
</th>
<th valign="middle" align="center" bgcolor="#33ff33">meaning in computers 
</th>
<th valign="middle" title="Table 1" align="center"
bgcolor="#33ff33">meaning in networks 
</th>
<th valign="middle" align="center" bgcolor="#33ff33">difference, %% 
</th>
</tr>
<tr>
<td valign="top">K (kilo) 
</td>
<td valign="top">2^10 = 1024 
</td>
<td valign="top">10^3 = 1000 
</td>
<td valign="top">2% 
</td>
</tr>
<tr>
<td valign="top">M (mega) 
</td>
<td valign="top">2^20 = 1,048,576 
</td>
<td valign="top">10^6 = 1,000,000 
</td>
<td valign="top">5% 
</td>
</tr>
<tr>
<td valign="top">G (giga) 
</td>
<td valign="top">2^30 = 1,073,741,624 
</td>
<td valign="top">10^9 = 1,000,000,000 
</td>
<td valign="top">7% 
</td>
</tr>
<tr>
<td valign="top">T (tera) 
</td>
<td valign="top">2^40 = 1,099,511,627,776 
</td>
<td valign="top">10^12 = 1,000,000,000,000 
</td>
<td valign="top">9% 
</td>
</tr>
<tr>
<td valign="top"> 
</td>
<td valign="top"> 
</td>
<td valign="top"> 
</td>
<td valign="top"> 
</td>
</tr>

</table>
 
As you can from table above the error in calculation is about 5% when prefix
is incorrectly interpreted. Please, note, that speed, that provider tells
you is "speed in network", i.e. calculated on decimal base. 
For example when provider tells you that your link is "ADSL 256/128" you
should understand that he means 256000/128000 bps. Which means, that you have
64000/16000 bytes per second speed in your link. 

<h3>Protocol overhead - what is it about</h3>
When amule is running, it constantly "talks" with other "mules" and servers.
This data exchange is needed to identify itself, request information about
available sources and files, perform searches and so on. Since this information
have no use for user itself, it's called "overhead" i.e. inevitable addition
to the data you actually want to upload or download. Amule calls this "connection
overhead". However, the number amule presents, includes only size of actual
data that amule itself sending to the network stack. Later, this data is
sent down to the net with more overhead - now of network protocols. How match
is it - lets see in the next section. 

<h3>Network overhead</h3>
First of all - we're talking about IPv4 network. Once upon a time, there
was only one type of IP network. Now there's 2 - IP version  4, the old
we all know; and IP version 6 - the new one. ED2K protocol by design, is
unable to talk over IPv6 network, so users who have it (in Japan and China
for example) will not be able to connect "as is". Using IPv4 means, that each
packet (TCP, UDP, ICMP) will have IPv4 header. The minimum size of this header
is 20 bytes. Header can have optional parts (each 4 bytes) and it's up to
your provider  - for example my add 1 option dword. 
When talking to other thing on ed2k network, amule uses wide known TCP protocol.
UDP also used, but in match smaller scale. As reader might know, TCP is reliable protocol, i.e. it's guarantied that data sent from one side will arrive on the other or error will be reported. In order to achieve this, TCP send its own data to addition to actual transfer. This data includes TCP client initial negotiation, checksums, sequence numbers and acknowledgments. All this in TCP header which is added to each packet sent. Size of this header
is 20 bytes minimum. While being small overhead for large bulk transfer, it
can take significant part of bandwidth when small amounts of data are being
exchanged. This is exactly what happens on source discovery part of amule.
Our client is trying to establish connection and negotiate with large number
of other clients. Doing this, amule opens new TCP connections all the
time. The amount of those connections is controlled by "Maximum
number of connections in 5 seconds" setting in preferences. Typical number
is about 100. Each TCP connection results in at least 3 packets traveling
the net - one is SYN packet, i.e. connection request, and one ACK or RST
when connection is accepted or refused, and SYN+ACK to establish session.
There's more overhead of DNS queries when address is resolved, retries when
host doesn't reply and so on. 

<h5>On low level:</h5>
After passing TCP and IP layers, packets going down to network interface
driver. The kind of this driver is depends on the way your computer is connected to internet. For simplicity sake we will assume that this computer is connected toISP directly, i.e. you have no LAN (or switch or router) between.
Common setups that I'm aware of: 

<ol>
<li>Analog modem, connected to telephone line (ISDN modem falls in this category too)</li>
<li>Cable modem, connected through ethernet, ISP gives you IP address through DHCP</li>
<li>Cable modem, connected through ethernet, ISP requires you to configure PPPoE or PPTP tunnel</li>
<li>ADSL modem, connected through ethernet. You must have PPPoE or PPTP tunnel</li>
<li>Variation of above - modem connected to PC by USB. </li>

</ol>
In each of above setups have there're different protocols in work, and different headers added to transmitted packets. But, there's important thing to note: ethernet frames traveling between cable/ADSL modem and PC doesn't reach ISP. And consequently not counted in rate calculations. PPPoE and
PPTP headers, on the contrary does reach ISP. Whether or not
your particular provider includes them in rate calculations I obviously have
no idea. For this reason I will exclude those headers from my calculations.
If you think that your ISP includes it, add 4 bytes to the size of each packet. 

<h5>Example:</h5>
Let's see how match network overhead we have on typical network. Our connection
is cable modem connected with ethernet link to PC directly (no router between).
In this setup we have IPv4 packets sent over ethernet. 
Lets say we have 10 new connection opened each second, and all accepted
(successfully established TCP session). This alone have (I'm counting data
going up - from my computer to the net): 
 
10 connection * 2 packets * (20 bytes of TCP + 20 bytes of IPv4) = 800 bytes. 
 
This mean that we starting with  1.16*8 Kbps of "invisible"
overhead caused by the very way the network works. Now, let's assume that
after each connection is established our amule sends something to other side
and waits to receive an answer. 
 
10 connections * (1 packet of data + 1 ACK)*(20 bytes of TCP + 20 bytes of IPv4) = 800 bytes. 
 
Total of 800 bytes + 800 bytes = 1600 bytes per second = 6400 bps = 6.4 Kbps 
 
What we have here is 6.4 Kbps of network overhead alone. Taking into account
that amule have another data to send (uploads) and it is not the only network
application running we will have following picture. Most chances that your
link to provider is not that fast.  Amule will try to open
10 connections per second and will try to upload on specified
speed. Operating system will share available bandwidth between those and between amule and other network applications (browser for example). Actual results will vary depending on specific OS settings. 

<h3>ACK bottleneck</h3>
In all calculations above there was one assumption - zero download. But, downloading is what the amule was build for. So, let's examine how the overhead
above affect downloading speed. The answer is in TCP protocol. When TCP sending
data, it requires from other side to acknowledge the reception. So, if client
A sending data to client B by TCP, B have to send to A special ACK packets
which tells B "ok, I've got it". If, however, A doesn't receive ACK packets
in time, he will assume that either packet is lost. So, without going deeply
into TCP specification: if B fails to send ACK to A, as a result A will
transmit slower. 
Now let's see situation in amule. We saw in previous chapter, that uplink
stream is congested by connections requests and uploads. As a result, there's
good chance that ACK packet for file we downloading will not be sent
on time. Remote party will notice and will slow down. This is one
more reason why upstream better not be too congested. 

<h3>Is there something I could do ?</h3>
OK, now when you understand while your network is so slow while amule is
running you would search a way to fix it. The answer in 2 words: "rate limit".
The first thing you should do is to assign realistic rate limits in amule
itself. If you have 128 Kbps uplink rate, don't set amule upload limit to
16 (kilobytes per second) just because 128/8=16. 
Better, but far more complicated solution is to use QoS and packet scheduling
services of your OS. For example, you can give higher priority to ACK packets
to solve above "ACK bottleneck" problem. The QoS topic, however, is beyond
scope of this article. 
 

<h3>Router (switch, home network):  is there any difference ?</h3>
When cable coming from your ISP is connected to some switching or routing
device, which in turn is connected to several PC's, bandwidth is shared between
them. So, having N computers connected, ideal device would simply provide
each one of them with 1/N of total bandwidth. Situation may vary in the real
life, and your particular device may have different idea about fairness. Since
you're not going to have hardware specs about your router chipset, the only
advice here is "try and see yourself".

FAQ amuled

2004-10-10T13:09:57Z

199.203.130.250:

This is full featured aMule, running without any user interface (GUI). It is controlled by remote access thru amuleweb, amulecmd or ed2k utilities.

Stripped from GUI, amuled have reduced memory and CPU requirements; it can run without X at all.