Difference between revisions of "Get HighID"
(→Description: much-needed copy-edit) |
(→Description: further copy-editing) |
||
| Line 8: | Line 8: | ||
== Description == | == Description == | ||
aMule uses three ports to transfer data with other clients and servers: | aMule uses three ports to transfer data with other clients and servers: | ||
| − | + | #the [[standard client TCP port]]; | |
| − | + | #the [[extended client UDP port]]; and | |
| − | + | #the [[extended server requests UDP port]]. | |
| − | Ideally, all three ports should be accessible. However, you can still connect to the '''ED2K''' network even if none of these ports is accessible. | + | Ideally, all three ports should be accessible. However, you can still connect to the '''ED2K''' network even if none of these ports is accessible. For ED2K connection, if the ''standard client TCP'' port (No. 1) is not accessible, you will receive a [[Low ID]] and experience significantly lower transfer speeds; access to this port (No. 1) is all you need to attain [[High ID]] status; this will provide the highest transfer speeds possible on the ED2K network. |
| − | + | ||
| − | + | ||
| − | For the '''Kademlia''' network, | + | For the '''Kademlia''' network, both ''standard client TCP'' and ''extended client UDP'' ports (Numbers 1 and 2) must be accessible. If they are not, you won't be able to connect to Kademlia at all. |
| − | Making the | + | Making the ''extended server requests UDP'' port (No. 3) accessible too is highly recommended, because this will provide you with valuable statistics and information about files on the ED2k network. Similarly, accessing the ''extended client UDP port'' (No. 2) on the ED2K network is highly recommended, because this will provide you with valuable statistics and information about other clients and files. |
== Determining which ports to forward == | == Determining which ports to forward == | ||
Revision as of 04:22, 22 August 2008
Description
aMule uses three ports to transfer data with other clients and servers:
- the standard client TCP port;
- the extended client UDP port; and
- the extended server requests UDP port.
Ideally, all three ports should be accessible. However, you can still connect to the ED2K network even if none of these ports is accessible. For ED2K connection, if the standard client TCP port (No. 1) is not accessible, you will receive a Low ID and experience significantly lower transfer speeds; access to this port (No. 1) is all you need to attain High ID status; this will provide the highest transfer speeds possible on the ED2K network.
For the Kademlia network, both standard client TCP and extended client UDP ports (Numbers 1 and 2) must be accessible. If they are not, you won't be able to connect to Kademlia at all.
Making the extended server requests UDP port (No. 3) accessible too is highly recommended, because this will provide you with valuable statistics and information about files on the ED2k network. Similarly, accessing the extended client UDP port (No. 2) on the ED2K network is highly recommended, because this will provide you with valuable statistics and information about other clients and files.
Determining which ports to forward
Start aMule and open the Preferences -> Connection window. See the Standard client TCP port box, the Extended client UDP port box and the number by the UDP port for extended server requests (TCP+3). Those three are the ports aMule uses.
As said before, it is recommended to make all three ports accessible (even if not all are required).
Making ports accessible
You can check if a port is "accessible" (also known as "open") by visiting aMule's Test Port page.
So what does "not accessible" mean? It means that:
- You are behind a router which is blocking incoming connections to your port
- You are behind a firewall (actually, when routers block ports it is because they are acting as a firewall) which is blocking some of your ports:
- The firewall can be on your computer, for example, the iptables daemon
- The firewall can be somewhere outside your computer, probably some gateway through which you connect to the internet
If you have a firewall, then you should ask your administrator to open the ports there (or read the manual if you can access the firewall's configuration). There are too many firewalls to describe, however, check the Firewall article.
If you are behind a router ask your administrator to forward the ports to your computer (see above to know which ports to forward). However, if you have access to your router's configuration, you can do that yourself:
- Disable DHCP in your computer (not in router!) to get a static IP address in the LAN. This is done through the /etc/interfaces configuration file (see man interfaces)
- In the router's configuration, forward the ports aMule should use to your IP (you static IP in the LAN, as described above) and apply changes in the router (you might have to restart the router)
The router's configuration is usually available through http://192.168.1.1 from the webbrowser. The exact place where ports can be forwarded in your router's configuration system varies greatly from one router to another. And there are hundreds of different router models, so this can't be explained here. However, as a general rule, you should search for some section called "LAN configuration", "NAT configuration", "Firewall", "Ports" or "Security" (remember, this is just a general rule. Your router could be very different). See the Routers article to see how different routers are set up, maybe you are lucky and your router is listed there :-)
Also, if you think the router is what is blocking the ports, you can go check " http://portforward.com/ ". This site offers a kind of walkthrough for a lot of routers, and it works most of the times. Some routersettings also are mentioned in Diesel´s router-database (rem.: german).
Notes
No, there's no easier way. That's how port forwarding goes :) Same for eMule, Shareaza, lphant, Napster, Morpheus, Kazaa, Apache, FTP Server, ...
