1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

An amule guide? maybe :P

Discussion in 'Cisco/Linksys Network Storage Devices' started by GnFi, Aug 31, 2010.

  1. GnFi

    GnFi Networkin' Nut Member

    An amule guide? maybe :p - INTRO

    My main goal is to have a “how to†on the amule configuration file, the tools we will use to manage this and some minor info about them and also a different way to alter the amule.conf file to our computer, some steps you should do to be able to share the downloads of amule within your ftp
    and finally a brief explain of some of the lines in amule.conf file that I can understand and you will need to make it work normally.
    Later I will alter the web interface a little bit so it will match the linksysinfo.org site here (mainly amule web interface banner and colors of it).
    I will also provide a prefixed amule.conf file for you that will only need md5 hash generated password (I will also explain how to generate the md5 hash inside busybox, but you can always use an online md5 hash generator for that). Remember that this file will use the default ports to connect.

    A big sorry for my English but it is not my mother language and I do not use it on a daily basis

    This guide is divided in 3 sections.

    1st section is the creation of the 2 folders amule will use:
    One folder for the temporary data (downloads that are not finished yet)
    and a second one for the finished downloads
    In this same section I will try to explain why in my setup i choose these folders to be inside /harddisk/volume_X/data/ (X stands a volume your harddisks are mounted on)

    In the 2nd section of this UFS200 Amule “how toâ€, we will investigate why it is so important to alter amule.conf file after we have a backup copy of it.
    I will also explain some things for the integrated vi editor the busybox installation the UFS200 has.
    In case you are not familiar with vi editor (as I am. I just find it a ***** and I always end up making mistakes) I will explain how to copy the amule configuration file to a shared folder of NAS200 harddisks (I have chosen /harddisk/volume_3/data/public/ for that purpose so that I am sure you can all see it),
    and what tool to use to edit it, save it and finally how to copy it back to the right folder so that amule can see it and use it.

    In the 3rd section I will try to explain what lines you will have to alter in amule.conf to make it work and also the use of every other line in this conf file. I will also explain how to generate an md5 hash from your password from inside busybox or from an online tool.

    What you need to start:
    As a start I will take for granted that you have UFS200 running.
    If you don't, there are other threads that will help you to get to this point. I don't have the knowledge to do that.
    2nd is to have access to NAS200 default web interface and the knowledge to add or to share some folders
    Since you have it up and running we are ready to go. All the tools we need are located into busybox (except Notepad++ in the case we choose to alter the amule.conf file with a different editor)
    I am not going to explain how to connect to busybox via ssh, how to install Jac4 (required to install UFS200), or how to install UFS200. I will also not explain how to share folders with NAS200 in your network and via FTP Protocol (use Linksys manual for that).
    Also I will not explain how to open ports to your router. You can either look into your manual and learn how to do that or use http://portforward.com/english/routers/port_forwarding/routerindex.htm site for that if it has your router listed
    I will not answer to questions like my amule is slow and thinks like that.

    Let’s start.....
  2. GnFi

    GnFi Networkin' Nut Member

    An amule guide? maybe :p - HOW TO

    Section 1 - Creating Amule Temporary and Finished downloads folders

    Amule and as all mule clients use 2 folders to sort its downloads.
    1 folder for files that are still being downloaded and 1 more for finished downloads. Until a downloaded file gets to 100% it stays in the temporary folder, after that its hashed chunks get in place and the file moves to finished download folder.
    Amule will use by default 2 folders that are inside /home/amuled/.aMule/ (/home/amuled/.aMule/Incoming &/home/amuled/.aMule/Temp)
    My main problem was that I couldn't find a way to share those folders in my FTP or Windows network. There might be a way but I wasn't going to loose time on that.
    What I did was to create 2 folders in the NAS200 harddisks. We will call Amule the 1st (this is the finished download folder) folder and AmuleTemp 2nd (the temporary and not finished download folder).
    After that I logged in NAS200 default web interface, in Shared Folders section and shared the 1st folder named Amule with everyone I wanted to be able to see it.
    I myself also shared the second with read/write access since I usually play with unfinished downloads. Feel free to do as you want with this folder.
    We will bind those 2 folders in the 3rd section of this “how to” later with amule.conf file.
    Feel free to rename those 2 folder and place them anywhere you want. You will also have to change the bindings at the amule.conf file exactly as you created them.

    Section 2 - Making a backup of amule.conf file, Brief explain of vi editor and a way to edit the file outside NAS200

    • Part 1: making backup of amule.conf

    This is a quite important step since making mistakes while altering a file with vi editor is not a hard thing. Also good if we want to revert back to default.
    Amule has a console option to revert configuration file back to normal but unfortunately it does not revert the right file. It reverts root amule config back to default.
    That does not work since we will not run amule as root so we do not use that configuration file (the emule root config file is in .aMule/ while running amule as a user uses the config file in /home/amuled/.aMule/).
    I really suggest making a backup to it. Even if you do not and have a problem then you can copy the file from .aMule/ to /home/amuled/.aMule/ and start editing it again
    I take as granted that you have access of UFS200 busybox. If not check UFS200 thread....
    It is also possible that if you erase amule.conf file and run amule a new conf file to be automatically created. I am not sure if amule works that way

    So go on and log in via ssh.
    Since you can now see the console (i see "root@GnF_NAS200 ~#" you will see something similar) we are ready to move on.
    We need a copy of /home/amuled/.aMule/amule.conf
    Easy to do it by executing this code
    cp /home/amuled/.aMule/amule.conf /home/amuled/.aMule/amuleback.conf
    We have just saved the amule.conf file located under /home/amuled/.aMule/ in the same directory under the name amuleback.conf

    In case you do not want to use vi editor (like me since i damaged the file more than once in vi) and want to do it in your computer with an editor like notepad++ do the following after making the backup

    cp /home/amuled/.aMule/amule.conf /harddisk/volume_X/data/public (note that X stands for the number your volumes are mounted on)
    We have just copied the amule.conf file to the public folder of the NAS200. I take for granted that you have access to this folder from windows network or via FTP.
    Download the file on your desktop and open it with notepad++ (you can download a free copy of notepad++ at http://notepad-plus-plus.org/)

    Now that we have a backup, on to part 2.​

    • Part 2: VI Editor

    I will just explain how to open a file (in our case amule.conf file) enter insert mode of VI Editor, Exit insert mode and then save the file from command mode and exit.

    (a small part from a vi guide taken from http://www.eng.hawaii.edu/Tutor/vi.html) follow the link to learn more about vi. There are much more vi guides on the net, I just chose that one. If www.eng.hawaii.edu have any problem copying text here from the guide they have, please let me know and I will remove it as soon as possible.
    VI has two modes:
    The first thing most users learn about the VI editor is that it has two modes: command and insert. The command mode allows the entry of commands to manipulate text. These commands are usually one or two characters long, and can be entered with a few keystrokes. The insert mode puts anything typed on the keyboard into the current file.

    VI starts out in command mode. There are several commands that put the VI editor into insert mode. The most commonly used commands to get into insert mode are a and i. Once you are in insert mode, you get out of it by hitting the escape key. If your terminal does not have an escape key, ^[ should work (control-[). You can hit escape two times in a row and VI would definitely be in command mode. Hitting escape while you are already in command mode doesn't take the editor out of command mode. It may beep to tell you that you are already in that mode.

    So when you first open any file, vi is in command mode. You cannot alter anything on the file.
    To enter insert mode press "i" once (if you hit it twice you will write an i character at the file so just don't) and on the lower left of your screen you will see the inserted word.
    Now that you are in insert mode you can make all the changes you want. Navigate with arrow keys (up, down, left, right), Delete with backspace (or back if your keyboard has it that way)

    After you make all the changes you need you have to exit insert mode. Do this by pressing ESC (or Escape if your keyboard has it that way)
    To save the file and exit the program just hold shift down and press twice z (you will give the command ZZ like that. Also works without shift and caps lock on I think)

    In case you chose to edit the file in your computer with notepad++ then transfer the altered file back to the public folder of NAS200, overwriting the old one.
    Then from your ssh console give this command:
    cp /harddisk/volume_X/data/public/amule.conf /home/amuled/.aMule/
    This command will take the altered amule.conf file from public folder of your NAS200 hard disks and place it in /home/amuled/.aMule/. It will automatically overwrite the old one without asking you​

    Section 3 - Altering amule.conf file & generating md5 hash values for the passwords amule needs

    Well this is it. Quite possible that all the above sections look useless to you but these are the steps I followed and I thought they should be here for users that are not that experienced, like me.

    In the amule.conf file you can alter a lot of things. I suggest you alter only things you know what they do and why you want to do it.
    You can alter the ports amule uses to connect (the same ones you have to port forward in your router), the port the web interface works on (you will have to port forward that, too, if you need to have access it through the internet and not only from within your lan), maximum speeds allowed to amule for uploading and downloading and a lot more things
    Below I will provide all the lines of amule.conf.
    Next to each line there will be a brief explanation. Any line with no explain is out of my knowledge and everyone is free to contribute.
    Any line in bold will have to be altered for amule to work normally (the lines that truly need to be altered are about 10)
    I suggest you close ipfiltering since it uses a lot of cpu cycles and NAS200 is very cpu limited.

    AppVersion=2.2.4		                        [COLOR="Red"]amule version - no need to change it[/COLOR]
    Nick=GnF			                        [COLOR="Red"]your nickname that other clients you connect on see - free to change it as i have[/COLOR]
    VerboseDebug=0		                         [COLOR="Red"]Possibly for debug?[/COLOR]
    MaxUpload=35			                 [COLOR="Red"]your max upload speed - fix this according to your internet line or what ever you want[/COLOR]
    MaxDownload=850		                 [COLOR="Red"]your max download speed - fix this according to your internet line or what ever you want[/COLOR]
    [SIZE="5"][B]Port=4662	                                 [COLOR="Red"]TCP port emule use to connect. You must port forward this port - feel free to change it and also don't forget to port forward the change you did[/B][/COLOR]
    [B]UDPPort=4672                                   [COLOR="Red"]UDP port emule use to connect. You must port forward this port - feel free to change it and also don't forget to port forward the change you did[/COLOR][/B][/SIZE]
    UDPDisable=0			                  [COLOR="Red"]Altering this to 1 disables UDP - do not change it[/COLOR]
    Autoconnect=1			                  [COLOR="Red"]Altering this to 0 disables Autoconnect. If you do amule wont autoconnect at startup and you will have to manually connect[/COLOR]
    MaxSourcesPerFile=300	                          [COLOR="Red"]Max known sources per file - keep it somewhere between 300 and 800, Get it high if you download a few but very popular files. Lower if the opposite exists   [/COLOR]
    MaxConnections=500		                  [COLOR="Red"]Maximum connections amule is allowed to have. They also include waiting connections. I prefer this around 200-300[/COLOR]
    MaxConnectionsPerFiveSeconds=20           [COLOR="Red"]Maximum connections per 5 sec. If you want to have a better line while amule works, for internet browsing keep this around 12 to 15. Less might do a better job. Remember that it will affect your download speed as you get it lower[/COLOR]
    RemoveDeadServer=1		                  [COLOR="Red"]Removes servers amule try to connect and they do not reply. Altering it to 0 disables it and dead servers stay on the list[/COLOR]
    DeadServerRetry=3		                  [COLOR="Red"]How many times to try reconnection on a dead server before it flags it as dead and removal happens[/COLOR]
    Reconnect=1			                  [COLOR="Red"]If a connection to a server die then emule try to reconnect either to the same server or another one. Altering this to 0 disables that and after amule loose connection it does nothing and stay disconnected [/COLOR]
    Scoresystem=1			                  [COLOR="Red"]Generates a file with a valid score system (I am not sure if it scores you or others that download from you)[/COLOR]
    [B][SIZE="5"][B]Serverlist=0                     [COLOR="Red"]O= does not auto update server met for the supplied url. 1= It does auto update server.met[/COLOR][/B][/SIZE][/B]
    AddServerListFromServer=0	                  [COLOR="Red"]When amule connects on a server it downloads a list of possibly valid servers [/COLOR]
    AddServerListFromClient=0	                  [COLOR="Red"]When amule connects on a client it downloads a list of possibly valid servers [/COLOR]
    SafeServerConnect=0		                  [COLOR="Red"]0= emules asks 2 servers the same time to connect, 1= emule asks 1 server to connect and waits for an answer, if there is none or a refusal, it goes to the next[/COLOR]
    AutoConnectStaticOnly=0	                  [COLOR="Red"]static list of servers are servers that you manually add to static. 0= autoconnect to every server in your list, 1= autoconnect only to static servers (if you have no static? :P)[/COLOR]
    UPnPEnabled=0		                          [COLOR="Red"]UPnP auto opens the TCP and UDP ports to the router. The router must support UPnP. Even if so, there are a lot of possible limitations that prevent it to work. Prefer manual port forwarding[/COLOR]
    UPnPTCPPort=50000		                  [COLOR="Red"]The port that amule client uses to negotiate the UPnP protocol with the router? Possibly. I am not sure[/COLOR]
    ConnectToKad=1		                          [COLOR="Red"]0= does not connect to Kademlia network (serverless), 1= Connects and uses Kademlia network (serverless)[/COLOR]
    ConnectToED2K=1		                  [COLOR="Red"]0= does not connect to ED2K network (with server), 1= Connects and uses ED2K network (with server)[/COLOR]
    [SIZE="5"][B]TempDir=/harddisk/volume_X/data/AmuleTemp	[COLOR="Red"]the directory for our temporary downloaded files. Remember the 2 folders we created before? Here we are[/B][/COLOR]
    [B]IncomingDir=/harddisk/volume_X/data/Amule		[COLOR="Red"]the directory for our Finished downloaded files. Remember the 2 folders we created before? Here we are[/B][/COLOR][/SIZE]
    ICH=1				                  [COLOR="Red"]Intelligent Corruption Handling. 0= disabled, 1 = enabled[/COLOR]
    AICHTrust=0			                  [COLOR="Red"]Trusting the Root Hash of ICH???? Possible. Check amule or even emule site for more info [/COLOR]
    CheckDiskspace=1		                  [COLOR="Red"]Checks for available free disk space and reports if it is less that the min you have asked it to check. 0=disabled 1=enabled[/COLOR]
    MinFreeDiskSpace=1		                  [COLOR="Red"]Minimum free disk space that it will start to notify you with a message[/COLOR]
    AddNewFilesPaused=0		                  [COLOR="Red"]When you add a new file for download it will stay paused. 0=disabled 1=enabled (1= you will have to manually start it)[/COLOR]
    ManualHighPrio=0		                          [COLOR="Red"]Every new file starts at high priority? I am not sure[/COLOR]
    FullChunkTransfers=1		                  [COLOR="Red"]When you download a file with amule the file gets divided into Chunks. This option makes sure that a chunk won't stop if it is not full. 0=disabled 1=enabled[/COLOR]
    StartNextFile=0		                          [COLOR="Red"]When a file gets completed amule automatically starts one of the paused files 0=disabled 1=enabled[/COLOR]
    StartNextFileSameCat=0	                  [COLOR="Red"]When amule automatically starts the next paused file it will prefer one from the same category if there is one. 0=disabled 1=enabled[/COLOR]
    AllocateFullFile=0		                          [COLOR="Red"]Lets say you add a file for download that is 100 Mbyte. Having this enabled will allocate all the space on the disk before it even completes the file. 0=disabled 1=enabled[/COLOR]
    [SIZE="5"][B]OSDirectory=/home/amuled/.aMule/	  [COLOR="Red"]Directory with the client in it. Change it to the right one if it is different (that is /home/amuled/.aMule[/COLOR][/B][/SIZE]        
    OnlineSignature=0		                  [COLOR="Red"]Right now all it does is to create a file thatyou can link on a forum signature lets say. 0=disabled 1=enable[/COLOR]
    OnlineSignatureUpdate=5	                  [COLOR="Red"]How often the client updates the online signature file[/COLOR]
    EnableTrayIcon=0		                          [COLOR="Red"]Tray icon (does NAS200 have a tray? :PPP) 0=disabled 1=enable[/COLOR]
    MinToTray=0			                  [COLOR="Red"]Minimize to tray :P 0=disabled 1=enable[/COLOR]
    ConfirmExit=1			                  [COLOR="Red"]Confirmation dialog when you try to exit (on the desktop of NAS200? :P) 0=disabled 1=enable[/COLOR]
    StartupMinimized=0		                  [COLOR="Red"]Startup minimized (Damn, this is fun...On NAS200 taskbar maybe? :P) 0=disabled 1=enable[/COLOR]
    ToolTipDelay=1			                   [COLOR="Red"]Delay after you pause your mouse on something before the tooltip appears [/COLOR]
    ShowOverhead=0		                           [COLOR="Red"]Shows overhead data speed except your download speed. I am not sure if it shows the numbers combined. Also does it work on web interface?[/COLOR]
    ShowInfoOnCatTabs=1		                   [COLOR="Red"]Shows info on category tabs[/COLOR] 0=disabled 1=enable
    ShowRatesOnTitle=0		                   [COLOR="Red"]Shows download and upload speed on window title (:P NAS200 again hehe) 0=disabled 1=enable[/COLOR]
    VerticalToolbar=0		                           [COLOR="Red"]Vertical toolbar (what? where? Damn i am on a NAS200 :P) 0=disabled 1=enable[/COLOR]
    VideoPlayer=			                   [COLOR="Red"]Default video player to open a file from within amule gui (:P) 0=disabled 1=enable[/COLOR]
    StatGraphsInterval=3		                   [COLOR="Red"]Update interval for the statistics graphs[/COLOR]
    statsInterval=30		                           [COLOR="Red"]Update interval for the statistics[/COLOR]
    DownloadCapacity=1000	                   [COLOR="Red"]The download speed that your router/modem synchronizes. Has nothing to do with Limits. We set this limit on the start of this file. This is just for graphs, and possibly for limits you can set from web interface[/COLOR]
    UploadCapacity=60		                   [COLOR="Red"]The upload speed that your router/modem synchronizes. Has nothing to do with Limits. We set this limit on the start of this file. This is just for graphs, and possibly for limits you can set from web interface[/COLOR]
    StatsAverageMinutes=60	                   [COLOR="Red"]Average download speed in X minutes. It’s just for stat graphs   [/COLOR]
    VariousStatisticsMaxValue=100		   [COLOR="Red"]Max connections for stats graphs. Nothing to do with maximum connections. We set it up that earlier[/COLOR]
    SeeShare=2			                  [COLOR="Red"]This is who can see our share files. Unfortunately i don't know what numbers stands for. Possibly : 0= none 1=friends 2=all? I really don't know[/COLOR]
    FilterLanIPs=1			                   [COLOR="Red"]Filters the lan ip. Filtering is done according to ipfilter.dat file.  0=disabled 1=enable[/COLOR]
    ParanoidFiltering=1		                   [COLOR="Red"]Paranoid Filtering? Don't know what it does[/COLOR]
    IPFilterAutoLoad=1		                   [COLOR="Red"]Auto loads the ipfilter.dat file from an ip address. There are a lot of sites out there with ipfilter files[/COLOR]
    IPFilterURL=			                           [COLOR="Red"]The url address from where the auto load of the ipfilter.dat file will be done[/COLOR]
    FilterLevel=127			                   [COLOR="Red"]The amount of the filter that will be done. How much aggressive? Not quite sure[/COLOR]
    FilterMessages=1		                           [COLOR="Red"]Filters messages send to your client via other clients. Filtering is done via keywords. 0=disabled 1=enable[/COLOR]
    FilterAllMessages=0		                   [COLOR="Red"]Filters all the messages. 0=disabled 1=enable[/COLOR]
    MessagesFromFriendsOnly=0		           [COLOR="Red"]Accept messages from friends only. 0=disabled 1=enable[/COLOR]
    MessageFromValidSourcesOnly=1	           [COLOR="Red"]Accept a message only if it comes from a valid source. 0=disabled 1=enable[/COLOR]
    FilterWordMessages=0		                   [COLOR="Red"]Filter messages according to words. 0=disabled 1=enable                  [/COLOR]
    MessageFilter=			                   [COLOR="Red"]You add here any word or phrase you want to filter. Separate words and phrases with |[/COLOR]
    FilterComments=0		                           [COLOR="Red"]Filter comments according to words. 0=disabled 1=enable[/COLOR]
    CommentFilter=		                           [COLOR="Red"]You add here any word or phrase you want to filter. Separate words and phrases with |[/COLOR]
    ShareHiddenFiles=0		                   [COLOR="Red"]Shares hidden files. 0=disabled 1=enable[/COLOR]
    AutoSortDownloads=0		                   [COLOR="Red"]Automatic sorting of the downloads. 0=disabled 1=enable[/COLOR]
    NewVersionCheck=0		                   [COLOR="Red"]Checks for new versions at startup. 0=disabled 1=enable[/COLOR]
    Language=			                           [COLOR="Red"]Language to use. I think null is the default that stands for English. To use another language you will have to create its file or download it.[/COLOR]
    DateTimeFormat=%A, %x, %X
    DropSlowSources=0		                   [COLOR="Red"] Drops sources that are slow. 0=disabled 1=enable[/COLOR]
    KadNodesUrl=http://emule-inside.net/nodes.dat	            [COLOR="Red"]url for downloading nodes.dat file for known nodes[/COLOR]
    [SIZE="5"][B]Ed2kServersUrl=http://gruk.org/server.met.gz           [COLOR="Red"]url for updating the server.met file. This is how your client will always know available and valid servers. Check at the end of this guide for a solution to a problem i had with auto-update. You can enter here any url you want to use and has a server.met file to upload to you[/B][/COLOR][/SIZE]
    ProxyEnableProxy=0		                                    [COLOR="Red"]enables proxy. 0=disabled 1=enable[/COLOR]
    ProxyType=0			                                    [COLOR="Red"]need research on what this stands for[/COLOR]
    ProxyName=			                                    [COLOR="Red"]name of the proxy[/COLOR]
    ProxyPort=1080		                                            [COLOR="Red"]proxy port[/COLOR]
    ProxyEnablePassword=0	                                            [COLOR="Red"]enables amule client to send a password to a proxy that needs one. 0=disabled 1=enable[/COLOR]
    ProxyUser			                                            [COLOR="Red"]your proxy username[/COLOR]
    ProxyPassword=		                                            [COLOR="Red"]your proxy password (needs a password translated to md5 hash i will explain at the end how to obtain one)[/COLOR]
    [SIZE="5"][B]AcceptExternalConnections=1		                    [COLOR="Red"] Be sure it is 1. Accept external connections. 0=disabled 1=enable[/B][/COLOR][/SIZE]
    ECPort=4712			                                     [COLOR="Red"]External Connect Port. Still researching it..... I did try to change it and i couldn't connect to a server? Don't touch it, it works fine like that[/COLOR]
    [SIZE="5"][B]ECPassword=			                                     [COLOR="Red"]External Connect password (needs a password translated to md5 hash I will explain at the end how to obtain one)[/B][/COLOR][/SIZE]
    UPnPECEnabled=0		                                             [COLOR="Red"]External connect UPnP. 0=disabled 1=enable. Also remember what i said before about UPnP problems and limitations[/COLOR]
    IpFilterClients=1 		                                             [COLOR="Red"]Filters clients ip addresses according to ipfilter.dat (cpu intensive)[/COLOR]
    IpFilterServers=1 		                                             [COLOR="Red"]Filters server ip addresses according to ipfilter.dat (cpu intensive)[/COLOR]
    [SIZE="5"][B]Enabled=0    			                                     [COLOR="Red"]Enables Web Interface 0=disabled 1=enable. How else to control your amule? Just enable it[/COLOR][/B]
    [B]Password=   			                                     [COLOR="Red"]Web Interface password (needs a password translated to md5 hash I will explain at the end how to obtain one)[/COLOR][/B][/SIZE]
    PasswordLow=  		                                             [COLOR="Red"]Web Interface Low Rights user password. A user with lower right. Cannot restart etc. (needs a password translated to md5 hash i will explain at the end how to obtain one)[/COLOR]
    [SIZE="5"][B]Port=4711			                                      [COLOR="Red"]Web interface manual port that you must port forward only if you need access to the web interface via the internet. You can also just use the default one. Feel free to change it and also port forward the new one[/COLOR][/B][/SIZE]          
    WebUPnPTCPPort=50001	                                       [COLOR="Red"]With Web Interface UPnP enabled the client will ask the router to open this port. Feel free to change it. Remember UPnP does not always work. Prefer Manual port forwarding[/COLOR]
    UPnPWebServerEnabled=0 		                              [COLOR="Red"] Enables UPnP web interface port[/COLOR]
    UseGzip=1			                                              [COLOR="Red"]Uses Gzip compression on the web interface. I think this is a bit cpu depended. What happens on a slow cpu like the NAS200 has? I am not sure tho.[/COLOR]
    UseLowRightsUser=0		                                      [COLOR="Red"]Enables low rights user password. 0=disabled 1=enable[/COLOR]
    PageRefreshTime=120		                                      [COLOR="Red"]Web interface refresh in seconds.[/COLOR]
    [SIZE="5"][B]Template=chicane 		                                      [COLOR="Red"]Web interface Template. There are 4 already installed and they have different looks, so choose the one you like more. 
    Your options to change them are : chicane , default , litoral , php-default[/COLOR][/B][/SIZE]
    Cat_ED2k\ Client=0
    Cat_Local\ Client\ Protocol=0
    Cat_Remote\ Client\ Protocol=0
    Cat_Packet\ Parsing\ Errors=0
    Cat_Client\ Kademlia\ UDP=0
    Cat_Kademlia\ Search=0
    Cat_Kademlia\ Routing=0
    Cat_Kademlia\ Indexing=0
    Cat_Kademlia\ Main\ Thread=0
    Cat_Kademlia\ Preferences=0
    Cat_Universal\ Plug\ and\ Play=0
    Cat_Kademlia\ UDP\ Firewall\ Tester=0
    Cat_Kademlia\ Packet\ Tracking=0
    Cat_Kademlia\ Entry\ Tracking=0

    CREATING md5 Hash

    Last thing........ md5 hash
    As I mentioned above, you cannot enter passwords directly into amule.conf. You have to convert them to md5 hash and use that hash in the place you want to enter the code.
    You can generate the hash from a lot of online hash generators, or self generate it inside busybox of UFS200.
    You can do it by typing this command in your console.

    echo -n "whateverpasswordyouwant" | md5sum | cut -d " " -f 1

    The output of this command is an md5 hash generated from everything inside the " "

    START and STOP of amule

    You can start amule with the command

    /etc/rc.d/rc.amuled start

    and you will stop it with

    /etc/rc.d/rc.amuled stop (amule has a process that automatically restarts amule process if that fails. So by killing the amule process and amule web interface process does not work. They will restart automatically.)

    AUTOSTART amule when NAS200 boot

    In case you want to autostart amule (and i agree with jackito that you shouldn't since it is quite heavy for NAS200 to run all the time) you will have to edit 2 files in /etc/rc.d/
    The first file is responsible for services that automatically start at NAS200 startup and the second one for shutting them down when NAS200 restarts or shutdown.
    To manage this process tho you will have to do the following.
    cd /etc/rc.d/
    vi rc.ufs200_services_startup
    Press "i" once to go into insert mode of vi
    Insert these 3 lines before #9 (be carefull with this). Change old #9 to #10. This is what you should end up with

    # 9- Start amule
    /bin/echo "Starting Amule..." >> /var/log/rc.ufs200_services_startup.log
    /etc/rc.d/amuled start


    Press esc twice and shift+zz to save and exit

    Now the service will autostart at NAS200 boot. Lets fix the file that shuts down the service.

    vi rc.ufs200_services_shutdown
    press "i" to enter input mode of vi
    Insert these 3 lines before #9 (be carefull with this). Change old #9 to #10. This is what you should end up with

    # 9- Stop amule
    /bin/echo "Stopping Amule..." >> /var/log/rc.ufs200_services_shutdown.log
    /etc/rc.d/rc.dctcs stop


    Anyone that has knowledge and can help, or anyone that finds errors in this guide is more than welcome to contribute.
    If you follow all the above steps, amule should work normally. If not please keep this thread clean and after opening amule, open with vi logfile (located in /home/amuled/.aMule/) and post it in a new thread in the right section of this forum. I will do my best to help you out.

    Godspeed in your amule voyage
  3. GnFi

    GnFi Networkin' Nut Member

    Small problem i had with autoupdate of server.met and a fix for it if someone has the same problem

    I Found a problem while i was trying to setup emule. My problem was with auto-update of the server list. It just didn't work. Inside logfile i could see it was trying to download the new file. But still my server list was quite old.
    To verify that i deleted every server in the list from emule web interface. After that i restarted it. And the list stayed empy.
    To fix that if it happens to you you will have to create a new file named addresses.dat in /home/amuled/.aMule/ and write inside it the web address that you will connect to download the server.met file. It seems in my case this file was missing and even if i manually entered the url in the amule.conf file, amule could't automatically create addresses.dat file. Its also possible that if you just manually create the file and leave it empty amule manages to auto update server.met file from the url you have given in the amule.conf file. I didn't try that so i cannot guarantee about it

    So on to the creation of addresses.dat file and editing it in vi
    To do that first move inside that directory by typing
    cd /home/amuled/.aMule/
    Then create the file by typing this command
    vi addresses.dat
    Vi will open with the new file. Its not saved yet.
    Inside vi editor press "i" (exactly as we did before for the amule.conf file) enter the web address that you will use to download the file (i use http://www.gruk.org/server.met you can use that also)
    press esc (or escape if your keyboard has it like that) two times to go back to command mode and finally press shift+zz two times to save and exit.
  4. GnFi

    GnFi Networkin' Nut Member

    Ready made amule.conf and addresses.dat files

    At last for those that have problems to fix amule alone i will provide a premade amule.conf file with default ports. You will still need to provide an md5 hash password.

    I will also provide addresses.dat file ready with a valid url in it for auto update of server.met for those that have problems and cannot do it alone.

    In any case you will still have to move them in /home/amuled/.aMule/ . Unfortunately i cannot do that for you.

    amule.conf link for download

    The changes i have made are quite lot in this file.
    Amule webinterface password is: nas200amule
    Amule webinterface low rights user password: nas200user
    Ports that you should port forward in your router: 4662 TCP, 4672 UDP, 4711 TCP (Those are the defaults for TCP, UDP, Web Interface i haven't change them)
    I have lowered some connection things so it will not be very aggressive with your line (that is at least with lines that are at least dl/ul=2048/384). That means you might not even notice it is working in the background and that you will be able to surf the net with no problem.
    On the other hand it won't download that fast.

    You should consider changing the password md5 hash to something yours, but thats just a recommendation.

    1.   MaxUpload=13
    2.   MaxDownload=200
    3.   TCP port is the default one Port=4662
    4.   UDP port is the default one UDPPort=4672
    5.   MaxSourcesPerFile=600
    6.   MaxConnections=150
    7.   RemoveDeadServer=0
    8.   DeadServerRetry=9
    9.   Serverlist=1
    10.   IncomingDir=/harddisk/volume_3/data/amule/    (create this folder in you nas via ftp or windows share. Keep all letters in lowercase.)
    11. TempDir=/harddisk/volume_3/data/amule/temp/ (create this subfolder in you nas via ftp or windows share. Keep all letters in lowercase.)
    12. CheckDiskspace=1
    13. MinFreeDiskSpace=200
    14. StartNextFile=1
    15. StatGraphsInterval=10
    16. statsInterval=60
    17. DownloadCapacity=900
    18. UploadCapacity=100
    19. VariousStatisticsMaxValue=200
    20. FilterLanIPs=0
    21. ParanoidFiltering=0
    22. IPFilterAutoLoad=0
    23. AcceptExternalConnections=1
    24. ECPassword=7e47fcfbacb882b959b28648a54ce130 (this is nas200amule in md5 hash)
    25. Enabled=1
    26. Password=7e47fcfbacb882b959b28648a54ce130 (this is nas200amule in md5 hash)
    27. PasswordLow=496d46e349099cbff2e96242251ff213 (this is nas200user in md5 hash)
    28. Port=4711
    29. UseGzip=0
    30. UseLowRightsUser=1
    31. PageRefreshTime=180
    32. Template=chicane
    33. FastED2KLinksHandler=0
  5. GnFi

    GnFi Networkin' Nut Member

    Troubleshooting way.....at least my way

    What you are trying to do here is forward a service via IP protocol to the outside world.

    In case you cannot reach your amule web interface i would suggest:

    1. Try to reach it with the internal IP of the nas on the port amule broadcasts. (e.g. from a computer inside your LAN

    If you can see the amule web interface from that PC it means that your configuration is right and amule broadcasts normally, so your problem is at your port forwarding in the router (blame NAT for that. You can also blame IPv4 :p)
    The solution is to either check if you have port forward the right ports, that is the same ones you used in your .conf file, or check if your router has a firewall or something that blocks you. In my country some ISP's have a firewall at the DSL line that is responsible for things like that. You can try contacting them and ask them if they have a service like that. They might call it advanced security? :p

    Another thing you can try is to look if your router has an option called DMZ (demilitarized zone). Any ip that goes into there is subject to no security from the routers firewall. Everything is allowed to go in and out to this address and from it.
    Try that only for testing. If it does work like that then check at your router again.
    No security in an equipment is not a good idea. Especially when it is a NAS with a lot of files in it. You don't want someone in it do you?

    2. In case you cannot connect to the amule web interface from a computer inside your lan using the local IP on the NAS and the port amule web interface use?
    Check if you can ping the NAS or even connect to the default linksys web interface. If you can check amule.conf again
    If you can't then check what ip the NAS has. Don't forget port forwarding at the router is done on a specific IP address. If you port forward a port on and then you restart NAS and it takes via DHCP the then the port forward is now for an equipment that is not on the same IP. I suggest you in this case to use manual IP configuration at your NAS.

    I think this covers most of the problems you can test alone and try to solve.
  6. faustf

    faustf Network Newbie Member

    hi guy some people can help me i have installe amule
    and i modify a amule.conf in this mode

    Password=number has of my password
    PasswordLow=number has of my password

    but when i start a amule not have opend port 4711 how is possible????

Share This Page