I2P

The Invisible Internet Project (I2P) is Article description::an anonymous network, similar to [[Tor.]] The key difference is that I2P is internal, focusing on providing anonymous services within the network rather than proxying traffic to the regular internet (although some proxy services do exist).

Prerequisites
Java 7 or higher must be installed to run the main implementation of I2P. See the Java article for more instructions on how to get the system to that point. If this is not possible, try the newer but less mature C++ implementation:.

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

i2pd (C++)
is also marked as unstable:

Services
examples below are for java implementation of the i2p. If you are using c++ version, substitute i2p for i2pd.

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.

Default configuration for ip2d is available at.

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.

Browser
You can use a pac file to delegate browser requests to different proxies. Here connections to localhost are handled directly (no proxy). Eepsites are handled by I2P proxy on port 4444. Other traffic goes via Tor SOCKS proxy on running on port 9050.

Save this file as, and point your browser to it. Most browsers accept Proxy configuration URL, where you can specify.

I2P's CSS can make browsers sluggish. You can add the following to your to speed up rendering:

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.

SSH
openssh doesn't have any native support for SOCKS5, so you will need to install openbsd-netcat. You'll need to modify your SSH config too. It is possible with ''netcat' also but the configuration below uses flags specific to the OpenBSD variant.

This enables proxying through a SOCKS5 I2P tunnel for all .i2p hosts. You will need to go to http://localhost:7657/i2ptunnelmgr and create a SOCKS5 client tunnel. Note the port you have used and replace '1234' in the below config with it.