Simple checklist for a nice Emule experience

Deutsche Version

Contents

0.0 Minimum System Requirements
1.0 ISP Trouble
1.1 NAT
1.2 Port-filtering/ Traffic-shaping/ Port-blocking
1.3 High Transfer Volume
2. LAN/ Router
2.1 Portforwarding
2.2 Max. Connections
3.0 Client Computer
3.1 NIC Drivers
3.2 DSL Drivers
3.3 Minimizing Running Operating System Services
3.4 Closing Open Ports
3.5 Firewall And IP-Filter (On Emule-Client PC)
3.6 "Hardening" The TCP-Stack
4.0 Emule
4.1 Ports
4.2 Preferences/ Tips
4.3 Server
4.4 Kademlia
5.0 Remarks

0.0 Minimum System Requirements

These requirements are meant for Emule running 24/7 under high load, not for a 24 hour quickie. If you want to work, surf, play and watch movies at the same time, use a CPU with 1 GHz or more and at least 768 MB RAM.
For your own sake.

• Pentium II CPU 350 MHz or higher
• 256 MB Ram , better 512 MB or more !
• BIG !!! harddisk, min. 50 GB for Emule temp + incoming together on a reserved partition on a 2nd internal harddisk, other shared files on additional partitions (also external possible), use of networkdrives not advised
• High speed internet connection via DSL-/ Cablemodem, Hard-/ Softwarerouter (ICS), Ethernet or Wireless LAN
  NO USB, Firewire, DSL modemcard, ISDN, analog modem, satellite or even more exotic connections !!!!!
• Network OS like 2000, XP (NT works), NOT Windows 95, 98, 98SE, ME !!!!
• A user who is both able and willing to use Google, read manuals and forum stickies completely, and reveals much more info in forum posts than just a poor "help me" !!
• The Emule client.
  Get the english original or a modified version only from the official website or its developer forum. All other versions are not supported there. You can easily end up with spyware or worse ...
• Additional information resources: Emule online manual, stickies in the developer forum, the changelog, links in the signature of forum menbers.

1.0 ISP Trouble

Many problems you experience with Emule originate at the choice of your internet service provider (isp).

Make sure you have an unrestricted internet connection !

Meaning : Your ISP assigns you a PUBLIC IP-address (abbr. IP), which is reachable from the internet, not a private IP-address, and you don't have to share it with a lot of other users (cf NAT, proxie).
If this is the case, you're effectively in a very big LAN with NO access to the router.

VERY BAD. You're stuck with LOWID, no matter what you try !

If you're unsure, don't hesitate to grill your ISP about this issue. Hey, they want your money, so you should get the real deal and not a cheap ripoff !

Change your ISP ASAP, if they make any trouble !

You can check your IP here : www.wieistmeineip.de or here : www.whatismyip.com .

Private IP-addresses (for LAN only):

10.0.0.0 to 10.255.255.255
172.16.0.0 to 172.31.255.255
192.168.0.0 to 192.168.255.255

1.2 Port-filtering/ Traffic-shaping/ Port-blocking

Make sure your ISP doesn't use any of these techniques to harass the innocent P2P user. Many reselling companies for big internet carriers use this to "convince" high-end users to leave.

Vigilant studying of the "terms of use" before signing the contract for your internet connection is highly recommended. Roam online forums like www.dslreports.com to get first-hand experiences from other users !

1.3 High Transfer Volume

Same problem here with resellers and high transfer volume users.

Solution: Use big carriers as your ISP.
They usually don't block/shape p2p-usage and don't care about high transfer volumes.

They own those damn pipes.

2.0 LAN/Router

The next common area of trouble are internet connections via home routers or LANs.

2.1 Portforwarding

• Use a FIXED PRIVATE LAN IP, NO DHCP for your Emule PC -> Emule_IP
  
• For incoming connections forward the ports your Emule client is using to the SAME ports of the LAN IP your Emule client is running on. Do this for each Emule client. If you're using more than one client, make sure EACH Emule client uses a DIFFERENT set of ports, no matter if they are running on different machines or all on one.
  
  Forwarding rules (portnames see Emule settings 4.1):
  
  Forward
  
  - INCOMING TCP FROM ANY_IP on TCPPort, WEBPort, MobilePort
  - INCOMING UDP FROM ANY_IP on UDPPort, ServerUDPPort
  
  TO Emule_IP and EXACTLY the same ports
  
  You can find info on portforwarding for various routers here : www.portforward.com
   
