AMule Project FAQ - User contributions [en]

AMuleWeb

2005-11-25T18:06:52Z

147.83.41.10:

== 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''
**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.

=== aMuleWeb with [[aMule]] 2.0.0-rcX versions ===

*[http://www.gnu.org/software/tar/tar.html Untar] the sources and copy '''''src/aMule.tmpl''''' or in new versions (you are using a ''new version'' if you don't have the file ''aMule.tmpl'' in ''src/'') only the following dir '''''src/webserver/''''' into your '''''~/.aMule/''''' directory. The following (run from the sources directory), should do so:
:''$ cp -r src/aMule.tmpl src/webserver/ ~/.aMule/''

* If you installed [[aMule]] from rpm, then you can do:
:''$ cp /usr/share/amuleweb/aMule.tmpl ~/.aMule/''
:''$ cp -r /usr/share/amuleweb/webserver/ ~/.aMule/''
:'''NOTE''': Note that in current versions (since [[aMule]] 2.0.0) the above step is not necessary (in fact, it is incorrect).

*Go to "Preferences"->"Remote Controls" (in [[aMule]]) and...
**Enable "Accept External Connections".
**Enable "Use TCP ports instead of unix local sockets".
**Enter a password for external connections. If you don't do this, amuleweb will not communicate with amule.

::'''NOTE:''' On some early [[aMule]] 2.0.0-rcX versions the above options weren't available (or didn't work). Use this if you want to run [[aMuled]], too. If you are using such [[aMule]] version and you don't wish to upgrade, then do the following:

:Shutdown [[aMule]] if it is still running.
:Edit your ''~/.eMule'' file, locate the ''[ExternalConnect]'' section and change:
::''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''

::'''NOTE:''' Since [[aMule]] 2.0.0 the ''~/.eMule'' file is now called ''~/.aMule/amule.conf''.

*Restart [[aMule]]

*Go to your "Preferences"->"Remote Controls" (in [[aMule]]) and setup your passwords here for [[External Connections]] and aMuleWeb login.
::'''NOTE:''' When you change your aMuleWeb and [[External Connections]] ports here, make sure to restart [[aMule]].
::'''NOTE:''' that ''"Enable aMuleWeb"'' has no effect and will be renamed in 2.0.0rc8. aMuleWeb is always enabled as long as you have [[External Connections]] enabled.
::'''NOTE:''' For users running [[aMuled|aMule Daemon]] you have to edit the ''.eMule'' file like shown above. For a way to setup a password check the [[Webserver-1.2.x|1.2.8 aMule HowTo]]. You can still do it in the same way.

*Now you're done! You are ready to run amuleweb and connect to it.

'''[[User:Stefanero|Stefanero]]'''

=== Webserver with aMule 1.2.8 or earlier ===

The following is based on the original instruction by BigBob. They guide you on how to modify [[aMule]]'s configuration files to set aMuleWeb correctly.

There is "Preferences"->"Remote Controls" now, but anyway, information is never a bad idea.

