Difference between revisions of "I2P"

From ArchWiki
Jump to: navigation, search
m (Usage)
m (add zh-hans)
 
(21 intermediate revisions by 14 users not shown)
Line 1: Line 1:
 
[[Category:Networking]]
 
[[Category:Networking]]
From the I2P homepage:
+
[[ja:I2P]]
:''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.''
+
[[ru:I2P]]
 +
[[zh-hans:I2P]]
 +
From the [https://geti2p.net/en/ 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.''
+
:Many applications are available that interface with I2P, including mail, peer-peer, IRC chat, and others.
  
 
== Installation ==
 
== Installation ==
I2P is available in the [[AUR]], with {{aur|i2p}} providing compilation from source, and {{aur|i2p-bin}} providing a precompiled binary.
+
I2P is available with the {{AUR|i2p}} package providing compilation  
 +
from source, and the {{AUR|i2p-bin}} package providing a precompiled binary; both of which require a [[Java]] Runtime Environment,  OpenJDK is fine, for the ARM platform Oracle Java is recommended.
  
== Usage ==
+
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.
  
First, invoke the i2prouter daemon:
+
Should these Java implementations be undesirable; {{AUR|i2pd}} is a full C++ client, which may suit hardware with limited resources.
  
'''SysV'''
+
== Usage ==
/etc/rc.d/i2prouter start
 
(add i2prouter to the DAEMONS array in your {{ic|/etc/rc.conf}} to start at boot)
 
  
'''systemd'''
+
First, [[start]] and optionally also enable the
systemctl start i2prouter.service
+
{{ic|i2prouter.service}}.
(issue ''systemctl enable i2prouter.service'' to start at boot)
 
  
This will launch the daemon under the system user 'i2p'. Next, open your browser of choice and visit the I2P welcome page at
+
This will launch the daemon under the system user {{ic|i2p}}. Next, open your browser of choice and visit the I2P welcome page at
  
 
  127.0.0.1:7657/home
 
  127.0.0.1:7657/home
  
From here you can navigate to I2Ps configuration and statistics pages, and links to "Eepsites of Interest" (eepsites being sites 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.
+
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 {{ic|.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.
  
To enable the use of outproxies, use the following browser settings:
+
In order to visit eepsite's configure your browser to use the local http proxy (not socks):
  
 
  HTTP  127.0.0.1 4444
 
  HTTP  127.0.0.1 4444
 
  HTTPS 127.0.0.1 4445
 
  HTTPS 127.0.0.1 4445
  
==External Links==
+
== Eepsite ==
 +
 
 +
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 {{ic|/opt/i2p}} as shown in the AUR [https://aur.archlinux.org/cgit/aur.git/tree/i2p.install?h=i2p i2p.install] file.
 +
 
 +
== See also ==
  
 
* [http://www.i2p2.de I2P Homepage]
 
* [http://www.i2p2.de I2P Homepage]
 
* [http://www.i2p2.de/faq.html I2P FAQ]
 
* [http://www.i2p2.de/faq.html I2P FAQ]
 
* [http://www.i2pproject.net Homepage mirror]
 
* [http://www.i2pproject.net Homepage mirror]
* [http://en.wikipedia.org/wiki/I2p I2P Wikipedia entry]
+
* [[wikipedia:I2p|I2P Wikipedia entry]]

Latest revision as of 06:38, 12 November 2017

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.

Installation

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.

Usage

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

127.0.0.1:7657/home

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  127.0.0.1 4444
HTTPS 127.0.0.1 4445

Eepsite

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