• Firewall rules for your router:
  
  - ALLOW INCOMING TCP/UDP FROM ALL_IP on TCPPort, WEBPort, MobilePort and UDPPort, ServerUDPPort
  - ALLOW ALL OUTGOING TCP/UDP FROM Emule_IP TO ANY_IP
   
• If your router is blocking ICMP or can't forward ICMP, the current USS (upload speed sense) implementation in Emule might cause some trouble.
  
  Otherwise
  
  - Forward INCOMING ICMP 0,3,11 FROM ANY_IP TO Emule_IP
  - ALLOW OUTGOING ICMP 8 FROM Emule_IP TO ANY_IP
  
  to allow USS to work.
  

Remember: ALL connections have to pass your router !

back to top

2.2 Max. Connections

Most LAN/W-LAN/DSL/cable-routers can handle only a small number of simultaneous internet connections (usually around 200-250).

• Make sure, the combined number of connections of all your Emule clients does not exceed this limit at any time.
  
• You can avoid this limitation by using an old P1 or P2 computer with Smoothwall (www.smoothwall.org) or IPCop (www.ipcop.org) as a powerful router with firewall and IDS. Perhaps you have an old machine lying around somewhere.

3.0 Client Computer

Now we are closing in on the troublemaking pc itself.

3.1 Networkcard (NIC) - Driver

Use up-to-date drivers for all your NIC's.

The default Windows drivers are mostly outdated and have problems coping with the number of network connections Emule is able to use. Problematic drivers can trigger the unpleasant "blue screen of death" "IRQ NOT LESS OR EQUAL", crashing Windows right when Emule is running fast.

To be able to update your network drivers, you first have to know your currently used network-chipset  and/or -manufacturer. If you have no user manual, the only way to be sure is opening your computer case and look for yourself. Don't trust your OS too much. Sometimes it doesn't recognize your NIC correctly and therefore installs wrong or 'far from optimal' network drivers.

Once you know your NIC's chipset, try Google or websites like www.driverguide.com to get up-to-date drivers for your OS.

3.2 DSL Driver

If you are NOT behind a router and connect to the internet via DSL-modem (pppoe):

With this type of connection the up- and downloading bandwidth are NOT independent. To upload with your maximum bandwidth and download with reasonable speed at the same time, or the other way around, use a trafficshaping tool like CfosSpeed (aka CFOS) (www.cfos.de). A good alternative to the standard Windows dsl-driver is raspppoe (www.raspppoe.com). Instead of using CfosSpeed you can use the USS (upload speed sense) function of Emule.

Both (CfosSpeed and USS) may work together or not. Try !

3.3 Minimizing Running Operating System Services

Warning: Not for complete noobs !

This is going to save memory and cpu resources and most importantly : you will have far less compatibility and security problems.

General rule: If you don't need a service, shut it down completely when possible !

For a comprehensive guide on OS-services, which ones you need and which not, look at www.blackviper.com.

In case this is too complicated for your liking, www.dingens.org, www.ntsvcfg.de offer tools for Win2000/XP, doing most (but not all) of the configurations for you. Still, very handy.

3.4 Closing Open Ports

Warning: Not for complete noobs !

If you're NOT behind a router, you're exposing your computer directly to the "wild" internet with lots of "open by default" ports. You can check it out here: https://grc.com/x/ne.dll?bh0bkyd2 or here: http://scan.sygate.com.
Even if you're already using a firewall to protect yourself, it might not work correctly if it is badly configured. Or you may have shut it down/disabled it either by choice or accident. So, closing those ports in the first place is always a good idea !

My favourite guide for this task is here: http://www.hsc.fr/ressources/breves/min_srv_res_win.en.html.en

After that there should be NO open ports left, but better check it again.

3.5 Firewall And IP-Filter (On Emule-Client PC)

After performing 3.3 and 3.4 there are only two firewall related issues left:

• blocking unwanted outgoing network traffic
  (viruses and trojans, privacy issues (microsoft, adware, spyware), unlicensed software calling home )
  
  My personal favorite for this job is Kerio personal firewall 2.1.5 (old, but small, fast, does its job and nothing else and is FREEWARE). Of course there are others like Sygate, Outpost, Kerio 4.x, Tiny , but they don't suit me. They tend to slow down network traffic and can't handle as many connections as Kerio 2.1.5 can.
  
  You'll find an excellent guide on configuring the Kerio 2.1.5 firewall for your personal needs here: http://www.dslreports.com/forum/remark,8023708~mode=flat
  (more good English links needed !)
  
  There are a few personal firewalls, which are known for causing many problems when used together with Emule (and other p2p). Avoid long frustrating troubleshooting by not using them or other related products, based on them, at all (ZoneAlarm, Nvidia firewall).
   
  For the configuration of your personal firewall there are 2 common cases:
   
