AMule Project FAQ - User contributions [en]

Firewall

2006-12-22T21:41:59Z

207.255.46.56: Add link to FAQ Why does Kademlia still say it is firewalled?

<center>'''English''' | [[Firewall-es|Español]] | [[Firewall-de|Deutsche]] </center>

== Firewalls ==

By default, firewalls and routers block incoming ports. To achieve the best results with aMule, you need to configure your firewall or router to open certain ports which aMule uses. (The port numbers are configurable in preferences). See [[FAQ eD2k-Kademlia#Which ports do I have to configure in a firewall or router to run aMule?|the FAQ]].

In particular, to be given an [[FAQ eD2k-Kademlia#What is LowID and HighID?|eD2k HighID]], port 4662 TCP must be listening (i.e. opened in your firewall and forwarded in your router). To have an optimal ED2K experience, two more port should be enabled for listening as well: UDP ports 4672 and 4665. If you are using Kad and your router is doing NAT (Network Address Translation), you should prevent your router from remapping the port of outgoing UDP port 4672 packets. This might help if you have a high ID but Kad status is 'firewalled'.

:'''Note''' As of mid-December 2006, aMule (CVS) has [[Universal Plug and Play]] (uPnP) capabilities which you can use to automatically configure the ports on your router, provided your router supports uPnP. This functionality is still being tested and should appear soon in an official release.

=== SuSE ===

'''[http://www.suse.com SuSE Linux]''' users try [[Firewall_SuSE|this HowTo]].

=== RedHat / Fedora Core ===

'''[http://fedora.redhat.com RedHat / Fedora Core]''' users try [[Firewall_Fedora|this HowTo]].

=== IPTables Configuration ===

If you set [http://www.ietf.org/rfc/rfc793.txt TCP] port in [[aMule]] to XX and [http://www.faqs.org/rfcs/rfc768.html 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 are building your iptables-rules from scratch, you also need to allow ''ESTABLISHED'' and ''RELATED'' traffic to come through your firewall:

''iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT''

And you must enable traffic to leave your machine aswell, by either allowing all outgoing traffic:

''iptables -P OUTPUT ACCEPT''

or specifying special rules.

'''NOTE:''' for [http://www.mandrake.com Mandrake] 10.0 Official and [http://www.iptables.org iptables] you may have to change the multi-port entry to ''iptables -A INPUT -p udp --dport '''XX:ZZ''' -j ACCEPT'' where ''XX'' is the same [http://www.ietf.org/rfc/rfc793.txt TCP] port number used in first line and ''ZZ'' is that number plus 3 (eg: ''4662:4665'')

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

Once everything is set, you can check [http://www.amule.org/testport.php here] if your ports are now open.

See also [[FAQ eD2k-Kademlia#Why does Kademlia still say it is firewalled?|the FAQ]] on "Why does Kademlia still say it is firewalled?"

== Routers ==

Here is a list of routers and how to set them up to forward their ports to [[aMule]].

In the descriptions below, examples are using the default ports (that is, ''4662'' for the [[Standard client TCP port]], ''4672'' for the [[Extended client UDP port]] and ''4665'' for the [[Extended server requests UDP port]].

=== Linksys WRT54GSV4 ===

#Open your web browser, ''http://192.168.1.1'' and log into it
#Go under ''Gaming applications''
#Now forward the ports to your computer:
##[[Standard client TCP port]]
###Change both ''Ports start'' and ''End'' to ''4662''
###In the next field set ''TCP''
###In the field, the last 3 digits of your LAN [[IP]]
##[[Extended client UDP port]]
###Change both ''Ports start'' and ''End'' to ''4672''
###In the next field set ''UDP''
###In the field, the last 3 digits of your LAN [[IP]]
##[[Extended server requests UDP port]]
###Change both ''Ports start'' and ''End'' to ''4665''
###In the next field set ''UDP''
###In the field, the last 3 digits of your LAN [[IP]]
#Now check ''Enable''
#And click ''Save settings''
#Then restart aMule :)

''--by '''Diablo69'''''

=== [http://www.linksys.com Linksys] Router configuration ===

This portion of the wiki applies only to stock versions of the [http://www.linksys.com Linksys] firmware. If you are using a [http://www.linksys.com Linksys] router running a variant of the [[GPL]] code, please follow the guides directly above as you are most likely using iptables.

Log into your [http://www.linksys.com Linksys] router. After successfully logging in, click on the main menu link labeled '''Applications & Gaming''' after which you should see an additional submenu list for this section. Make sure you are under the correct submenu by clicking '''Port Range Forwarding'''.

At this point, you should see a table with 6 columns. The columns are: ''Application'', ''Start to'', ''End'', ''Protocol'', ''IP Address'', ''Enable''.

'''The Application column''' 
Friendly name for the service. Put anything you want here, [[aMule]] being suggested.

'''The Start to -> End column''' 
Start and end ports. '''Start to''' should be ''4662'' but, in the end, this should reflect whatever port you have defined in [[aMule]] ''Preferences'' -> ''Connection'' -> ''Client TCP Port''. '''End''' should be ''4672'' but, in the end, this should reflect whatever port you have defined in [[aMule]] ''Preferences'' -> ''Connection'' -> ''eMule extended UDP Port''.

I suggest using 2 separate entries for each port unless this is not possible.

'''The Protocol column''' 
Protocol to listen for. If you use one line to open your [[aMule]] ports, set this option to '''Both'''. If you use a separate entry line for each, select option '''TCP''' for [[FAQ_ed2k#What_does_each_port_do?|Client TCP Port]] and option '''UDP''' for [[eMule]] [[FAQ_ed2k#What_does_each_port_do?|extended UDP Port]].

'''The IP Address column''' 
Internal [[IP|IP address]] to forward requests to. This is typically the internal (private) [[IP|IP address]] of the computer that will use [[aMule]].

'''The Enable column''' 
Enable rule. You'll need to check this in order to enable your [[aMule]] rules.

After adding your rule, make sure you save your settings. You can verify whether your rules work by [http://www.amule.org/testport.php testing your ports].

=== [http://www.dlink.com DLink] Router configuration ===

Log in to your [http://www.dlink.com DLink] router. There are three steps to take to enable your [[aMule]] [[port]]s.

'''IP Address setup'''

In the Home tab, click the DHCP button. This page displays the current [[IP address]]es assigned by the router, both static and dynamic. Look for the name or MAC address of the computer you'll be running [[aMule]] on. If your computer is receiving dynamically assigned [[IP address]]es, you will have to change your settings every so often if your [[IP address]] changes. To avoid this, use the Static DHCP section, and perform the following steps:

*'''Name''': Type in the name of your computer here, could be anything
*'''IP''': The [[IP address]] you want the router to always assign to your computer
*'''MAC Address''': The MAC address of your computer. You should be already connected to the router, so you can find your computer in the ''DHCP Client'' drop-down menu, and click clone, to populate this number
*Click ''Apply''

Now your computer will always receive the same [[IP address]].

Now click on the ''Advanced'' tab, and there are two areas that need to be updated:

'''Virtual Server'''
*Click the ''Virtual Server'' button. This page forwards external requests to a specific internal [[IP address]] in your network
*Click ''Enabled''
*Enter a name in the ''Name'' entry box, eg ''aMule TCP''
*Enter your static [[IP address]] in the ''Private IP'' box
*Select [http://www.ietf.org/rfc/rfc793.txt TCP] in ''Protocol type''
*Private [[port]] is the [[port]] that the router will forward the requests to on your computer. This can be anything, a good value is the default [[aMule]] [http://www.ietf.org/rfc/rfc793.txt TCP] [[port]], ''4662''
*Public [[port]] is the [[port]] that the router will receive requests on. Again, a good value is the [[aMule]] [http://www.ietf.org/rfc/rfc793.txt TCP] [[port]] of ''4662''
*Schedule is the times at which the port is open. Select ''Always'', or whatever times you wish
*Click ''Apply''

'''Applications'''
*Click the ''Applications'' button. This page allows you to enter a range of [[port]]s to open for application usage
*Click ''Enabled''
*Enter the [http://www.ietf.org/rfc/rfc793.txt TCP] [[port]] in the first ''Trigger Port'' box, a good value being ''4662''
*Select ''Trigger Type'' as [http://www.ietf.org/rfc/rfc793.txt TCP]
*In ''Public Port'', enter the range from your [[aMule]] [http://www.ietf.org/rfc/rfc793.txt TCP] [[port]] to your [[aMule]] [http://www.faqs.org/rfcs/rfc768.html UDP] [[port]], usually ''4662''-''4672''
*Select ''UDP'' as the ''Public Type''
*Click ''Apply''

You should now be all set, assuming that your computer firewall is setup to allow access on the selected [[port]]s.

'''Alternate Configuration (ie instead of Applications) for D-Link '''
*Go back to virtual server and set 2 other virtual servers for the UDP ports
(It works only that way on my D-Link DI-804HV)

*Virtual server aMuleUDP4665 - select your IP address and UDP and 4665 (port)

*Virtual Server aMuleUDP4672 - select your ip address and UDP and 4672 (port)

(disable the above amule applications if you did try and it do not work).
Then you shoudl have all arrows green ( and 3 virtual servers running for amule, 1 for TCP and 2 for UDP).

=== Netgear router ===

First, go to your router control page, locate at [http://routerlogin.net/start.htm http://routerlogin.net/start.htm]. Then, on the left side of the screen, under the Advanced group of options, click "Port Forwarding/Port Triggering." Click the "Add Custom Service" button, name it aMule1 (or whatever), set it as a TCP-only forwarding, with the starting and ending port being 4662 and the server IP address being whatever local address you're using (probably 192.168.1.2, if you're the only one connected to the router, but check), and click Apply. Repeat the process with aMule2 and aMule 3, using UDP-only ports for both and starting and ending ports of 4665 and 4672, respectively. (That is, the same starting and ending port within aMule2 and aMule3, but aMule2=4665 and aMule3=4672.) Make sure that iptables is properly set up on the machine which will run aMule (as above), and you're done.

=== TRENDnet router TW100 ===

First connect to your router: usually open a browser and type directly the router IP address: such as 192.168.0.1 (or 192.168.1.1), then the login box should appear ( depending on your router config) - if so answer the message log message with ‘admin’ as username and nothing as password (or you password if
you did set one).

Then On the left side Menu, Select Internet and thenselect Advanced Setup (Advanced Internet). Then click/select, [Special Applications]:

Add or replace 2 lines in the Special Applications list:
(Try not to remove something which you are using and which is already enabled)
(just add the new application for amule at the end in position Nr. 5 or Nr.6 in the list for example):

Create the entries as follows:

amuleU4665 TCP-4665-4665 UDP-4665-4665

amuleU4672 TCP-4672-4672 UDP-4672-4672 )

(In my Application List the “amuleU4665” and “amule4672” are in Nr1 and Nr2 but it can be in any position in your list).

->Click on the small box [ ] on the left for both lines of your amuleUxxxx applications to enable the special applications to work!

Then click on [Save], then click on [Close]

Then click on [Save] again on the page – Advanced Internet .

The next and last step is to click on the “Virtual Servers” menu on the left side, then the “Virtual Server page will appear”:

Add a new virtual server named like: AmuleTCP

Select your computer* IP Address: in the DropDown Menu

Select: TCP

Write the 4662 Port and 4662 port (both fields the same port)

Then [Add as new server]

Then you are set to have High ID and Kad ON. Finished with the Low-ID, yellow arrows and Kad Firewalled. Now all you arrows should be green and you should have access to Kad and ed2K.

''Important Note:''
*Be careful in the case that your computer is using the DHCP protocol (ie to obtain IP address from the router).
The router might not give all the time the same IP address to your computer.
(normally it does so... but sometimes it can change).
You have two solutions if you see that you have a low- ID then: (2 solutions)

1) log back to the router go back to the virtual server, select the amuleTCP virtual server that you created and just reselect you computer in the “PC(server)” entry box. And select [Update this server] and log out. It should do the job.

Or an alternative solution :

2)You can Set-up your computer with a fixed IP address if you want. If this problem of low-ID happens too often because you DHCP router gives different IP address to your computer, then you can put your computer in static mode or DHCP reserved address. But you need to know your DNS server(s) before to do that – so check with your ISP which are your DNS servers. Then configure your computer to run with a fixed DHCP/ Static address / Manual Address (name depends what OS you are running). For that go to your network settings and put the P address you want, and the gateway (you router IP address) and the DNS from your ISP – All this to be done ion the Other / PC Database (Admin) page of the router.

'''In the case that your TRENDNet router crashes or stop forwarding any''' traffic from/to your aMule computer . (it happened to me), then :

- reduce the Connection limit (in Preferences->Connection) to 100 (or to 50)
- reduce the "Max new connections / 5 secs" (in Preferences->Core Tweaks) to 10 (or to 5)
Stop amule and restart aMule so that configuration will be validated.

Make some tests to find your best config. It should give more stability to your router and avoid your router to crash ( ie you would have to reset and/or turn it on and off). This might be true for other routers as well(?).

''(TRENDnet Firewall from RFV - --[[User:Robert364|Robert364]] 17:05, 5 Nov 2006 (CET))
''

=== OpenBSD ===

The firewall that comes with OpenBSD is called packetfilter (pf). To get aMule running, you must add the following rules to your pf.conf (/etc/pf.conf):

''# aMule TCP and UDP'' 
''rdr on EXTIF proto tcp from any to any port 4662 -> IPADDR'' 
''rdr on EXTIF proto udp from any to any port 4672 -> IPADDR'' 
''rdr on EXTIF proto udp from any to any port 4665 -> IPADDR''

EXTIF is the name of your network-device that is connected with the internet. 
IPADDR is the internal ip-address of the computer in your network that runns aMule.

Example (device is '''/dev/xl0''', ip of computer running aMule is '''192.168.1.10'''):

''# aMule TCP and UDP'' 
''rdr on '''xl0''' proto tcp from any to any port 4662 -> '''192.168.1.10''' '' 
''rdr on '''xl0''' proto udp from any to any port 4672 -> '''192.168.1.10''' '' 
''rdr on '''xl0''' proto udp from any to any port 4665 -> '''192.168.1.10''' ''

Of course, the computer running aMule must also have access to the internet so add the following rules too:

''nat on EXTIF from IPADDR to any -> (EXTIF)'' 

EXTIF is the name of your network-device that is connected with the internet. 
IPADDR is the internal ip-address of the computer in your network that runns aMule.

Example (like above):

''nat on '''xl0''' from '''192.168.1.10''' to any -> ('''xl0''')''

Up to now there is no way (I could think of), to give KAD a better connection than "firewalled". See [[FAQ eD2k-Kademlia#Why does Kademlia still say it is firewalled?|the FAQ]] on "Why does Kademlia still say it is firewalled?"

FAQ eD2k-Kademlia

2006-12-22T21:36:38Z

207.255.46.56: More emphasis on Kad use of 4672 vs. NAT

<center>
<h4>F.A.Q. on eD2k-Kademlia</h4>

'''English''' | [[FAQ_eD2k-Kademlia-es|Español]] | [[FAQ_eD2k-Kademlia-it|Italiano]] | [[FAQ_eD2k-Kademlia-de|Deutsch]] | [[FAQ_ed2k-fr|Français]] | [[FAQ_eD2k-Kademlia-nl|Nederlands]] | [[FAQ_eD2k-Kademlia-pl|Polish]] | [[FAQ_eD2k-Kademlia-ru|Russian]]
</center>

== What is ED2K? ==

ED2K is a protocol originally used by the P2P (Peer-to-Peer) client [[eDonkey2000]], which is where the name comes from. It is a server-client based protocol, with the ability to exchange sources between clients.

The ED2K network is server based like many other P2P networks such as [[Kazaa]] (Kazaa is server based, but hides the server connection from the user), which means that the first thing you do when you run [[aMule]] is to connect to a server (either manually or automatically).

Once successfully connected to a server, the client can search, either locally (the connected server) or globally (all servers), for any file and the servers asked will provide the client with a list of all the files which match search parameters.

If the user starts a download, the client will then ask the server for sources, which the server will return in the form of IP addresses for the clients that have told the server that they have the specific file.

Then the remote client will begin to upload a whole chunk to your client as soon as you are the [[FAQ_eD2k-Kademlia#What_is_all_this_talk_about_credits,_ratings_and_scoring_about?|first in the queue]], and when the chunk has been completly sent, you will be taken back to its upload queue. This way different chunks get spread around the ED2K network, so that, although no-one may have at a same given moment the complete file, it may be completed by downloading the different chunks from different people (it is well known that users tend to stop sharing a file once it has been completed).

Note that clients upload only '''one''' chunk at a time to another client. Even if a client is in the upload queue of two different files of a same user and gets to the top of both, that user will only upload one of the files to that client (the other upload, depending on the ED2K application the client uses, will probably remain as a maximum priority upload, but will not begin until the other chunk has been successfully uploaded).

If both users have HighID (see [[FAQ_eD2k-Kademlia#What_is_LowID_and_HighID?|What is LowID and HighID?]]) the transfer will be done directly from client to client (Peer-to-Peer), but if one of the clients have LowID, the connection will be established through the server, since LowID cannot accept incoming connections. As a result, two LowID clients '''cannot''' connect to each other.

== What is Kademlia? ==

Kademlia is a natural evolution of the ED2K network. Kademlia is the future. See [[FAQ_eD2k-Kademlia#Are_there_any_limitations_on_the_ED2K_network?|Are there any limitations on the ED2K network?]] for more information on why Kademlia is necessary.

Since Kademlia is a decentralized network, it removes the bottleneck that was previously caused by the need for servers (though [[Lugdunum]] has done great work in reducing this bottleneck). Now, instead of connecting to a server, you just connect to a client (with a known IP-address and port), which supports the network [[Kademlia]]. This is called the Boot Strapping.

Once connected, depending on your ability to accept incoming connections, you are given either "open" or "firewalled" status, which is similar to the HighID and LowID of the ED2K network. Then you are given an ID.

When searching, each client acts as a small server and is given responsibility for certain keywords or sources. This adds to the complexity of finding sources, as you no longer have a central server to ask, but instead will have to propagate the query through the network.

Kademlia is supported in aMule since the 2.1.0 version.

== Is Kademlia the same as Overnet? ==

Short and clear: No. Overnet is the natural serverless evolution of the eDonkey software, while Kademlia is the natural serverless evolution of *Mule clients. Both are based on the original [[Kademlia]] algorithm but have been applied in different ways and therefore are incompatible. So, it's the same philosophy, but different rules. To learn about how Overnet works, refer to http://www.edonkey2000.com/documentation/how_on.html but, keep in mind, Overnet's development is closed until it reaches version 1.0, while Kademlia's development is completly open from the very beginning.

== What is a chunk? ==

In the ED2K protocol, to avoid sharing corrupt files, each file is divided into various parts, which are known as ''chunks'', and then each chunk is hashed (read below to know what a [[FAQ_eD2k-Kademlia#What_is_a_hash?|hash]] is). Each chunk is 9.28MB in size, so a 15MB file will be divided into two chunks (9.28MB + 5.72MB), a 315KB file will be a single chunk and a 100MB file will be divided into 11 chunks (10x9.28MB + 7.2MB).

== What is a hash? ==

Dividing each file into chunks (see [[FAQ_eD2k-Kademlia#What_is_a_chunk?|What is a chunk?]]) will avoid the problem of downloading a whole corrupted file since only the corrupted chunk will have to be downloaded again, but a method to identify corrupted chunks is needed. This is done by using MD4 hashes.

A [[MD4 hash]] is a unique value each chunk is given and is the result of a mathematical operation on every single bit on the chunk. This means that modifying a single bit in a chunk would result in a completely different hash. That means that the [[client]] needs to verify the integrity of each part of a file as it is downloaded.

Not only are the chunks hashed but also, in order to get a file-hash, all chunks's hashes are concatenated one after the other in their file order (that is: chunk1's_hash+chunk2's_hash+chunk3's_hash+...) and the resulting string is hashed. This way, each file on the ED2K network has a unique identifier. The file hash isn't taken from hashing the whole file, but from hashing the value of the chunk's hashes.

In reality, you need both the hash of a file and its size. These pieces of information is embedded in the ED2k URLs found in many places.

Take this for example:

ed2k://|file|eMule0.42f-Sources.zip|2407949|CC8C3B104AD58678F69858F1F9B736E9|/

The interesting parts are the fifth part, "2407949", which is the size of the file in bytes and the last part, "CC8C3B104AD58678F69858F1F9B736E9", which is the hash itself, stored as hex-decimals, 32 letters long.

The filename itself is irrelevant in the process of identifying the file.

== Why after searching, some files which are the same appear as a different file in the results, although they even have the same name? ==

If you understood "What is a hash" you will understand this quickly. When a search is started, the server tells the ED2K client the filename of the found file and the hash of the complete file for each file which matches the search. If two files, although being the same, have some difference in their content, no matter if it's big or small, the hash is different, so they are considered as a different file. That's also the reason why two file with different file name appear as the same file: on the ED2K network, the filename isn't important, the hash is.

== What is LowID and HighID? ==

Each client is assigned an ID (Identification) number which is unique and will distinguish the client from all other clients on the server. If this ID is below 16777216 (16 million) then you have a LowID and anything over is a HighID. Whether your client receives a high or low ID will depend on your client and whether or not the Client TCP port is open. Client TCP Port is an customisable option located in Preferences -> Connection. The default port is 4662 which is fine. If you understand [[FAQ_ed2k#What_is_ED2K?|what ED2K is]], odds are you'll understand the chances that clients with LowIDs may be unable to connect to other clients with LowIDs which reduces transfer rates significantly. This is the reason why having port 4662 TCP (or the one set in Preferences) is so important. Some of the larger servers refuse clients with LowIDs and disallow connections since LowID clients have data transfered through the server, rather than directly from the other client, which in turn adds more overhead for the server.

For clients with a HighID, their ID is the result of a mathematical operation with their IP which corresponds to A + 256*B + 256*256*C + 256*256*256*D, where the IP is A.B.C.D. Keep in mind that this ID has identification purposes as well. Apart from having an ID over or under 16777216, it does not matter if the ID is bigger or smaller. This means a client with an ID of 50000000 isn't any better than a client with an ID of 49999999. The only exception is at times servers are either incorrectly configured or are very busy and issue LowIDs to clients even though port 4662 TCP is open. These are rare exceptions but it can happen sometimes.

If you're unsure about having proper port settings, you can test your ports [http://www.amule.org/testport.php here].

== Which ports do I have to configure in a firewall or router to run aMule? ==

One has to distinguish between incoming and outgoing connections. Normally, all ports of a router are open for sending data (outgoing connection).

So, in this normal case, You only have to configure the ports for ''incoming'' connections:

aMule works even with no specific ports opened, but you won't get a HighID in this case. As mentioned above, to be given a HighID, port 4662 TCP (or the one set in the Preferences) must be listening (i.e. opened in your firewall and forwarded in your router).

Apart from that port, to have an optimal ED2K experience, two more port should be enabled for listening as well: UDP ports 4672 and 4665 (that is, TCP_PORT+3) (both can be changed to any other number in the Preferences).

== Why does Kademlia still say it is "firewalled?" ==

If you are using Kad and your router is doing NAT (Network Address Translation), you should prevent your router from remapping the port of outgoing UDP port 4672 packets. This might help if you have a high ID but Kad status is 'firewalled'.

== What does each port do? ==

Well, since most ports can be configured to be set to any other number, the defaults will be listed. The traffic direction is from client perspective (you):
*4661 TCP (outgoing): Port, on which a server listens for connection (defined by server).
*4662 TCP (outgoing and incoming): Client to client transfers.
*4665 UDP (outgoing and incoming): Used for global server searches and global source queries. This is always Client TCP port + 3
*4672 UDP (outgoing and incoming): Extended eMule protocol, Queue Rating, File Reask Ping, Kad. Kad will be 'firewalled' if NAT (Network Address Translation) remaps this port number.
*4711 TCP: WebServer listening port.
*4712 TCP: External Connection port. Used to communicate aMule with other applications such as aMule WebServer or aMuleCMD.
== Are there any limitations on the ED2K network? ==

Not much, but yes, there are: two natural limits and a "forced" limitation. The two natural limits have already been mentioned before. First, the issues on LowID users (their transfers involve data through the server and two LowID clients can't share between them). The second, although ED2K is a p2p protocol, it needs servers to establish the p2p connection. This has lots of problems relating to bottlenecks, privacy and scalability (if one single server is disconnected, a big part of the network is disconnected with it). This latter one is solved in the Kademlia protocol.

About the "forced" limitation, it's only a limit to make sure that clients share, so that the ED2K network will not disappear: clients which have an upload limit of X KBps, where X is between 0 and 3.99 (both included) can download at a maximum of X*3 KBps. Clients which have an upload limit of Y KBps, where Y is between 4 and 9.99 (both included) can download at a maximum of Y*4 KBps. Clients with an upload limit of 10KBps or more have no downloading limitations. This restriction is set in the client application so it could be by-passed by hacking the code, but that would probably result in being banned from the servers you connect to.

Also, any client is forced to allow at least three upload slots, so it's not possible to allow more than upload_limit/3 KBps per slot.

There is one last limit: Maximum file size is exactly 256GB (274877906944 bytes). Older limit (up to eMule 0.46 and aMule 2.1.*) was slightly under 4GB aproximately (exactly 4294967295 bytes, although aMule would only support files up to 4290048000 bytes).

Additionally, this is not an eD2k limitation but a server limitation, servers will only send 300 results for your searches, so don't expect any more results.

And on the clients side, filenames are usually limited to 161 [[character]]s.

== Are there any limitations on the Kademlia network? ==

*As it is a network derived from the ed2k network and, therefore, has to maintain compatibility when it comes to identify files uniquely, the 256GB maximum file size limit exisits in the Kademlia network too.
*Same happens with the 161 characters limit.

== In search window, what filter stands for which filetype? ==

Keep in mind that the filters in the search window don't depend on the file type, but on the extensions of the filenames, in the following way:
*'''Archive:''' ''.ace .arj .rar .tar.bz2 .tar.gz .zip .Z''
*'''Audio:''' ''.aac .ape .au .mp2 .mp3 .mp4 .mpc .ogg .wav .wma''
*'''CDImage:''' ''.bin .ccd .cue .img .iso .nrg .sub''
*'''Picture:''' ''.bmp .gif .jpeg .jpg .png .tif''
*'''Program:''' ''.com .exe''
*'''Video:''' ''.avi .divx .mov .mpeg .mpg .ogg .ram .rm .vivo .vob''

So, a movie file that has the name "Birthday.zip" will appear in the Archive filter, but not in the Video filter.

== What is a source? ==

A source is a client which is sharing some chunk in some file you have in your downloading queue which you still have not completed. Obviously, the more sources you can get for a given file, the more possibilities you have to download the file and the quicker you'll download it. Keep in mind that there's a difference between "sources" and "available sources" if you're on LowID, since "sources"s stands for clients sharing a chunk or file you still haven't completed, while "available sources" stands for clients sharing a chunk or file you still haven't completed and from who you can download (that is, a source who is on HighID).

== What is all this talk about credits, ratings and scoring about? ==

All three concepts have to do with the way in which the ED2K network establishes the uploading queues preferences.

The score is the most important value: the client with the higher score will be the next client which you'll provide a slot to. The way in the score value is set is this: score = rate x time_waiting_in_seconds / 100
So, to understand this, we must known what rate is.

Rate can be understood as an objective preference. This is, the preference which a client is given without caring how much time it's been waiting. When a client is added to the uploading queue, it gets a rate of 100. This value is modified following according to this:

According to the amount of credits, the rate will be multiplied by 1x to 10x.
Depending on the file priority, it will be multiplied by 0.2x to 1.8x (Release 1.8x, High 0.9x, Normal 0.7x, Low 0.6x, Very Low: 0.2x). 
Users on specific old clients which load too much the network traffic will get penalized by multiplying their rate by 0.5x.

Banned clients will instantly get no rate (that is, their rate will by multiplied by 0).

This multiplying values are known as "modifiers". Clients with a modifier value strictly bigger than 1 will be marked as yellow in the icon.

So we only have credits left to known. Credits are a prize you get for uploading files to a specific user. Credits are exchanged between two specific clients, they are not global, so your own credits can't be viewed, although you can know the credits any other user has on you (that is, the credits you owe that client). Since credits are managed by the uploading client, you might be uploading to some client with no credits support, so you will gain no credits on him, although that client will actually get credits on you if it uploads to you, since you do have credits support. This credits are stored in clients.met file.

The credits modifier used by rate is the lower between these two: (upload_total x 2)/download_total or sqrt(upload_total+2) where both upload_total and download_total are measured in MBs.

If the result is lower than 1, then it is set to 1 and if it is bigger than 10, it is set to 10. In addition, if the uploaded total is less than 1MB, the modifier is set to 1 and if the downloaded total is equal to 0, then the modifier is set to 10.

== What is a slot? ==

When uploading files, your upload bandwidth (which may vary depending on the upload limit or the natural connection-type upload limit) will be divided into slots. So, each slot is an amount of KBps which will be assigned to each client who tries to download from you.

Firewall

2006-12-22T21:28:38Z

207.255.46.56: Add details to the intro.

<center>'''English''' | [[Firewall-es|Español]] | [[Firewall-de|Deutsche]] </center>

== Firewalls ==

By default, firewalls and routers block incoming ports. To achieve the best results with aMule, you need to configure your firewall or router to open certain ports which aMule uses. (The port numbers are configurable in preferences). See [[FAQ eD2k-Kademlia#Which ports do I have to configure in a firewall or router to run aMule?|the FAQ]].

In particular, to be given an [[FAQ eD2k-Kademlia#What is LowID and HighID?|eD2k HighID]], port 4662 TCP must be listening (i.e. opened in your firewall and forwarded in your router). To have an optimal ED2K experience, two more port should be enabled for listening as well: UDP ports 4672 and 4665. If you are using Kad and your router is doing NAT (Network Address Translation), you should prevent your router from remapping the port of outgoing UDP port 4672 packets. This might help if you have a high ID but Kad status is 'firewalled'.

:'''Note''' As of mid-December 2006, aMule (CVS) has [[Universal Plug and Play]] (uPnP) capabilities which you can use to automatically configure the ports on your router, provided your router supports uPnP. This functionality is still being tested and should appear soon in an official release.

=== SuSE ===

'''[http://www.suse.com SuSE Linux]''' users try [[Firewall_SuSE|this HowTo]].

=== RedHat / Fedora Core ===

'''[http://fedora.redhat.com RedHat / Fedora Core]''' users try [[Firewall_Fedora|this HowTo]].

=== IPTables Configuration ===

If you set [http://www.ietf.org/rfc/rfc793.txt TCP] port in [[aMule]] to XX and [http://www.faqs.org/rfcs/rfc768.html 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 are building your iptables-rules from scratch, you also need to allow ''ESTABLISHED'' and ''RELATED'' traffic to come through your firewall:

''iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT''

And you must enable traffic to leave your machine aswell, by either allowing all outgoing traffic:

''iptables -P OUTPUT ACCEPT''

or specifying special rules.

'''NOTE:''' for [http://www.mandrake.com Mandrake] 10.0 Official and [http://www.iptables.org iptables] you may have to change the multi-port entry to ''iptables -A INPUT -p udp --dport '''XX:ZZ''' -j ACCEPT'' where ''XX'' is the same [http://www.ietf.org/rfc/rfc793.txt TCP] port number used in first line and ''ZZ'' is that number plus 3 (eg: ''4662:4665'')

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

Once everything is set, you can check [http://www.amule.org/testport.php here] if your ports are now open.

== Routers ==

Here is a list of routers and how to set them up to forward their ports to [[aMule]].

In the descriptions below, examples are using the default ports (that is, ''4662'' for the [[Standard client TCP port]], ''4672'' for the [[Extended client UDP port]] and ''4665'' for the [[Extended server requests UDP port]].

=== Linksys WRT54GSV4 ===

#Open your web browser, ''http://192.168.1.1'' and log into it
#Go under ''Gaming applications''
#Now forward the ports to your computer:
##[[Standard client TCP port]]
###Change both ''Ports start'' and ''End'' to ''4662''
###In the next field set ''TCP''
###In the field, the last 3 digits of your LAN [[IP]]
##[[Extended client UDP port]]
###Change both ''Ports start'' and ''End'' to ''4672''
###In the next field set ''UDP''
###In the field, the last 3 digits of your LAN [[IP]]
##[[Extended server requests UDP port]]
###Change both ''Ports start'' and ''End'' to ''4665''
###In the next field set ''UDP''
###In the field, the last 3 digits of your LAN [[IP]]
#Now check ''Enable''
#And click ''Save settings''
#Then restart aMule :)

''--by '''Diablo69'''''

=== [http://www.linksys.com Linksys] Router configuration ===

This portion of the wiki applies only to stock versions of the [http://www.linksys.com Linksys] firmware. If you are using a [http://www.linksys.com Linksys] router running a variant of the [[GPL]] code, please follow the guides directly above as you are most likely using iptables.

Log into your [http://www.linksys.com Linksys] router. After successfully logging in, click on the main menu link labeled '''Applications & Gaming''' after which you should see an additional submenu list for this section. Make sure you are under the correct submenu by clicking '''Port Range Forwarding'''.

At this point, you should see a table with 6 columns. The columns are: ''Application'', ''Start to'', ''End'', ''Protocol'', ''IP Address'', ''Enable''.

'''The Application column''' 
Friendly name for the service. Put anything you want here, [[aMule]] being suggested.

'''The Start to -> End column''' 
Start and end ports. '''Start to''' should be ''4662'' but, in the end, this should reflect whatever port you have defined in [[aMule]] ''Preferences'' -> ''Connection'' -> ''Client TCP Port''. '''End''' should be ''4672'' but, in the end, this should reflect whatever port you have defined in [[aMule]] ''Preferences'' -> ''Connection'' -> ''eMule extended UDP Port''.

I suggest using 2 separate entries for each port unless this is not possible.

'''The Protocol column''' 
Protocol to listen for. If you use one line to open your [[aMule]] ports, set this option to '''Both'''. If you use a separate entry line for each, select option '''TCP''' for [[FAQ_ed2k#What_does_each_port_do?|Client TCP Port]] and option '''UDP''' for [[eMule]] [[FAQ_ed2k#What_does_each_port_do?|extended UDP Port]].

'''The IP Address column''' 
Internal [[IP|IP address]] to forward requests to. This is typically the internal (private) [[IP|IP address]] of the computer that will use [[aMule]].

'''The Enable column''' 
Enable rule. You'll need to check this in order to enable your [[aMule]] rules.

After adding your rule, make sure you save your settings. You can verify whether your rules work by [http://www.amule.org/testport.php testing your ports].

=== [http://www.dlink.com DLink] Router configuration ===

Log in to your [http://www.dlink.com DLink] router. There are three steps to take to enable your [[aMule]] [[port]]s.

'''IP Address setup'''

In the Home tab, click the DHCP button. This page displays the current [[IP address]]es assigned by the router, both static and dynamic. Look for the name or MAC address of the computer you'll be running [[aMule]] on. If your computer is receiving dynamically assigned [[IP address]]es, you will have to change your settings every so often if your [[IP address]] changes. To avoid this, use the Static DHCP section, and perform the following steps:

*'''Name''': Type in the name of your computer here, could be anything
*'''IP''': The [[IP address]] you want the router to always assign to your computer
*'''MAC Address''': The MAC address of your computer. You should be already connected to the router, so you can find your computer in the ''DHCP Client'' drop-down menu, and click clone, to populate this number
*Click ''Apply''

Now your computer will always receive the same [[IP address]].

Now click on the ''Advanced'' tab, and there are two areas that need to be updated:

'''Virtual Server'''
*Click the ''Virtual Server'' button. This page forwards external requests to a specific internal [[IP address]] in your network
*Click ''Enabled''
*Enter a name in the ''Name'' entry box, eg ''aMule TCP''
*Enter your static [[IP address]] in the ''Private IP'' box
*Select [http://www.ietf.org/rfc/rfc793.txt TCP] in ''Protocol type''
*Private [[port]] is the [[port]] that the router will forward the requests to on your computer. This can be anything, a good value is the default [[aMule]] [http://www.ietf.org/rfc/rfc793.txt TCP] [[port]], ''4662''
*Public [[port]] is the [[port]] that the router will receive requests on. Again, a good value is the [[aMule]] [http://www.ietf.org/rfc/rfc793.txt TCP] [[port]] of ''4662''
*Schedule is the times at which the port is open. Select ''Always'', or whatever times you wish
*Click ''Apply''

'''Applications'''
*Click the ''Applications'' button. This page allows you to enter a range of [[port]]s to open for application usage
*Click ''Enabled''
*Enter the [http://www.ietf.org/rfc/rfc793.txt TCP] [[port]] in the first ''Trigger Port'' box, a good value being ''4662''
*Select ''Trigger Type'' as [http://www.ietf.org/rfc/rfc793.txt TCP]
*In ''Public Port'', enter the range from your [[aMule]] [http://www.ietf.org/rfc/rfc793.txt TCP] [[port]] to your [[aMule]] [http://www.faqs.org/rfcs/rfc768.html UDP] [[port]], usually ''4662''-''4672''
*Select ''UDP'' as the ''Public Type''
*Click ''Apply''

You should now be all set, assuming that your computer firewall is setup to allow access on the selected [[port]]s.

'''Alternate Configuration (ie instead of Applications) for D-Link '''
*Go back to virtual server and set 2 other virtual servers for the UDP ports
(It works only that way on my D-Link DI-804HV)

*Virtual server aMuleUDP4665 - select your IP address and UDP and 4665 (port)

*Virtual Server aMuleUDP4672 - select your ip address and UDP and 4672 (port)

(disable the above amule applications if you did try and it do not work).
Then you shoudl have all arrows green ( and 3 virtual servers running for amule, 1 for TCP and 2 for UDP).

=== Netgear router ===

First, go to your router control page, locate at [http://routerlogin.net/start.htm http://routerlogin.net/start.htm]. Then, on the left side of the screen, under the Advanced group of options, click "Port Forwarding/Port Triggering." Click the "Add Custom Service" button, name it aMule1 (or whatever), set it as a TCP-only forwarding, with the starting and ending port being 4662 and the server IP address being whatever local address you're using (probably 192.168.1.2, if you're the only one connected to the router, but check), and click Apply. Repeat the process with aMule2 and aMule 3, using UDP-only ports for both and starting and ending ports of 4665 and 4672, respectively. (That is, the same starting and ending port within aMule2 and aMule3, but aMule2=4665 and aMule3=4672.) Make sure that iptables is properly set up on the machine which will run aMule (as above), and you're done.

=== TRENDnet router TW100 ===

First connect to your router: usually open a browser and type directly the router IP address: such as 192.168.0.1 (or 192.168.1.1), then the login box should appear ( depending on your router config) - if so answer the message log message with ‘admin’ as username and nothing as password (or you password if
you did set one).

Then On the left side Menu, Select Internet and thenselect Advanced Setup (Advanced Internet). Then click/select, [Special Applications]:

Add or replace 2 lines in the Special Applications list:
(Try not to remove something which you are using and which is already enabled)
(just add the new application for amule at the end in position Nr. 5 or Nr.6 in the list for example):

Create the entries as follows:

amuleU4665 TCP-4665-4665 UDP-4665-4665

amuleU4672 TCP-4672-4672 UDP-4672-4672 )

(In my Application List the “amuleU4665” and “amule4672” are in Nr1 and Nr2 but it can be in any position in your list).

->Click on the small box [ ] on the left for both lines of your amuleUxxxx applications to enable the special applications to work!

Then click on [Save], then click on [Close]

Then click on [Save] again on the page – Advanced Internet .

The next and last step is to click on the “Virtual Servers” menu on the left side, then the “Virtual Server page will appear”:

Add a new virtual server named like: AmuleTCP

Select your computer* IP Address: in the DropDown Menu

Select: TCP

Write the 4662 Port and 4662 port (both fields the same port)

Then [Add as new server]

Then you are set to have High ID and Kad ON. Finished with the Low-ID, yellow arrows and Kad Firewalled. Now all you arrows should be green and you should have access to Kad and ed2K.

''Important Note:''
*Be careful in the case that your computer is using the DHCP protocol (ie to obtain IP address from the router).
The router might not give all the time the same IP address to your computer.
(normally it does so... but sometimes it can change).
You have two solutions if you see that you have a low- ID then: (2 solutions)

1) log back to the router go back to the virtual server, select the amuleTCP virtual server that you created and just reselect you computer in the “PC(server)” entry box. And select [Update this server] and log out. It should do the job.

Or an alternative solution :

2)You can Set-up your computer with a fixed IP address if you want. If this problem of low-ID happens too often because you DHCP router gives different IP address to your computer, then you can put your computer in static mode or DHCP reserved address. But you need to know your DNS server(s) before to do that – so check with your ISP which are your DNS servers. Then configure your computer to run with a fixed DHCP/ Static address / Manual Address (name depends what OS you are running). For that go to your network settings and put the P address you want, and the gateway (you router IP address) and the DNS from your ISP – All this to be done ion the Other / PC Database (Admin) page of the router.

'''In the case that your TRENDNet router crashes or stop forwarding any''' traffic from/to your aMule computer . (it happened to me), then :

- reduce the Connection limit (in Preferences->Connection) to 100 (or to 50)
- reduce the "Max new connections / 5 secs" (in Preferences->Core Tweaks) to 10 (or to 5)
Stop amule and restart aMule so that configuration will be validated.

Make some tests to find your best config. It should give more stability to your router and avoid your router to crash ( ie you would have to reset and/or turn it on and off). This might be true for other routers as well(?).

''(TRENDnet Firewall from RFV - --[[User:Robert364|Robert364]] 17:05, 5 Nov 2006 (CET))
''

=== OpenBSD ===

The firewall that comes with OpenBSD is called packetfilter (pf). To get aMule running, you must add the following rules to your pf.conf (/etc/pf.conf):

''# aMule TCP and UDP'' 
''rdr on EXTIF proto tcp from any to any port 4662 -> IPADDR'' 
''rdr on EXTIF proto udp from any to any port 4672 -> IPADDR'' 
''rdr on EXTIF proto udp from any to any port 4665 -> IPADDR''

EXTIF is the name of your network-device that is connected with the internet. 
IPADDR is the internal ip-address of the computer in your network that runns aMule.

Example (device is '''/dev/xl0''', ip of computer running aMule is '''192.168.1.10'''):

''# aMule TCP and UDP'' 
''rdr on '''xl0''' proto tcp from any to any port 4662 -> '''192.168.1.10''' '' 
''rdr on '''xl0''' proto udp from any to any port 4672 -> '''192.168.1.10''' '' 
''rdr on '''xl0''' proto udp from any to any port 4665 -> '''192.168.1.10''' ''

Of course, the computer running aMule must also have access to the internet so add the following rules too:

''nat on EXTIF from IPADDR to any -> (EXTIF)'' 

EXTIF is the name of your network-device that is connected with the internet. 
IPADDR is the internal ip-address of the computer in your network that runns aMule.

Example (like above):

''nat on '''xl0''' from '''192.168.1.10''' to any -> ('''xl0''')''

Up to now there is no way (I could think of), to give KAD a better connection than "firewalled".

Usage Statusbar

2006-12-22T21:06:22Z

207.255.46.56: s/iw/is/

[[Usage aMule|Back to Index]]

== Description ==

The status bar allows to easily view general useful information about the current aMule session.

It is placed at the bottom of the main window and looks like this:

http://www.amule.org/dev-up/window_statusbar1.jpg

== Usage ==

The status bar is divided into several sections:

=== Log ===

You can see the last line printed into the log at the left most part of the statusbar:

http://www.amule.org/dev-up/window_statusbar2.jpg

The line might be only partially shown if it is larger than the space left in the statusbar. In this case it comes very useful to click in the information button by the text.

http://www.amule.org/dev-up/window_statusbar3.jpg

When clicked, a window will popup displaying the complete line.

http://www.amule.org/dev-up/window_statusbar13.jpg

=== Users ===

aMule tries to calculate the amount of users currently connected to the networks it is connected to.

The first number in the '''Users''' field corresponds to the estimated amount of users currently connected to the ed2k network.

http://www.amule.org/dev-up/window_statusbar4.jpg

The second number in that field corresponds to the estimated amount of users connected to the Kademlia network.

http://www.amule.org/dev-up/window_statusbar5.jpg

In both ed2k and Kad numbers the following letters are used to specify the multiplying factor:
{|
| '''''Letter''''' || '''Multiplying factor'''
|-
| ''k'' || 1000
|-
| ''M'' || 1000x1000
|-
| ''G'' || 1000x1000x1000
|-
| ''T'' || 1000x1000x1000x1000
|}

=== Files ===

aMule also tries to calculate the amount of currently available files on the networks it is connected to.

Again, the first number in the '''Files''' field corresponds to the estimated amount of files currently available in the ed2k network.

http://www.amule.org/dev-up/window_statusbar6.jpg

And again, the second number in this field corresponds to the estimated amount of files currently available in the Kademlia network.

http://www.amule.org/dev-up/window_statusbar7.jpg

As with the [[Usage_Statusbar#Users||Users]] field, the last letter indicates the multiplying factor (see above which letter corresponds to which multiplying factor).

=== Speed ===

The statusbar provides a handy way to know the bandwidth aMule is effectively taking.

First it has a graphic which displays two arrows surrounding a globe provides a brief summary of the connection status. The downwards arrow will be green when aMule is downloading and red when it isn't. The upwards arrow will be green when aMule is uploading and red when it isn't.

http://www.amule.org/dev-up/window_statusbar33.jpg

This are the possible graphics:
{|
| '''Graphic''' || '''''Description'''''
|-
| http://www.amule.org/dev-up/window_statusbar29.jpg || ''aMule isn't downloading nor uploading''
|-
| http://www.amule.org/dev-up/window_statusbar30.jpg || ''aMule is downloading but isn't uploading''
|-
| http://www.amule.org/dev-up/window_statusbar31.jpg || ''aMule isn't downloading but is uploading''
|-
| http://www.amule.org/dev-up/window_statusbar32.jpg || ''aMule both downloading and uploading''
|}

Right by the connections status icon the upload and download speeds are displayed.

In the '''Up''' field you can see the upload speed it is performing.

http://www.amule.org/dev-up/window_statusbar8.jpg

In the '''Down''' field you can see at what speed aMule is downloading.

http://www.amule.org/dev-up/window_statusbar9.jpg

If you have enabled "Show overhead bandwidth" in Preferences, then a number in brackets will appear both by the upload and download speed numbers. This numbers show the bandwidth that the overhead traffic (connections, pings, control traffic, ...) are taking for the uploads and downloads respectively.

http://www.amule.org/dev-up/window_statusbar28.jpg

=== Networks ===

The last field shows information about the networks status.

If you are connected to the ed2k network, you will be able to see the name (or IP if it has no known name) of the ed2k server you are connected to.

http://www.amule.org/dev-up/window_statusbar11.jpg

If you are not connected to the ed2k network, they you will see '''Not connected''' or '''Connecting''' if you are trying to connect.

Now about the Kademlia network, you should see its status by the '''Kad''' text.

http://www.amule.org/dev-up/window_statusbar12.jpg

Possible values are:
{|
| '''Text''' || '''''Meaning'''''
|-
| ''ok'' || Connected
|-
|''firewalled'' || Firewalled
|-
| ''off'' || Not connected, offline
|}

A very special icon in the statusbar is the earth icon:

http://www.amule.org/dev-up/window_statusbar10.jpg

The arrows in this globe change their colour depending on the connection status of aMule.

The lower-left arrow refers to the ed2k network:

http://www.amule.org/dev-up/window_statusbar23.jpg

The upper-right arrow refers to the Kademlia network:

http://www.amule.org/dev-up/window_statusbar24.jpg

This are the coulour's meanings:
{|
| '''Colour''' || '''''Meaning'''''
|-
| Red || ''Offline, not connected''
|-
| Orange || ''Connecting''
|-
| Yellow || ''Connected but firewalled''
|-
| Green || ''Connected''
|}

Here is the list of all possible globe icons and their meanings:

{|
| http://www.amule.org/dev-up/window_statusbar16.jpg || Both ed2k and kademlia networks are offline
|-
| http://www.amule.org/dev-up/window_statusbar17.jpg || The ed2k network is offline, but Kad is connected though firewalled
|-
| http://www.amule.org/dev-up/window_statusbar15.jpg || The ed2k network is offline, but Kad is connected
|-
| http://www.amule.org/dev-up/window_statusbar19.jpg || The ed2k network is being connected, while the kad network is offline
|-
| http://www.amule.org/dev-up/window_statusbar18.jpg || The ed2k network is being connected, while the Kad network is connected though firewalled
|-
| http://www.amule.org/dev-up/window_statusbar14.jpg || The ed2k network is being connected, while the Kad network is connected
|-
| http://www.amule.org/dev-up/window_statusbar26.jpg || The ed2k network is connected with LowID (firewalled), while the Kad network is offline
|-
| http://www.amule.org/dev-up/window_statusbar25.jpg || Both the ed2k and Kad networks are connected but firewalled
|-
| http://www.amule.org/dev-up/window_statusbar21.jpg || The ed2k network is connected, while the Kad network is offline
|-
| http://www.amule.org/dev-up/window_statusbar20.jpg || Both the ed2k and Kad networks are connected, but the Kad network is firewalled
|-
| http://www.amule.org/dev-up/window_statusbar22.jpg || Both the ed2k and Kad networks are connected
|}

'''Note:''' It should never happen that ed2k arrow is yellow and the Kad arrow is green, so it is not listed int he above table.

== Overview ==

http://www.amule.org/dev-up/window_statusbar27.jpg

{|
|+ Quick Reference
| '''Number''' || '''''Description'''''
|-
| 1 || ''Popup complete last log line''
|-
| 2 || ''Last log line (just what fits in window)''
|-
| 3 || ''Estimated online ed2k users''
|-
| 4 || ''Estimated online Kademlia users''
|-
| 5 || ''Estimated available ed2k files''
|-
| 6 || ''Estimated available Kademlia files''
|-
| 7 || ''Uploading speed''
|-
| 8 || ''Uploading overhead speed''
|-
| 9 || ''Downloading speed''
|-
| 10 || ''Downloading overhead speed''
|-
| 11 || ''ED2k and Kademlia status graphical summary''
|-
| 12 || ''ED2k connected server name or ed2k status''
|-
| 13 || ''Kademlia status''
|-
| 14 || ''Connection status graphical summary''
|}

<center>[[Usage aMule|Back to Index]]</center>