I2P

From ArchWiki
Jump to navigation Jump to search

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.

Installation

Install the i2pd package for the daemon written in C++ which may suit hardware with limited resources or i2pd-gitAUR for the development version.

The standard I2P suite is available with the i2pAUR and i2p-binAUR packages. Both require a Java Runtime Environment (i.e. OpenJDK). Oracle Java is recommended for the ARM platform.

The I2P homepage also provides a pre-compiled binary which includes command line (headless) option and can be installed in the user's home directory. In this case I2P will auto update itself through the i2p network.

Usage

If you installed i2pd, you will have to start and optionally also enable the i2pd.service at this point. The configuration for the daemon is made in /etc/i2pd/i2pd.conf. If i2p was installed, you will have to start and optionally enable the i2prouter.service instead.

Open your browser of choice and visit the I2P welcome page at 127.0.0.1:7070 or 127.0.0.1:7657 for the suite (see the FAQ). From here you can navigate to I2Ps configuration and statistics pages, and links to Eepsites. Also, be aware that eepsites are unavailable until the daemon has bootstrapped to the network, which can take several minutes.

In order to visit eepsites configure your browser to use the local proxy:

HTTP  127.0.0.1 4444
SOCKS 127.0.0.1 4447

Eepsite

To 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.

For the daemon see [1].

See also