1. You're running Emule on a standalone computer with an application based firewall like Sygate, Kerio/Tiny or Outpost without router. The firewall ruleset for Emule is :
 
• ALLOW ALL OUTGOING TCP/UDP TO ANY_IP for Emule.exe
• ALLOW OUTGOING ICMP 0,3,11 TO ANY_IP
• ALLOW INCOMING TCP FROM ANY_IP on TCPPort, WEBPort, MobilePort for Emule.exe
• ALLOW INCOMING UDP FROM ANY_IP on UDPPort, ServerUDPPort for Emule.exe
• ALLOW INCOMING ICMP 8 FROM ANY_IP
   
2. You're running Emule behind a router. It's a little bit more work then:
 
• Use a static LAN-IP out of f.e. 192.168.0.1-254 for your client-pc: Emule_IP
• Configure the ROUTER_IP also out of 192.168.0.1-254, but different from your Emule_IP ! and use it as standard gateway and DNSserver on your client-pc.
  
• On your router forward the ports ( see 2.1 ) you chose for Emule ( see 4.1 ) to the Emule_IP (refer to your manual for guidance on forwarding ports specifically with your router)
• If your router is capable, also forward incoming ICMP 8 to the Emule-IP and allow outgoing ICMP 0,3,11.
• The only firewall rule on your Emule pc is then:
  
  ALLOW ALL INCOMING/OUTGOING TCP/UDP/ICMP TO/FROM ANY_IP for Emule.exe
   


• blocking network traffic with unfriendly IP's
  (copyright goons, gov, mil, you get what I mean )
  
  You have to use specialized tools, because most personal firewalls are not up to this.
  
  The most up-to-date IP-blocklist for this purpose is maintained at http://bluetack.co.uk. With the Blocklistmanager you can convert it into a filterlist for Protowall or your p2p-software (Emule) or both.
  
  By the by : Check carefully, if your own IP is being blocked by this IP-blocklist. It is far from being perfect, some IP-ranges are really big and some might even accidentally block "innocent" filesharers like yourself.
  
  To make things even more complicated many servers are using IP-blocklists from various sources as well. It is possible you can not connect to a server, because of this. Usually there is a message like "Error - your IP is part of ipfilter.dat" is the serverlog when this happens.
  
  If your IP is blocked by the IP-blocklist from Bluetack, you can do at least something:
  1. Load ALL blocklists with the Blocklistmanager
  2. Search for fitting IP-ranges in the lists
  3. Post the troublemaking list and IP-range in the Bluetack forum.
  4. Pray, this range is quickly processed.
  5. Pray, other users and server are updating their blocklists quickly.
  
  On blocklists from other sources you are on your own.
  So, better check twice !
  
  To sum it up, by using an IP-filterlist you can lose some of your sources and it does not provide complete protection at all.
  
  But it is certainly better than nothing.

3.6 "Hardening" The TCP-Stack

Warning: Not for complete noobs !

There are tools and guides to change the standard network configuration, for your computer to be less vulnerable against many common attacks (like DOS), even without a firewall. Consider this only if you are able to repair any problems yourself, because this requires the manual changing of registry settings.

http://www.sniff-em.com/harden-it.shtml Automatic tool : Harden-it
Microsoft:
http://support.microsoft.com/kb/324270/en-us/ Windows Server 2003
http://support.microsoft.com/kb/315669/en-us/ Windows 2000/XP
http://www.microsoft.com/technet/security/topics/Serversecurity/tcg/tcgch00.mspx Threats and Countermeasures
Other:
http://www.winguides.com/registry/display.php/1237/

4.0 Emule

Now we finally arrive at the application in question.

4.1 Ports

So the whole set of used ports is:

• TCPPort -> set in Preferences
• UDPPort -> set in Preferences
• ServerUDPPort -> set in preferences.ini
  (Standard: random, choose a fixed value when using a router)
  
  and ONLY IF NEEDED:
  
• WEBPort (TCP) -> set in Preferences
• MobilePort (TCP) -> set in Preferences

