aMule shares code with the eMule Project and includes no adware or spyware as is often found in proprietary P2P applications. The credit and partial downloads files from eMule can be used by aMule and vice versa, making program substitution simple.
According to the aMule official FAQ, these are the default ports. Server ports 4661 TCP and 4665 UDP are only used by the EDonkey network. Therefore, the Kad Network will only use 4662 TCP and 4672 UDP. The traffic direction is from client perspective:
4661 TCP (outgoing): Port on which an eDonkey server listens for connection (port number may vary depending on eDonkey server used).
4662 TCP (outgoing and incoming): Client to client transfers.
4665 UDP (outgoing and incoming): Used for global eDonkey server searches and global source queries. This is always Client TCP port + 3.
aMule can be compiled using -disable-monolithic parameter: this allows aMule to be run in a modular way. This means that the core functionalities of the program can be started using amuled, the aMule daemon while the software behavior can be controlled through three different interfaces:
The command-line aMule client.
The regular GUI of the software. Experimental, a lot of features missing in comparison with the monolithic version and is unstable. There are Linux and Windows version for this tool: users can connect an aMule instance running on Linux from a workstation running Windows and the Win32 version of aMuleGUI.
The web interface provided by the aMule core built-in Webserver. It can be Retrieved the LAN or from the Internet, provided that any Internet router is properly configured using port forwarding.