From ArchWiki
Jump to navigation Jump to search

From the I2P homepage:

I2P is an anonymizing network, offering a simple layer that identity-sensitive applications can use to securely communicate. All data is wrapped with several layers of encryption, and the network is both distributed and dynamic, with no trusted parties.
Many applications are available that interface with I2P, including mail, peer-peer, IRC chat, and others.


I2P is available with the i2pAUR package providing compilation from source, and the i2p-binAUR package providing a precompiled binary; both of which require a Java Runtime Environment, OpenJDK is fine, for the ARM platform Oracle Java is recommended.

The I2P homepage also provides a precompiled binary package for command line (headless) install in the users home directory. In case of this installation type I2P will auto update itself through the i2p network.

Should these Java implementations be undesirable; i2pdAUR is a full C++ client, which may suit hardware with limited resources.


First, start and optionally also enable the i2prouter.service.

This will launch the daemon under the system user i2p. Next, open your browser of choice and visit the I2P welcome page at

From here you can navigate to I2Ps configuration and statistics pages, and links to "Eepsites of Interest" (an w:eepsite being a site available only through the I2P network, similar to how .onion sites are only available through the Tor network). Also, be aware that eepsites are unavailable until the daemon has bootstrapped to the network, which can take several minutes.

In order to visit eepsite's configure your browser to use the local http proxy (not socks):

HTTP 4444
HTTPS 4445


If you make an eepsite, follow the I2P instructions, but keep in mind that the home directory will apply to the i2p user whose home directory is /opt/i2p as shown in the AUR i2p.install file.

See also