When using a router, those ports have to be forwarded (2.1).

My personal choice for the first three ports is on my system 55, 56, 57.

This way most users with a 'bad ISP' (see portblocking) can still connect to my Emule without problems. Ports below 1024 are usually left untouched by ISP's. On a Windows NT/2000/XP pc you can find a list of ports and their common use in this textfile :

WINDOWS\system32\drivers\etc\services .

Just be sure you don't choose a port which is already being used on your computer.
In such a case, you will see an errormessage in the serverlog:
Fatal Error: Unable to create socket on port xxxx

Tools to help you include: ActivePorts (www.protect-me.com/freeware.html), TCPView (www.sysinternals.com/Utilities/TcpView.html), X-Netstat (www.freshsw.com) or "netstat" in the Windows commandconsole.

If it is too difficult for you to decide which ports below 1024 to use, you can choose ports over 10000 more freely. Those are often used for online games.

In theory any port between 1 and 65535 is possible.

4.2 Preferences/ Tips

• Max. connections: 150-200 are enough (for all Emule clients combined if you're using a router !)
• Max. new connections per 5 seconds : 5-10 for people with low cost routers and 30-40 for others.
  Some routers are capable of much more. You should know yourself, what you are doing in that case.
• Upload limit : either a fixed limit of 80% of your maximum upload capacity, or no limit and USS enabled.
  Under no circumstances no upload limit AND USS disabled !
  (If you don't know your line capacities, use online-speedtests on www.speedguide.net or www.dslreports.com, exit Emule for reliable results !)
• Try to gather 2000 - 4000 available sources (not more!)
  Play with max. sources per file and running downloads.
• Use a large upload queue size for the credit system working effectively. Rejecting clients due to a full queue unnecessarily increases upload overhead, which can't be used for uploading real data anymore.
• Disable the credit system if you want to release rare files AND download something else at the same time
• Due to the waiting time in long queues and your limited upload capability, all ed2k-clients usually need a few days to build up speed (including Emule).
  The most important tip is therefore: STAY ONLINE 24/7
  In case you need to break your internet connection for any reason, keep it short (about 30 minutes). Your client has to contact it's sources at regular intervals to keep its place in their upload queue.

4.3 Server

Lately there is an increasing number of fake servers appearing in the ed2k-network, spying on users, spreading fake search results and sources. There are countermeasures to avoid these servers. Time will tell, how effective they really are:

Razorback 2.0 and 2.1 are gone as of Feb. 23rd.
Now all Razorback servers are fake !

The procedure itself hasn't changed, only the source of a clean server list:

1. Delete server.met or delete all servers in your server list, if Emule is running.
2. In the server-preferences disable "update server list when a client connects".
3. Enable "autoconnect to servers in static list only".
4. Enable "don't remove static server".
5. Load a clean server list either manually with ed2k://|serverlist|http://corpo.free.fr/server.met|/ or add http://corpo.free.fr/server.met to addresses.dat as only entry.
6. Enable "auto-update server list at startup".
7. Choose 5-10 servers you trust as static servers.
8. Get a new and up-to-date IP-filterlist from Bluetack once a week.
9. Reload the IP-filterlist in security-preferences and enable "filter servers too".

4.4 Kademlia

The Kademlia-implementation (serverless network) in the current Emule-clients (.47) has reached a point to be a very good alternative to the old serverbased network. Users with enough upload-bandwidth (min. 128 KBit) can use both systems simultaneously.

Users with routers or USB-devices might run into problems, though. Often they are not able to use KAD.

Some "security" applications like ZoneAlarm or the "worm protection" in Norton products can cause havoc as well.

5.0 Remarks

Those recommendations are based on my own experiences with my Emule client-usage and internet connection since 2002 and the help of other users.
Your own experiences might differ from that. To be sure, your have to try it by yourself.

And thanks go to (in alphabetical order, just to be fair):
Anabolic-Frolic, Ashrak, crf, dani_555, fluke667, fractal.design, leuk_he, Paingiver, sauberesocke, SYS 64738, Unyure, xscarab, ...

Comments, corrections, suggestion, additions, ... are welcome.
Send a PM to qm2003 in the official Emule forum http://forum.Emule-project.net.

This checklist may be copied and quoted freely, as long as the author "qm2003" is referred to and a link to http://home.arcor.de/qm2003 is set. A short notice (mailto:qm2003@arcor.de) is eligible, but not mandatory.

last updated: March 06 2006