I2P

The Invisible Internet Project (I2P).

Prerequisites
Java 7 or higher must be installed. See the Java article for more instructions on how to get the system to that point.

The is currently marked as unstable. Special permission must be granted for it to install on stable systems:

Or:

OpenRC
To start the i2p service when the system boots:

To start the i2p service now:

systemd
To start the i2p service when the system boots:

To start the i2p service now:

Configuration
Most I2P configuration is done in the Router Console, accessible via web browser at  once the router service has been started.

Firewall
I2P selects a random port between 9000 and 31000 for inbound traffic when the router is first run. This port is forwarded automatically by UPnP, but if your gateway/firewall does not support UPnP, it will need to be manually forwarded (both TCP and UDP) for best performance. Visit http://localhost:7657/confignet to find out which port.

Eepsites
To access websites hosted on the I2P network, a web browser must be configured to use a proxy at  for HTTP and   for HTTPS. This can be accomplished globally in most browsers' proxy settings, or specifically for sites with the .i2p TLD using a plugin like FoxyProxy for Firefox or Chrome See also: https://geti2p.net/en/about/browser-config

Bittorrent
I2PSnark, the I2P Bittorrent client, is accessible at  with no additional configuration. However, the above Eepsite configuration is necessary to reach the trackers on which the torrents are found.

IRC
Using any IRC client, set up a connection to No account creation is required. If using Pidgin, be sure to fill in the Ident name and Real name fields in addition to Username, otherwise Pidgin may expose identity information from other configured accounts.