*Shutdown [[aMule]] to avoid overwritting config files while shutting down.
*Copy from [[aMule]]'s sources (version 1.2.4 or later) the directory ''src/webserver/'' into your ''~/.aMule/webserver/'' directory.
*Copy from [[aMule]]'s sources (version 1.2.4 or later) the file ''src/aMule.tmpl'' into your ''~/.aMule/aMule.tmpl'' directory.
*Open a terminal and type (you might have to install ''[http://www.delorie.com/gnu/docs/textutils/md5sum.1.html md5sum]''):
:''echo -n "'''THEPASWORDYOUWANT'''" | md5sum | cut -d " " -f 1''
:This command will reply with an [[MD4 hash|MD5 hash]]. Something like: 324f85f6095f9e5fe25b6c85af44b445
*Edit your ''~/.eMule'' file, locate the ''[ExternalConnect]'' section in it and change this fields:
:''AcceptExternalConnections=1'' <- To enable [[aMule]] to listen for [[External Connections]].
:''ECUseTCPPort=0'' <- Set this to 1 to use the [http://www.faqs.org/faqs/internet/tcp-ip/resource-list TCP] port. If disabled [[External Connections]] will fail!!
:''ECPort=4712'' <- Put here the port on which you want [[aMule]] to listen for [[External Connections]].
:''ECPassword=39e5049d0614baf21906500e2261d500'' <- Put here the password for [[External Connections]]<nowiki>'</nowiki> authentications you generated before in terminal (something like 324f85f6095f9e5fe25b6c85af44b445).
*Edit your ''~/.eMule'' file, locate the ''[WebServer]'' section in it and change fields:
:''Password=324f85f6095f9e5fe25b6c85af44b445'' <- Put here the password generated with [http://www.delorie.com/gnu/docs/textutils/md5sum.1.html md5sum] for the admin (full privileged users).
:''PasswordLow=1db5a746266e941b3ef7dd3586863ca7'' <- Put here the password generated with [http://www.delorie.com/gnu/docs/textutils/md5sum.1.html md5sum] for "low users" (low privileged users).
:''Port=10000'' <- Put the port you want aMuleWeb to listen on.
:''Enabled=1'' <- This option has been deprecated and is completly ignored now. Enabling External Connections will enable any application it connects to it, including [[aMuleWeb]].
:''UseGzip=1'' <- Enable compression on communication.
:''PageRefreshTime=120'' <- Put here the web page refresh time (in seconds).
:''UseLowRightsUser=0'' <- 0/1 (disabled/enabled) "low user" access.
*Restart [[aMule]].
*Once [[aMule]] is running, start the web interface (aMuleWeb).
*Now point your web browser to http://localhost:10000 (or whatever your host and ports are) and authenticate yourself with "Password" (for full privileged user) or "PasswordLow" (for low privileged user, if enabled).
*That's all :)

:'''NOTE:'' In latest [[aMule]] 1.2.x releases, the option ''WebTemplateFile'' allows to override the file template to use (thanks to [[User:Stefanero|Stefanero]]. You can set this option in the ''[eMule]'' section. Example:

:''WebTemplateFile=eMule.tmpl''

== 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]]'''

== 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]].

MlDonkey

2005-06-05T15:34:10Z

147.83.41.10:

== What is [http://mldonkey.berlios.de mlDonkey] ? ==

[http://mldonkey.berlios.de mlDonkey] was the first (partially) open-source client for the [[FAQ_eD2k-Kademlia|ed2k network]], and the source of much controversy due to features that others considered harmful to the [[FAQ_eD2k-Kademlia|ed2k network]]. The core network code was originally kept closed-sources in order to prevent [[Leech|leecher-mods]], however, this was changed after [[eMule]] arrived with a fully open-source client.

Unlike the Mule [[Client]]s, [http://mldonkey.berlios.de mlDonkey] was created as a [[Server|server]]/[[Client|client]] system from the beginning, which means that it runs as a daemon, without the need for a GUI, though many separate GUIs are available. This makes it the client of choice for people who wish to run it on a router or such.

[http://mldonkey.berlios.de mlDonkey] also boasts of supporting other networks than the [[FAQ_eD2k-Kademlia|ed2k network]], such as
* [[Overnet]]
* [[DirectConnect]] (alpha)
* [[Gnutella]] and [[Gnutella2_(G2)|Gnutella2]]
* [[OpenNapster]] (alpha)
* [[SoulSeek]] (beta)
* [[BitTorrent]]
* [[FastTrack]]
* [[AudioGalaxy]] (defunct)
* HTTP, FTP and SSH through FileTP

Since [http://mldonkey.berlios.de mlDonkey] 2.5.30-x, a feature know as ''swarming'' is supported. With this, it is possible download a file from [[kazaa|Fastrack]], [[BitTorrent]] and [[FAQ_eD2k-Kademlia|ed2k]] networks at same time.

'''NOTE:''' [[aMule]] is a '''separate''' project and is '''not''' related to
[http://mldonkey.berlios.de mlDonkey] in any way.

Talk:HowTo Compile In Debian/Ubuntu

2005-05-17T16:47:23Z

147.83.41.10:

To successully compile aMule in my Sarge I had to create a link like this:

''ln -s /usr/include/crypto++ /usr/include/cryptopp''

because the make process searchs for config.h in cryptopp directory, not in crypto++.

'''They might have hanged the pathnames again. Thanks for the info :-) '''
'''The problem is that both crypto++ and Debian's crypto++ package have been changing the pathnames in order to suit, and this has become a mess. hehehe '''
'''Anyway, since next [[aMule]] release (it is currenly already implemented into aMule CVS) crypto++ will no longer be needed since it's necessary functions have been coded into aMule. '''
'''Again, thanks for the info!'''

----

28/09/04 - stk : A small error in step 8 : remplace "ls -s /usr/include/crypto++ /usr/include/cryptopp" by "ln -s /usr/include/crypto++ /usr/include/cryptopp" ;)

'''Thanx a lot! Fixed.'''

----

other info : In my Sarge, with libcrypto++5.1_5.1-5_i386.deb and libcrypto++-dev_5.1-5_i386.deb package, I have an error : ld cannot find lcryptopp..

so, I have made a link with this command : "ln -s /usr/lib/libcrypto++5.1.so /usr/lib/libcryptopp.so" and run ldconfig -> it work !

'''I completly forgot to answer to you :-( i added your comment to the howto some long time ago. thanks :)'''

----

jeremie :

Installing 200rc6 is a piece of cake with your advices. (sarge on 20041019)

No more fuss about crypto++ and so on, just apt-get the packages, then configure / make / make install.

It takes 5 minutes.

Thanks for the names of the dependancies.

'''Very much thanks for your words! Makes me feel batter :)'''

----

Works just fine in Ubuntu

I just wanted to let you know that this HowTo also applies just fine to "HowTo Compile in Unbuntu". Sure, anyone would have probably guessed that, but I can confirm it now... :-)

'''Hey! Thanx! THat is indeed an important note since Ubunto is being so successful and popular lately. I'll try to fix it somewhere to link ubunto users there too :)'''

----

Hi, I had problems with the ''libcurl2-dev''. Is ''libcurl3-dev'' the actual package?

'''Yes, you can use libcurl3-dev without any problems. In fact, thatnks for the note, i just changed it to point to liburl3 in the guide ;-)'''

-----

17/05/2005
Hi, I don't want compile amule :-), so I add ''deb http://www.vollstreckernet.de/debian/ testing amule'' and
''deb http://www.vollstreckernet.de/debian/ testing wx'' in my /etc/apt/sources.list. But ''apt-get update && apt-get install amule'' don't work... I find an error in ''http://www.vollstreckernet.de/debian/dists/testing/amule/binary-i386/Packages.gz
''. In fact, Packages.gz is broken!!!

'''Please contact Vollstrecker in http://forum.amule.org or mail him. He is the deb packager for CVS builds. Thanks :-)'''

Talk:Proxy

2005-05-03T10:24:36Z

147.83.41.10:

This is all nice and dandy, but can you configure aMule to use a proxy?

'''Of course: Prefereces -> Proxy'''

'''I guess you didn't search much...'''

How to launch VNC with aMule at Linux boot

2005-05-03T10:21:09Z

147.83.41.10:

<h2>''By [[User:Frankk|Frankk]]''</h2>

== General ==

This describes a very simple configuration to launch [http://www.redstonesoftware.com/vnc.html VNC] at [http://www.kernel.org Linux] startup (as a specified user). [[aMule]] will be launched automatically with [http://www.redstonesoftware.com/vnc.html VNC].
This will work in [http://www.slackware.com Slackware] and distro based on the same init method. If someone knows how to modify it to make it work under other distros you are welcome to add it to this page. Thanks.

Add the ''rc.vnc'' script to ''/etc/rc.d''

Modify user according to the user running [[aMule]]. 
The ''rm /tmp/.X11-unix/X$theScreen'' is there in case the server crashes or your mother/wife/husband removes the power plug cleaning the room... ;-)

''#!/bin/sh'' 
''#'' 
''# Startup/Stop script for vncserver.'' 
''#'' 

''#Here, the choosen user to run amule'' 
''theUser=choosenuser'' 
''#And here, the choosen screen to run the vncserver'' 
''theScreen=1''

''case "$1" in''

'' 'start')''
''if [ -f /tmp/.X11-unix/X$theScreen ]; then rm /tmp/.X11-unix/X$theScreen; fi'' 
''/bin/su - $theUser -c "PATH=/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin /usr/bin/vncserver :$theScreen"'' 
'';;''

'' 'stop')'' 
''/bin/su - $theUser -c "PATH=/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin /usr/bin/vncserver -kill :$theScreen"'' 
'';;''

''*)'' 
''echo "Usage: /etc/rc.d/rc.vnc { start | stop }"'' 
'';;''

''esac''

Make it executable with:

''<pre>chmod 755 /etc/rc.d/rc.vnc</pre>''

Modify the following files:

In ''/etc/rc.d/rc.local'' add:

''# Start VNC server'' 
''if [ -x /etc/rc.d/rc.vnc ]; then'' 
''. /etc/rc.d/rc.vnc start'' 
''fi''

In ''/etc/rc.d/rc.6'' add:

''# Shut down the VNC server'' 
''if [ -x /etc/rc.d/rc.vnc ]; then'' 
''/etc/rc.d/rc.vnc stop'' 
''fi''

In ''~/.vnc/xstartup'' (in home directory of the user specified above) add (change with your preferred [[aMule]] startup script):

''amule &''

== On [http://www.debian.org Debian] Woody ==

Run (as root):

''apt-get install vncserver xvncviewer flwm''

There is no support for ''~/.vnc/xstartup'' so, instead, use ''$vncStartup'' in ''.vncrc'' to determine a xstartup-script (this replaces your ''~/.xsession'' file).

For more information, read ''man vnc.conf''

For example, in a Woody/Sarge/Sid: 
Login as the user who is going to run [[aMule]] 
''mkdir ~/.vnc/'' 
Create the ''~/.vnc/xstartup'' file, with the next content 

''/usr/bin/flwm &'' 
''/usr/bin/amule &'' 
''/usr/bin/amule &''

With sone versions of [http://www.redstonesoftware.com/vnc.html vncserver], it's necessary to launch at least twice the [[aMule]]. The [http://flwm.sourceforge.net flwm] is an optional window manager.

Create the file ''~/.vncrc'' with the next content: 
Login as the user and run ''xvncviewer :1'' to create the password file and debug possible probelms (the logs are under the ''~/.vnc/'' dir

''$vncStartup = "/home/amule/.vnc/xstartup";'' 
''$geometry ="800x600";''

(replace ''/home/amule'' for the home of the user running [http://www.redstonesoftware.com/vnc.html VNC])

To show the [[aMule]] window, run:
''xvncviewer localhost:1''

If you want to autostart a [http://www.redstonesoftware.com/vnc.html VNC] session on system startup, you can put a line in ''/etc/init.d/bootmisc.sh'' like this:

''su '''username''' -c vncserver''

Replace '''username''' with the name of the user that you want to launch vnc. (Added by '''ghent''')

== To start [[aMuleWeb]] also at startup: ==

This is probably the most unelegant way to do this, but it seems to work.

The problem is that you have to supply user input when starting [[aMuleWeb]] (the password).

You can circumvent this with supplying a password with the ''-pw'' option: ''amuleweb -pw ""'' (this is for no password, you have to remove the [http://www.ietf.org/rfc/rfc1321.txt MD5 sum] from the ''ECPassword'' entry in your ''~/.eMule'' file for this to work).

Now [[aMuleWeb]] starts without any user input, but unfortunately it wouldn't work when we would just add it to the xstartup-file, because [[aMule]] needs a few seconds more to start up.

Therefor we have to start [[aMuleWeb]] a few seconds after [[aMule]].

To achieve this, we add a line similar to this one:

''/bin/sh /home/aMule/amuleweb-start.sh &''

to the xstartup-file.

And in the home-directory, we create a file called ''amuleweb-start.sh'', with the following content:

#! /bin/sh
sleep 30;
/usr/bin/amuleweb -pw "";

That's all.

Like I said, probably extremely amateurish, but it should work...

== [http://www.mandrake.com Mandrake] 10.0 ==

The script from [[User:Frankk|Frankk]] is the one I use, but you can customize the size of the [http://www.redstonesoftware.com/vnc.html VNC] server :
''/bin/su - $theUser -c "PATH=/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin /usr/bin/vncserver :$theScreen"''

add

''/bin/su - $theUser -c "PATH=/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin /usr/bin/vncserver :$theScreen -geometry 1240x980"''

or whatever value.

Personaly, I use as xstartup script ([http://www.icewm.org iceWM] is really nice and so CPU-cheap) :

''#!/bin/sh'' 
''starticewm&'' 
''amule''

To start [http://www.redstonesoftware.com/vnc.html VNC] at startup, I called the previous script ''/etc/init.d/amulevnc'' and chmod to 744 (''chmod 744 /etc/init.d/amulevnc'' as root). 
Instead of modifying ''/etc/rc.d/rc.vnc'', I added links in the corresponding ''/etc/rc$RUNLEVEL.d'' directories. 
It's quite simple to understand how it works: 
Each directory represents a runlevel, and contains links to the scripts from ''/etc/init.d'' which need to be run/stop. 
For instance, the link ''/etc/rc5.d/S55sshd'' to ''/etc/init.d/sshd'' will start ''sshd'' on runlevel 5,
whereas ''/etc/rc6.d/K25sshd'' linked to ''/etc/init.d/sshd'' will stop it in runlevel 6. 
You get it? Links starting with 'KXX' will stop a service, and those starting with 'SXX' will start them. The number will define the order.

So to run [http://www.redstonesoftware.com/vnc.html VNC] on startup, just do (as root :-) )
''re>ln -s /etc/init.d/amulevnc /etc/rc5.d/S99amule''
''ln -s /etc/init.d/amulevnc /etc/rc6.d/K02amule''
and you're all set!

PS: This method should work on systems other than [http://www.mandrake.com Mandrake], give it a test.

Questions & comments: ''air_1 '''at''' libertysurtf.fr''

== [http://www.gentoo.org Gentoo] ==

For [http://www.gentoo.org Gentoo]'ers follow these steps:

'''ATENTION: THE BOOT PROCESS DOESN'T WORK, I'LL TRY TO FIX IT AS SOON AS POSSIBLE'''

Why, while my HD died a couple of days, I had to re-install [http://www.gentoo.org Gentoo] and I'm having some problems with [http://www.x.org X] and [http://fluxbox.sourceforge.net fluxbox], as soon as this is fixed, I'll be needing this to work, so change WILL be made to correct what's wrong. Sorry, --[[User:PedroAlgarvio|PedroAlgarvio]] 21:37, 2 May 2005 (CEST)

=== Install [http://www.realvnc.com VNC] ===

This is a how to for a server with no X window manager at all. I only run web and mail services, and o course, aMule. Adapt to you're sictuation.
I use [http://www.tightvnc.com TightVNC], but should also work with other [http://www.realvnc.com VNC]'s.

emerge tightvnc

=== Configuring [http://www.realvnc.com VNC] ===

==== Server Config ====

To configure the [http://www.realvnc.com VNC] server, execute:

vncserver :1

You'll be asked to answer some questions, such as password, answer accordingly. After you can kill it:

vncserver -kill :1

==== Programs to Start ====

Now let's config what should be started with this [http://www.realvnc.com VNC] session:
edit ~/.vnc/xstartup

vi ~/.vnc/xstartup

You should see something like:

#!/bin/sh

xrdb $HOME/.Xresources
xsetroot -solid grey
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
twm &

[http://www.x.org xterm] is a console, and [http://www.x.org twm] is the window manager. I use [http://fluxbox.sourceforge.net fluxbox], and don't want no terminal, just [[aMule]] so, it's like this:

#!/bin/sh

xrdb $HOME/.Xresources
xsetroot -solid grey
amule &
fluxbox &

=== Starting [http://www.realvnc.com VNC] at boot ===

Since I won't be starting no Window Manager at boot, but still want [[aMule]] started with the user interface(you could just run [[aMuled]]), I'll need an init script:

vi /etc/init.d/vncserver

Make it look like:

#!/sbin/runscript
# Copyright 1999-2005 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $

depend() {
need net
}

checkconfig() {
ebegin "Check config"
#PATH="$PATH:/usr/X11R6/bin/"

# The Username that will run VNC
USER="vampas"

# The display that VNC will use
DISPLAY="1"

# The Desktop geometry to use.
#GEOMETRY="<WIDTH>x<HEIGHT>"
#GEOMETRY="1280x1024"
GEOMETRY="1024x780"

# The name that the VNC Desktop will have.
NAME="aMule"
}

start() {
checkconfig
ebegin "Starting vncserver for user ${USER} on localhost:${DISPLAY}"
su ${USER} -c "/usr/bin/vncserver -name ${NAME} -geometry ${GEOMETRY} :${DISPLAY}"
eend $?
}

stop() {
checkconfig
ebegin "Stoping vncserver for user ${USER} on localhost:${DISPLAY}"
su ${USER} -c "/usr/bin/vncserver -kill :${DISPLAY}"
eend $?
}

restart() {
svc_stop
svc_start
}

Make it executable:

chmod +x /etc/init.d/vncserver

Now add it to boot:

rc-update add vncserver default

And you should be ready to go, if not ''<ufs AT sapo DOT pt>''

--[[User:PedroAlgarvio|PedroAlgarvio]] 06:10, 2 May 2005 (CEST)

User:PedroAlgarvio

2005-05-02T16:41:16Z

147.83.41.10:

[[aMule]] user

'''[[aMule]] concerns:'''

*Did the [[How_to_launch_VNC_with_aMule_at_Linux_boot#Gentoo|Gentoo aMule boot]] article

How to launch VNC with aMule at Linux boot

2005-05-02T16:40:03Z

147.83.41.10:

<h2>''By [[User:Frankk|Frankk]]''</h2>

== General ==

This describes a very simple configuration to launch [http://www.redstonesoftware.com/vnc.html VNC] at [http://www.kernel.org Linux] startup (as a specified user). [[aMule]] will be launched automatically with [http://www.redstonesoftware.com/vnc.html VNC].
This will work in [http://www.slackware.com Slackware] and distro based on the same init method. If someone knows how to modify it to make it work under other distros you are welcome to add it to this page. Thanks.

Add the ''rc.vnc'' script to ''/etc/rc.d''

Modify user according to the user running [[aMule]]. 
The ''rm /tmp/.X11-unix/X$theScreen'' is there in case the server crashes or your mother/wife/husband removes the power plug cleaning the room... ;-)

''#!/bin/sh'' 
''#'' 
''# Startup/Stop script for vncserver.'' 
''#'' 

''#Here, the choosen user to run amule'' 
''theUser=choosenuser'' 
''#And here, the choosen screen to run the vncserver'' 
''theScreen=1''

''case "$1" in''

'' 'start')''
''if [ -f /tmp/.X11-unix/X$theScreen ]; then rm /tmp/.X11-unix/X$theScreen; fi'' 
''/bin/su - $theUser -c "PATH=/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin /usr/bin/vncserver :$theScreen"'' 
'';;''

'' 'stop')'' 
''/bin/su - $theUser -c "PATH=/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin /usr/bin/vncserver -kill :$theScreen"'' 
'';;''

''*)'' 
''echo "Usage: /etc/rc.d/rc.vnc { start | stop }"'' 
'';;''

''esac''

Make it executable with:

''<pre>chmod 755 /etc/rc.d/rc.vnc</pre>''

Modify the following files:

In ''/etc/rc.d/rc.local'' add:

''# Start VNC server'' 
''if [ -x /etc/rc.d/rc.vnc ]; then'' 
''. /etc/rc.d/rc.vnc start'' 
''fi''

In ''/etc/rc.d/rc.6'' add:

''# Shut down the VNC server'' 
''if [ -x /etc/rc.d/rc.vnc ]; then'' 
''/etc/rc.d/rc.vnc stop'' 
''fi''

In ''~/.vnc/xstartup'' (in home directory of the user specified above) add (change with your preferred [[aMule]] startup script):

''amule &''

== On [http://www.debian.org Debian] Woody ==

Run (as root):

''apt-get install vncserver xvncviewer flwm''

There is no support for ''~/.vnc/xstartup'' so, instead, use ''$vncStartup'' in ''.vncrc'' to determine a xstartup-script (this replaces your ''~/.xsession'' file).

For more information, read ''man vnc.conf''

For example, in a Woody/Sarge/Sid: 
Login as the user who is going to run [[aMule]] 
''mkdir ~/.vnc/'' 
Create the ''~/.vnc/xstartup'' file, with the next content 

''/usr/bin/flwm &'' 
''/usr/bin/amule &'' 
''/usr/bin/amule &''

With sone versions of [http://www.redstonesoftware.com/vnc.html vncserver], it's necessary to launch at least twice the [[aMule]]. The [http://flwm.sourceforge.net flwm] is an optional window manager.

Create the file ''~/.vncrc'' with the next content: 
Login as the user and run ''xvncviewer :1'' to create the password file and debug possible probelms (the logs are under the ''~/.vnc/'' dir

''$vncStartup = "/home/amule/.vnc/xstartup";'' 
''$geometry ="800x600";''

(replace ''/home/amule'' for the home of the user running [http://www.redstonesoftware.com/vnc.html VNC])

To show the [[aMule]] window, run:
''xvncviewer localhost:1''

If you want to autostart a [http://www.redstonesoftware.com/vnc.html VNC] session on system startup, you can put a line in ''/etc/init.d/bootmisc.sh'' like this:

''su '''username''' -c vncserver''

Replace '''username''' with the name of the user that you want to launch vnc. (Added by '''ghent''')

== To start [[aMuleWeb]] also at startup: ==

This is probably the most unelegant way to do this, but it seems to work.

The problem is that you have to supply user input when starting [[aMuleWeb]] (the password).

You can circumvent this with supplying a password with the ''-pw'' option: ''amuleweb -pw ""'' (this is for no password, you have to remove the [http://www.ietf.org/rfc/rfc1321.txt MD5 sum] from the ''ECPassword'' entry in your ''~/.eMule'' file for this to work).

Now [[aMuleWeb]] starts without any user input, but unfortunately it wouldn't work when we would just add it to the xstartup-file, because [[aMule]] needs a few seconds more to start up.

Therefor we have to start [[aMuleWeb]] a few seconds after [[aMule]].

To achieve this, we add a line similar to this one:

''/bin/sh /home/aMule/amuleweb-start.sh &''

to the xstartup-file.

And in the home-directory, we create a file called ''amuleweb-start.sh'', with the following content:

#! /bin/sh
sleep 30;
/usr/bin/amuleweb -pw "";

That's all.

Like I said, probably extremely amateurish, but it should work...

== [http://www.mandrake.com Mandrake] 10.0 ==

The script from [[User:Frankk|Frankk]] is the one I use, but you can customize the size of the [http://www.redstonesoftware.com/vnc.html VNC] server :
''/bin/su - $theUser -c "PATH=/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin /usr/bin/vncserver :$theScreen"''

add

''/bin/su - $theUser -c "PATH=/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin /usr/bin/vncserver :$theScreen -geometry 1240x980"''

or whatever value.

Personaly, I use as xstartup script ([http://www.icewm.org iceWM] is really nice and so CPU-cheap) :

''#!/bin/sh'' 
''starticewm&'' 
''amule''

To start [http://www.redstonesoftware.com/vnc.html VNC] at startup, I called the previous script ''/etc/init.d/amulevnc'' and chmod to 744 (''chmod 744 /etc/init.d/amulevnc'' as root). 
Instead of modifying ''/etc/rc.d/rc.vnc'', I added links in the corresponding ''/etc/rc$RUNLEVEL.d'' directories. 
It's quite simple to understand how it works: 
Each directory represents a runlevel, and contains links to the scripts from ''/etc/init.d'' which need to be run/stop. 
For instance, the link ''/etc/rc5.d/S55sshd'' to ''/etc/init.d/sshd'' will start ''sshd'' on runlevel 5,
whereas ''/etc/rc6.d/K25sshd'' linked to ''/etc/init.d/sshd'' will stop it in runlevel 6. 
You get it? Links starting with 'KXX' will stop a service, and those starting with 'SXX' will start them. The number will define the order.

So to run [http://www.redstonesoftware.com/vnc.html VNC] on startup, just do (as root :-) )
''re>ln -s /etc/init.d/amulevnc /etc/rc5.d/S99amule''
''ln -s /etc/init.d/amulevnc /etc/rc6.d/K02amule''
and you're all set!

PS: This method should work on systems other than [http://www.mandrake.com Mandrake], give it a test.

Questions & comments: ''air_1 '''at''' libertysurtf.fr''

== [http://www.gentoo.org Gentoo] ==

For [http://www.gentoo.org Gentoo]'ers follow these steps:

=== Install [http://www.realvnc.com VNC] ===

This is a how to for a server with no X window manager at all. I only run web and mail services, and o course, aMule. Adapt to you're sictuation.
I use [http://www.tightvnc.com TightVNC], but should also work with other [http://www.realvnc.com VNC]'s.

emerge tightvnc

=== Configuring [http://www.realvnc.com VNC] ===

==== Server Config ====

To configure the [http://www.realvnc.com VNC] server, execute:

vncserver :1

You'll be asked to answer some questions, such as password, answer accordingly. After you can kill it:

vncserver -kill :1

==== Programs to Start ====

Now let's config what should be started with this [http://www.realvnc.com VNC] session:
edit ~/.vnc/xstartup

vi ~/.vnc/xstartup

You should see something like:

#!/bin/sh

xrdb $HOME/.Xresources
xsetroot -solid grey
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
twm &

[http://www.x.org xterm] is a console, and [http://www.x.org twm] is the window manager. I use http://fluxbox.sourceforge.net fluxbox], and don't want no terminal, just [[aMule]] so, it's like this:

#!/bin/sh

xrdb $HOME/.Xresources
xsetroot -solid grey
amule &
fluxbox &

=== Starting [http://www.realvnc.com VNC] at boot ===

Since I won't be starting no Window Manager at boot, but still want [[aMule]] started with the user interface(you could just run [[aMuled]]), I'll need an init script:

vi /etc/init.d/vncserver

Make it look like:

#!/sbin/runscript
# Copyright 1999-2005 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $

depend() {
need net
}

checkconfig() {
ebegin "Check config"
#PATH="$PATH:/usr/X11R6/bin/"

# The Username that will run VNC
USER="vampas"

# The display that VNC will use
DISPLAY="1"

# The Desktop geometry to use.
#GEOMETRY="<WIDTH>x<HEIGHT>"
#GEOMETRY="1280x1024"
GEOMETRY="1024x780"

# The name that the VNC Desktop will have.
NAME="aMule"
}

start() {
checkconfig
ebegin "Starting vncserver for user ${USER} on localhost:${DISPLAY}"
su ${USER} -c "/usr/bin/vncserver -name ${NAME} -geometry ${GEOMETRY} :${DISPLAY}"
eend $?
}

stop() {
checkconfig
ebegin "Stoping vncserver for user ${USER} on localhost:${DISPLAY}"
su ${USER} -c "/usr/bin/vncserver -kill :${DISPLAY}"
eend $?
}

restart() {
stop
start
}

Make it executable:

chmod +x /etc/init.d/vncserver

Now add it to boot:

rc-update add vncserver default

And you should be ready to go, if not ''<ufs AT sapo DOT pt>''

--[[User:PedroAlgarvio|PedroAlgarvio]] 06:10, 2 May 2005 (CEST)

How to launch VNC with aMule at Linux boot

2005-05-02T16:38:37Z

147.83.41.10:

<h2>''By [[User:Frankk|Frankk]]''</h2>

== General ==

This describes a very simple configuration to launch [http://www.redstonesoftware.com/vnc.html VNC] at [http://www.kernel.org Linux] startup (as a specified user). [[aMule]] will be launched automatically with [http://www.redstonesoftware.com/vnc.html VNC].
This will work in [http://www.slackware.com Slackware] and distro based on the same init method. If someone knows how to modify it to make it work under other distros you are welcome to add it to this page. Thanks.

Add the ''rc.vnc'' script to ''/etc/rc.d''

Modify user according to the user running [[aMule]]. 
The ''rm /tmp/.X11-unix/X$theScreen'' is there in case the server crashes or your mother/wife/husband removes the power plug cleaning the room... ;-)

''#!/bin/sh'' 
''#'' 
''# Startup/Stop script for vncserver.'' 
''#'' 

''#Here, the choosen user to run amule'' 
''theUser=choosenuser'' 
''#And here, the choosen screen to run the vncserver'' 
''theScreen=1''

''case "$1" in''

'' 'start')''
''if [ -f /tmp/.X11-unix/X$theScreen ]; then rm /tmp/.X11-unix/X$theScreen; fi'' 
''/bin/su - $theUser -c "PATH=/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin /usr/bin/vncserver :$theScreen"'' 
'';;''

'' 'stop')'' 
''/bin/su - $theUser -c "PATH=/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin /usr/bin/vncserver -kill :$theScreen"'' 
'';;''

''*)'' 
''echo "Usage: /etc/rc.d/rc.vnc { start | stop }"'' 
'';;''

''esac''

Make it executable with:

''<pre>chmod 755 /etc/rc.d/rc.vnc</pre>''

Modify the following files:

In ''/etc/rc.d/rc.local'' add:

''# Start VNC server'' 
''if [ -x /etc/rc.d/rc.vnc ]; then'' 
''. /etc/rc.d/rc.vnc start'' 
''fi''

In ''/etc/rc.d/rc.6'' add:

''# Shut down the VNC server'' 
''if [ -x /etc/rc.d/rc.vnc ]; then'' 
''/etc/rc.d/rc.vnc stop'' 
''fi''

In ''~/.vnc/xstartup'' (in home directory of the user specified above) add (change with your preferred [[aMule]] startup script):

''amule &''

== On [http://www.debian.org Debian] Woody ==

Run (as root):

''apt-get install vncserver xvncviewer flwm''

There is no support for ''~/.vnc/xstartup'' so, instead, use ''$vncStartup'' in ''.vncrc'' to determine a xstartup-script (this replaces your ''~/.xsession'' file).

For more information, read ''man vnc.conf''

For example, in a Woody/Sarge/Sid: 
Login as the user who is going to run [[aMule]] 
''mkdir ~/.vnc/'' 
Create the ''~/.vnc/xstartup'' file, with the next content 

''/usr/bin/flwm &'' 
''/usr/bin/amule &'' 
''/usr/bin/amule &''

With sone versions of [http://www.redstonesoftware.com/vnc.html vncserver], it's necessary to launch at least twice the [[aMule]]. The [http://flwm.sourceforge.net flwm] is an optional window manager.

Create the file ''~/.vncrc'' with the next content: 
Login as the user and run ''xvncviewer :1'' to create the password file and debug possible probelms (the logs are under the ''~/.vnc/'' dir

''$vncStartup = "/home/amule/.vnc/xstartup";'' 
''$geometry ="800x600";''

(replace ''/home/amule'' for the home of the user running [http://www.redstonesoftware.com/vnc.html VNC])

To show the [[aMule]] window, run:
''xvncviewer localhost:1''

If you want to autostart a [http://www.redstonesoftware.com/vnc.html VNC] session on system startup, you can put a line in ''/etc/init.d/bootmisc.sh'' like this:

''su '''username''' -c vncserver''

Replace '''username''' with the name of the user that you want to launch vnc. (Added by '''ghent''')

== To start [[aMuleWeb]] also at startup: ==

This is probably the most unelegant way to do this, but it seems to work.

The problem is that you have to supply user input when starting [[aMuleWeb]] (the password).

You can circumvent this with supplying a password with the ''-pw'' option: ''amuleweb -pw ""'' (this is for no password, you have to remove the [http://www.ietf.org/rfc/rfc1321.txt MD5 sum] from the ''ECPassword'' entry in your ''~/.eMule'' file for this to work).

Now [[aMuleWeb]] starts without any user input, but unfortunately it wouldn't work when we would just add it to the xstartup-file, because [[aMule]] needs a few seconds more to start up.

Therefor we have to start [[aMuleWeb]] a few seconds after [[aMule]].

To achieve this, we add a line similar to this one:

''/bin/sh /home/aMule/amuleweb-start.sh &''

to the xstartup-file.

And in the home-directory, we create a file called ''amuleweb-start.sh'', with the following content:

#! /bin/sh
sleep 30;
/usr/bin/amuleweb -pw "";

That's all.

Like I said, probably extremely amateurish, but it should work...

== [http://www.mandrake.com Mandrake] 10.0 ==

The script from [[User:Frankk|Frankk]] is the one I use, but you can customize the size of the [http://www.redstonesoftware.com/vnc.html VNC] server :
''/bin/su - $theUser -c "PATH=/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin /usr/bin/vncserver :$theScreen"''

add

''/bin/su - $theUser -c "PATH=/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin /usr/bin/vncserver :$theScreen -geometry 1240x980"''

or whatever value.

Personaly, I use as xstartup script ([http://www.icewm.org iceWM] is really nice and so CPU-cheap) :

''#!/bin/sh'' 
''starticewm&'' 
''amule''

To start [http://www.redstonesoftware.com/vnc.html VNC] at startup, I called the previous script ''/etc/init.d/amulevnc'' and chmod to 744 (''chmod 744 /etc/init.d/amulevnc'' as root). 
Instead of modifying ''/etc/rc.d/rc.vnc'', I added links in the corresponding ''/etc/rc$RUNLEVEL.d'' directories. 
It's quite simple to understand how it works: 
Each directory represents a runlevel, and contains links to the scripts from ''/etc/init.d'' which need to be run/stop. 
For instance, the link ''/etc/rc5.d/S55sshd'' to ''/etc/init.d/sshd'' will start ''sshd'' on runlevel 5,
whereas ''/etc/rc6.d/K25sshd'' linked to ''/etc/init.d/sshd'' will stop it in runlevel 6. 
You get it? Links starting with 'KXX' will stop a service, and those starting with 'SXX' will start them. The number will define the order.

So to run [http://www.redstonesoftware.com/vnc.html VNC] on startup, just do (as root :-) )
''re>ln -s /etc/init.d/amulevnc /etc/rc5.d/S99amule''
''ln -s /etc/init.d/amulevnc /etc/rc6.d/K02amule''
and you're all set!

PS: This method should work on systems other than [http://www.mandrake.com Mandrake], give it a test.

Questions & comments: ''air_1 '''at''' libertysurtf.fr''

== [http://www.gentoo.org Gentoo] ==

For [http://www.gentoo.org Gentoo]'ers follow these steps:

=== Install [http://www.realvnc.com VNC] ===

This is a how to for a server with no X window manager at all. I only run web and mail services, and o course, aMule. Adapt to you're sictuation.
I use [http://www.tightvnc.com TightVNC], but should also work with other [http://www.realvnc.com VNC]'s.

emerge tightvnc

=== Configuring [http://www.realvnc.com VNC] ===

==== Server Config ====

To configure the [http://www.realvnc.com VNC] server, execute:

vncserver :1

You'll be asked to answer some questions, such as password, answer accordingly. After you can kill it:

vncserver -kill :1

==== Programs to Start ====

Now let's config what should be started with this [http://www.realvnc.com VNC] session:
edit ~/.vnc/xstartup

vi ~/.vnc/xstartup

You should see something like:

#!/bin/sh

xrdb $HOME/.Xresources
xsetroot -solid grey
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
twm &

[http://www.x.org xterm] is a console, and [http://www.x.org twm] is the window manager. I use http://fluxbox.sourceforge.net fluxbox], and don't want no terminal, just [[aMule]] so, it's like this:

#!/bin/sh

xrdb $HOME/.Xresources
xsetroot -solid grey
amule &
fluxbox &

=== Starting VNC at boot ===

Since I won't be starting no Window Manager at boot, but still want aMule started with the user interface(you could just run the *amuled*), I'll need an init script:

vi /etc/init.d/vncserver

Make it look like:

#!/sbin/runscript
# Copyright 1999-2005 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $

depend() {
need net
}

checkconfig() {
ebegin "Check config"
#PATH="$PATH:/usr/X11R6/bin/"

# The Username that will run VNC
USER="vampas"

# The display that VNC will use
DISPLAY="1"

# The Desktop geometry to use.
#GEOMETRY="<WIDTH>x<HEIGHT>"
#GEOMETRY="1280x1024"
GEOMETRY="1024x780"

# The name that the VNC Desktop will have.
NAME="aMule"
}

start() {
checkconfig
ebegin "Starting vncserver for user ${USER} on localhost:${DISPLAY}"
su ${USER} -c "/usr/bin/vncserver -name ${NAME} -geometry ${GEOMETRY} :${DISPLAY}"
eend $?
}

stop() {
checkconfig
ebegin "Stoping vncserver for user ${USER} on localhost:${DISPLAY}"
su ${USER} -c "/usr/bin/vncserver -kill :${DISPLAY}"
eend $?
}

restart() {
stop
start
}

Make it executable:

chmod +x /etc/init.d/vncserver

Now add it to boot:

rc-update add vncserver default

And you should be ready to go, if not <ufs AT sapo DOT pt>.

--[[User:PedroAlgarvio|PedroAlgarvio]] 06:10, 2 May 2005 (CEST)

HowTo compile on Win32 with MinGW

2005-05-02T16:25:45Z

147.83.41.10:

<center><h2>Originally by '''Madcat'''</h2></center>

This wiki page only supports the lastest [[aMule_CVS|CVS]] version of [[aMule]].

== List of things you need to compile [[aMule]] ==

'''Note:''' Some of these require manually moving includes/libs into the right directories.

[http://www.microsoft.com/windows Windows] port of [http://gcc.gnu.org GNU C compiler] -> [http://prdownloads.sf.net/mingw/MinGW-3.1.0-1.exe?download Download]

Minimal [http://www.gnu.org GNU] shell for [http://www.microsoft.com/windows Windows] -> [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download Download]

Developer toolkit for [http://www.mingw.org/msys.shtml MSys] (for [http://www.gnu.org/software/cvs CVS] & co) -> [http://prdownloads.sf.net/mingw/msysDTK-1.0.1.exe?download Download]

[http://www.gnu.org/software/libiconv LibIConv] (required by [http://www.gnu.org/software/gettext gettext]) ->
[http://prdownloads.sf.net/mingw/libiconv-1.8.0-2003.02.01-1.exe?download Download]

[http://www.gnu.org/software/gettext GetText] (for [http://www.gnu.org/software/gettext po files], [http://www.gnu.org/software/automake/automake.html autogen.sh], etc) ->
[http://prdownloads.sf.net/mingw/gettext-0.11.5-2003.02.01-1.exe?download Download]

[http://www.zlib.org zlib] compression library ->
[http://www.zlib.net/zlib-1.2.2.tar.gz Download]

[http://www.microsoft.com/windows Windows] port of [[wxWidgets]] library ->
[http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.6.0.zip Download]

== Common guidelines, issues, solutions ==

When compiling [[wxWidgets]], you should make use of the following configure flags:
''--disable-shared --without-checklistbox''

Link statically against ''[http://www.zlib.org zlib]'' to avoid distributing extranous DLLs (and generally make life simpler).

== Compilation ==

The compilation itself it's actually just a matter of following the usual compilation way: ''./configure && make''

However, [http://www.zlib.org zlib] detection might fail. If that's the case, you need to add ''--with-zlib=/local/'' to yout configure flags.

== Compiling with [http://www.parinya.ca/mingwstudio.html MinGW Studio] ==

'''NOTE:''' The compilation with [http://www.parinya.ca/mingwstudio.html MinGW Studio] is deprecated right now and generally doesn't work at the moment. Might work again in the future.

Since the 2004/07/17, you can find in [http://www.gnu.org/software/cvs CVS] the file ''amule.msp'' which is the project file relative to the [http://www.parinya.ca/mingwstudio.html MinGW Studio] IDE ([http://www.gnu.org/philosophy/free-sw.html Free] and under [http://www.gnu.org/copyleft/gpl.html GPL] at http://www.parinya.ca/ and shipped with precompiled [[wxWidgets|wxMSW]]).

Install [http://www.parinya.ca/mingwstudio.html MinGW Studio], add [http://www.zlib.org Zlib] and [http://curl.haxx.se Curl] compiled libs in The [http://www.parinya.ca/mingwstudio.html MinGW Studio] tree.

Then, open ''amule.msp'' with [http://www.parinya.ca/mingwstudio.html MinGW Studio], press '''F7''', and [[aMule]] "should" be compiled :)

Yes, I know, "compile" is not the same as "work" ... But it is a great begining

Firewall

2005-01-09T12:41:31Z

147.83.41.10:

'''NOTE:''' If you run [http://www.suse.com SuSE Linux], try [[Firewall_SuSE|this HowTo]] first.

If you set TCP port in [[aMule]] to XX and UDP port to YY then you have to set your firewall like this:

''iptables -A INPUT -p tcp --dport '''XX''' -j ACCEPT'' 
''iptables -A INPUT -p udp --dport '''XX+3''' -j ACCEPT'' 
''iptables -A INPUT -p udp --dport '''YY''' -j ACCEPT'' 

If you want to setup [[aMule]] behind a NAT gateway, you should add these lines to your [http://www.netfilter.org iptables] configuration script, on the gateway :

''EXTIF'' is your external interface

''EMULEPORT='''4662''''' 
''EMULEUDP='''4672''''' 
''EMULEUDP2=`expr $EMULEPORT + 3`'' 
''EMULEHOST='''10.0.0.2''''' 
''iptables -t nat -A PREROUTING -i $EXTIF -p tcp --destination-port $EMULEPORT -j DNAT --to-destination $EMULEHOST:$EMULEPORT'' 
''iptables -t nat -A PREROUTING -i $EXTIF -p udp --destination-port $EMULEUDP -j DNAT --to-destination $EMULEHOST:$EMULEUDP'' 
''iptables -t nat -A PREROUTING -i $EXTIF -p udp --destination-port $EMULEUDP2 -j DNAT --to-destination $EMULEHOST:$EMULEUDP2'' 

You also should make sure that your FORWARD-string is set up correctly. Usually, you will have an entry like this:

''iptables -A FORWARD -i $EXTIF -o $INTIF -d $EMULEHOST -m state --state ESTABLISHED,RELATED -j ACCEPT''

where ''INTIF'' is your internal interface and ''EMULEHOST'' is the host running the [[FAQ_eD2k-Kademlia#What_is_ED2K?|eD2k]] [[server]] on your internal network.

This will prevent new connections. So, you should allow all forwarding for [[aMule]]-related ports:

''iptables -A FORWARD -i $EXTIF -o $INTIF -p tcp --dport $EMULEPORT -d $EMULEHOST -j ACCEPT'' 
''iptables -A FORWARD -i $EXTIF -o $INTIF -p udp --dport $EMULEUDP -d $EMULEHOST -j ACCEPT'' 
''iptables -A FORWARD -i $EXTIF -o $INTIF -p udp --dport $EMULEUDP2 -d $EMULEHOST -j ACCEPT''