I2P 0.9.23
THE INVISIBLE INTERNET PROJECT
What does I2P do for you?
The I2P network provides strong privacy protections for communication over the Internet. Many activities that would risk your privacy on the public Internet can be conducted anonymously inside I2P.
What is I2P?
I2P is an anonymous overlay network - a network within a network. It is intended to protect communication from dragnet surveillance and monitoring by third parties such as ISPs.
I2P is used by many people who care about their privacy: activists, oppressed people, journalists and whistleblowers, as well as the average person.
No network can be "perfectly anonymous". The continued goal of I2P is to make attacks more and more difficult to mount. Its anonymity will get stronger as the size of the network increases and with ongoing academic review.
I2P is available on desktops, embedded systems (like the Raspberry Pi) and Android phones. Help spread the word!
The Invisible Internet Project (I2P)
I2P is an anonymous network, exposing a simple layer that applications can use to anonymously and securely send messages to each other. The network itself is strictly message based (a la IP), but there is a library available to allow reliable streaming communication on top of it (a la TCP). All communication is end to end encrypted (in total there are four layers of encryption used when sending a message), and even the end points ("destinations") are cryptographic identifiers (essentially a pair of public keys).
How does it work?
To anonymize the messages sent, each client application has their I2P "router" build a few inbound and outbound "tunnels" - a sequence of peers that pass messages in one direction (to and from the client, respectively). In turn, when a client wants to send a message to another client, the client passes that message out one of their outbound tunnels targeting one of the other client's inbound tunnels, eventually reaching the destination. Every participant in the network chooses the length of these tunnels, and in doing so, makes a tradeoff between anonymity, latency, and throughput according to their own needs. The result is that the number of peers relaying each end to end message is the absolute minimum necessary to meet both the sender's and the receiver's threat model.
The first time a client wants to contact another client, they make a query against the fully distributed "network database" - a custom structured distributed hash table (DHT) based off the Kademlia algorithm. This is done to find the other client's inbound tunnels efficiently, but subsequent messages between them usually includes that data so no further network database lookups are required.
More details about how I2P works are available.
What can you do with it?
Within the I2P network, applications are not restricted in how they can communicate - those that typically use UDP can make use of the base I2P functionality, and those that typically use TCP can use the TCP-like streaming library. We have a generic TCP/I2P bridge application ("I2PTunnel") that enables people to forward TCP streams into the I2P network as well as to receive streams out of the network and forward them towards a specific TCP/IP address.
I2PTunnel is currently used to let people run their own anonymous website ("eepsite") by running a normal webserver and pointing an I2PTunnel 'server' at it, which people can access anonymously over I2P with a normal web browser by running an I2PTunnel HTTP proxy ("eepproxy"). In addition, we use the same technique to run an anonymous IRC network (where the IRC server is hosted anonymously, and standard IRC clients use an I2PTunnel to contact it). There are other application development efforts going on as well, such as one to build an optimized swarming file transfer application (a la BitTorrent), a distributed data store (a la Freenet / MNet), and a blogging system (a fully distributed LiveJournal), but those are not ready for use yet.
I2P is not inherently an "outproxy" network - the client you send a message to is the cryptographic identifier, not some IP address, so the message must be addressed to someone running I2P. However, it is possible for that client to be an outproxy, allowing you to anonymously make use of their Internet connection. To demonstrate this, the "eepproxy" will accept normal non-I2P URLs (e.g. "http://www.i2p.net") and forward them to a specific destination that runs a squid HTTP proxy, allowing simple anonymous browsing of the normal web. Simple outproxies like that are not viable in the long run for several reasons (including the cost of running one as well as the anonymity and security issues they introduce), but in certain circumstances the technique could be appropriate.
The I2P development team is an open group, welcome to all who are interested in getting involved, and all of the code is open source. The core I2P SDK and the current router implementation is done in Java (currently working with both sun and kaffe, gcj support planned for later), and there is a simple socket based API for accessing the network from other languages (with a C library available, and both Python and Perl in development). The network is actively being developed and has not yet reached the 1.0 release, but the current roadmap describes our schedule.
What can you do with I2P?
Email: Integrated web mail interface, plugin for serverless email.
Web browsing: Anonymous websites, gateways to and from the public Internet.
Blogging and forums: Blogging and Syndie plugins.
Website hosting: Integrated anonymous web server.
Real-time chat: Instant messaging and IRC clients.
File sharing: ED2K and Gnutella clients, integrated BitTorrent client.
Decentralized file storage: Tahoe-LAFS distributed filesystem plugin.
SUPPORTED APPLICATIONS
Blogging, Forums, and Wikis
Decentralized File Storage
Development Tools
Version control
Domain Naming
Email
File Sharing
BitTorrent clients
BitTorrent trackers and indexers
ED2K
Gnutella
Network Administration
General-purpose socket utilities
SSH/SCP/SFTP
Real-time Chat
Instant messaging clients
IRC clients
IRC servers
Web Browsing
Anonymous websites
Proxy software
Inproxies
Outproxies
Website Hosting
Web servers
This is intended to be a comprehensive listing of applications used with I2P. If you know of something that's missing please submit a ticket on Trac, and be sure to select the “www” component in the submission form.
Supported applications are tagged with one or more of the following:
bundled
Bundled application — I2P ships with a few officially supported applications that let new users take immediate advantage of some of I2P's more useful capabilities.
plugin
Third-party plugin — I2P's plugin system provides convenient deployment of I2P-enabled applications and allows tighter integration with the router. Plugins are [reviewed by the community](http://plugins.i2p.xyz) to identify security and anonymity issues.
standalone, standalone/mod
Third-party standalone application — Many standard network applications only require careful setup and configuration to communicate anonymously over I2P. These are tagged with standalone. Some applications, tagged with standalone/mod, require patching to function properly over I2P or to prevent inadvertent disclosure of identifying information such as the user's hostname or external IP address.
service
Third-party essential network service — Services which on the I2P network are analogous to those provided on the public Internet by hosting providers, ISPs, and Google: eepsite indexes and jump services, search engines, email, DNS-style name services, hosting, proxies, etc. These services focus on boosting the usefulness of the network as a whole, and making network content more discoverable.
unmaintained
Unmaintained — This is used to tag plugins, applications, and services which appear to be unmaintained and may be removed from this listing in the future.
Warning: Using an application, plugin, or service with I2P doesn't automatically protect your anonymity. I2P is merely a set of tools which can help you mitigate certain identified threats to anonymity. We do not and cannot make any guarantees about the safety of the applications, plugins, and services listed below. Most applications and plugins must be properly configured, and some will need to be patched — and even then your anonymity might not be assured. Similarly, services could put your anonymity at risk, either by design or through carelessness on their part or your own.
If you have doubts about the suitability of an application, plugin, or service for use with I2P, you are urged to inquire about privacy issues with its maintainers, to search its mailing lists and bug tracker if one exists, and consult trusted, knowledgeable members of the I2P community.
Take responsibility for your own anonymity and safety — always seek expert advice, educate yourself, practice good judgment, be mindful of disclosing personally identifying information, and don't take shortcuts.
Blogging, Forums, and Wikis
El Dorado — Lightweight forum software. [standalone/mod]
Pebble — Another lightweight blogging platform. [plugin, standalone/mod]
phpBB — Most popular open source forum software. [standalone/mod]
Syndie — Distributed forums software, originally developed by jrandom. [plugin, standalone, unmaintained]
JAMWiki — A Java-based MediaWiki clone. No external database needed. Plugin available here. [standalone, plugin]
Decentralized File Storage
Tahoe-LAFS-I2P — Port of the Tahoe-LAFS distributed file system to the I2P network. Controller plugin here. [plugin, standalone]
Development Tools
Version control
Git — Most popular distributed version control system. [standalone]
Monotone — Another distributed version control system. Currently used in I2P development. [standalone]
Domain Naming
susidns — Provides management of addressbooks, which are part of a simple, user-controlled I2P naming system somewhat analogous to the Internet's Domain Name System (DNS). Addressbooks map Base64 destinations to short, usually human-readable “domain” names ending with a .i2p suffix which the I2P router's HTTP client can resolve back to Base64 addresses. (Note: While Base64 destinations are globally unique, addressbook “domain” names only resolve to unique destinations locally.) [bundled]
Email
I2P-Bote — Serverless peer-to-peer email application using a distributed hash table (DHT) for secure mail storage. [plugin]
Postman's anonymous email service — Provides email service within the I2P network via @mail.i2p addresses, and email gateway service between the I2P network and the public Internet via @i2pmail.org addresses. One of the oldest continuous services on I2P. [service]
susimail — Simple web browser-based email interface. Configured to use Postman's email service by default. [bundled]
Sylpheed Claws, Thunderbird, other MUAs — Can be configured to use Postman's email service. See this comparison of MUAs, and configuration settings for SMTP and POP3. [standalone]
File Sharing
BitTorrent clients
I2PSnark — I2P's integrated BitTorrent client. [bundled]
I2PSnarkXL — Modified version of I2PSnark. [standalone]
Robert — A fork of rufus that uses the Basic Open Bridge (BOB) and has many improvements, including using the latest wxwidgets and python. It also supports use of seedless if installed for trackerless torrents and magnet-link like fetching of torrents within I2P. [standalone]
Transmission — Clean, full-featured cross-platform BitTorrent client with official ports for several GUI toolkits. [standalone/mod]
Azureus/Vuze — Has a plugin providing I2P support. [standalone, unmaintained]
BitTorrent trackers and indexers
For a detailed feature comparison of I2P-enabled trackers/indexers, see here.
Bytemonsoon — The code that powered one of the first major tracker/indexer sites on the Internet. Patched for I2P. [standalone/mod]
opentracker — Lightweight tracker/indexer. I2P mod available in the i2p.opentracker branch of the I2P Monotone repository. [standalone/mod]
zzzot — zzz's Java-based open tracker. More info here. [plugin]
ED2K
iMule — I2P port of the aMule ED2K client. [standalone]
Gnutella
I2Phex — Port of the Phex Gnutella client. Website for plugin version here. [plugin, standalone]
jwebcache — Cache for Gnutella peers on I2P. Website for plugin version here. [plugin, standalone]
Network Administration
General-purpose socket utilities
netcat — Unix standard tool for socket relaying. Several clones, ports, and forks have appeared over the years. [standalone]
socat — Like netcat but more powerful. [standalone]
tsocks — Proxy providing simple, transparent SOCKS-ification of network applications. [standalone]
SSH/SCP/SFTP
OpenSSH — Most popular implementation of the Secure Shell (SSH) protocol and related tools. [standalone]
PuTTY — Open source Secure Shell (SSH) client for Windows. [standalone]
Real-time Chat
Instant messaging clients
I2P Messenger — IM client with multiple incarnations. [standalone]
IRC clients
Many IRC clients leak identifying information to servers or other clients, so I2P's IRC and SOCKS IRC client tunnels filter certain inbound and outbound messages to scrub data such as LAN IP addresses, external IP addresses, local hostnames, and the name and version of the IRC client. Two message types in particular, DCC and CTCP, can't be sufficiently anonymized without changes to the protocols or to IRC client/server code, so they are completely blocked, except for CTCP ACTION (the message emitted by the /me command) which isn't inherently dangerous.
I2P's IRC filtering may not cover every possible leak — users should also check if their client is sending their real name or local username. Packet sniffers such as Wireshark are useful here. Eliminating remaining leaks may be as simple as changing the client's default configuration. If that doesn't help, inform the I2P developers; they may be able to solve it via additional filtering.
jIRCii — Small Java-based IRC client. Plugin available here. [plugin, standalone]
XChat — Cross-platform graphical IRC client. [standalone]
irssi — Unixy terminal-based IRC client. [standalone]
WeeChat — Another Unixy terminal-based IRC client. [standalone]
IRC servers
ngIRCd — IRC server developed from scratch. [standalone/mod]
UnrealIRCd — Most popular IRC server. [standalone/mod]
Web Browsing
Anonymous websites
Eepsites — Any website hosted anonymously on I2P, reachable through the I2P router's HTTP proxy. [service]
Deepsites — Distributed anonymous websites hosted using Tahoe-LAFS-I2P, currently only reachable with Tahoe-LAFS-I2P clients or through the Tahoe-LAFS-I2P HTTP proxy. [service]
i2host.i2p.xyz — Website for sponge's jump service. Source code available. [service]
i2jump.i2p.xyz — Another jump service. [service]
identiguy.i2p.xyz — Dynamically updated eepsite index. [service]
stats.i2p — Website for zzz's jump service. [service]
Proxy software
Polipo — SOCKS-enabled caching web proxy with basic filtering capabilities. [standalone]
Privoxy — Privacy-focused non-caching web proxy with advanced filtering capabilities. Excels at removing ads and other junk. [standalone]
Squid — Venerable caching web proxy. [standalone]
Inproxies
Gateways allowing users on the public Internet to access eepsites.
i2p.to — tino's inproxy on the public Internet. [service]
i2p.us — Another inproxy on the public Internet. [service]
i2p.me — Another inproxy on the public Internet. [service]
Outproxies
Gateways allowing I2P users to access content hosted on the public Internet.
false.i2p — Publicly advertised outproxy running Squid, located in Europe. [service]
Website Hosting
Jetty — Lightweight web server and Java servlet container. I2P is tightly integrated with a bundled copy of Jetty which by default is configured to host the user's eepsite. The bundled Jetty also serves the I2P router console and web applications bundled with I2P. [bundled, standalone]
Web servers
In addition to Jetty, any web server should function over I2P without modification so long as it's HTTP-compliant. Some web servers known to currently serve content on the I2P network are:
Apache HTTP Server — Most popular web server on the public WWW. [standalone]
Apache Tomcat — Web server and Java servlet container. More features than Jetty. [standalone]
lighttpd — Fast lightweight web server. [standalone]
nginx — High-performance lightweight web server. [standalone]
OS: Windows 2000/XP/2003/Vista/7/8/10
Post-install work
After running the installer on windows, simply click on the "Start I2P" button which will bring up the router console, which has further instructions.
On Unix-like systems, I2P can be started as a service using the "i2prouter" script, located in the directory you selected for I2P. Changing to that directory in a console and issuing "sh i2prouter status" should tell you the router's status. The arguments "start", "stop" and "restart" control the service. The router console can be accessed at its usual location. For users on OpenSolaris and other systems for which the wrapper (i2psvc) is not supported, start the router with "sh runplain.sh" instead.
When installing for the first time, please remember to adjust your NAT/firewall if you can, bearing in mind the Internet-facing ports I2P uses, described here among other ports. If you have successfully opened your port to inbound TCP, also enable inbound TCP on the configuration page.
Also, please review and adjust the bandwidth settings on the configuration page, as the default settings of 96 KBps down / 40 KBps up are fairly slow.
If you want to reach eepsites via your browser, have a look on the browser proxy setup page for an easy howto.
MAC OS X : Download the 0.9.23 OSX graphical installer file and run java -jar i2pinstall_0.9.23.jar
GNU/Linux/BSD/Solaris : Download the graphical installer file and run java -jar i2pinstall_0.9.23.jar
Packages for : Debian & Ubuntu are available.
Android :Outside I2P:
I2P 0.9.22
Inside I2P:
I2P 0.9.22
Google Play:
I2P 0.9.22
Our F-Droid repository:
I2P 0.9.22
F-Droid:
I2P 0.9.19
Development Builds:
str4d's eepsite
Requires Android 2.3 (Gingerbread) or higher. If you earlier installed I2P, you need to reinstall because we have also changed the release keys. 512 MB RAM minimum; 1 GB recommended. The release and dev versions of the I2P APK are not compatible, as they are signed by zzz and str4d respectively. Uninstall one before installing the other.
https://geti2p.net/en/
THE INVISIBLE INTERNET PROJECT
What does I2P do for you?
The I2P network provides strong privacy protections for communication over the Internet. Many activities that would risk your privacy on the public Internet can be conducted anonymously inside I2P.
What is I2P?
I2P is an anonymous overlay network - a network within a network. It is intended to protect communication from dragnet surveillance and monitoring by third parties such as ISPs.
I2P is used by many people who care about their privacy: activists, oppressed people, journalists and whistleblowers, as well as the average person.
No network can be "perfectly anonymous". The continued goal of I2P is to make attacks more and more difficult to mount. Its anonymity will get stronger as the size of the network increases and with ongoing academic review.
I2P is available on desktops, embedded systems (like the Raspberry Pi) and Android phones. Help spread the word!
The Invisible Internet Project (I2P)
I2P is an anonymous network, exposing a simple layer that applications can use to anonymously and securely send messages to each other. The network itself is strictly message based (a la IP), but there is a library available to allow reliable streaming communication on top of it (a la TCP). All communication is end to end encrypted (in total there are four layers of encryption used when sending a message), and even the end points ("destinations") are cryptographic identifiers (essentially a pair of public keys).
How does it work?
To anonymize the messages sent, each client application has their I2P "router" build a few inbound and outbound "tunnels" - a sequence of peers that pass messages in one direction (to and from the client, respectively). In turn, when a client wants to send a message to another client, the client passes that message out one of their outbound tunnels targeting one of the other client's inbound tunnels, eventually reaching the destination. Every participant in the network chooses the length of these tunnels, and in doing so, makes a tradeoff between anonymity, latency, and throughput according to their own needs. The result is that the number of peers relaying each end to end message is the absolute minimum necessary to meet both the sender's and the receiver's threat model.
The first time a client wants to contact another client, they make a query against the fully distributed "network database" - a custom structured distributed hash table (DHT) based off the Kademlia algorithm. This is done to find the other client's inbound tunnels efficiently, but subsequent messages between them usually includes that data so no further network database lookups are required.
More details about how I2P works are available.
What can you do with it?
Within the I2P network, applications are not restricted in how they can communicate - those that typically use UDP can make use of the base I2P functionality, and those that typically use TCP can use the TCP-like streaming library. We have a generic TCP/I2P bridge application ("I2PTunnel") that enables people to forward TCP streams into the I2P network as well as to receive streams out of the network and forward them towards a specific TCP/IP address.
I2PTunnel is currently used to let people run their own anonymous website ("eepsite") by running a normal webserver and pointing an I2PTunnel 'server' at it, which people can access anonymously over I2P with a normal web browser by running an I2PTunnel HTTP proxy ("eepproxy"). In addition, we use the same technique to run an anonymous IRC network (where the IRC server is hosted anonymously, and standard IRC clients use an I2PTunnel to contact it). There are other application development efforts going on as well, such as one to build an optimized swarming file transfer application (a la BitTorrent), a distributed data store (a la Freenet / MNet), and a blogging system (a fully distributed LiveJournal), but those are not ready for use yet.
I2P is not inherently an "outproxy" network - the client you send a message to is the cryptographic identifier, not some IP address, so the message must be addressed to someone running I2P. However, it is possible for that client to be an outproxy, allowing you to anonymously make use of their Internet connection. To demonstrate this, the "eepproxy" will accept normal non-I2P URLs (e.g. "http://www.i2p.net") and forward them to a specific destination that runs a squid HTTP proxy, allowing simple anonymous browsing of the normal web. Simple outproxies like that are not viable in the long run for several reasons (including the cost of running one as well as the anonymity and security issues they introduce), but in certain circumstances the technique could be appropriate.
The I2P development team is an open group, welcome to all who are interested in getting involved, and all of the code is open source. The core I2P SDK and the current router implementation is done in Java (currently working with both sun and kaffe, gcj support planned for later), and there is a simple socket based API for accessing the network from other languages (with a C library available, and both Python and Perl in development). The network is actively being developed and has not yet reached the 1.0 release, but the current roadmap describes our schedule.
What can you do with I2P?
Email: Integrated web mail interface, plugin for serverless email.
Web browsing: Anonymous websites, gateways to and from the public Internet.
Blogging and forums: Blogging and Syndie plugins.
Website hosting: Integrated anonymous web server.
Real-time chat: Instant messaging and IRC clients.
File sharing: ED2K and Gnutella clients, integrated BitTorrent client.
Decentralized file storage: Tahoe-LAFS distributed filesystem plugin.
SUPPORTED APPLICATIONS
Blogging, Forums, and Wikis
Decentralized File Storage
Development Tools
Version control
Domain Naming
File Sharing
BitTorrent clients
BitTorrent trackers and indexers
ED2K
Gnutella
Network Administration
General-purpose socket utilities
SSH/SCP/SFTP
Real-time Chat
Instant messaging clients
IRC clients
IRC servers
Web Browsing
Anonymous websites
Proxy software
Inproxies
Outproxies
Website Hosting
Web servers
This is intended to be a comprehensive listing of applications used with I2P. If you know of something that's missing please submit a ticket on Trac, and be sure to select the “www” component in the submission form.
Supported applications are tagged with one or more of the following:
bundled
Bundled application — I2P ships with a few officially supported applications that let new users take immediate advantage of some of I2P's more useful capabilities.
plugin
Third-party plugin — I2P's plugin system provides convenient deployment of I2P-enabled applications and allows tighter integration with the router. Plugins are [reviewed by the community](http://plugins.i2p.xyz) to identify security and anonymity issues.
standalone, standalone/mod
Third-party standalone application — Many standard network applications only require careful setup and configuration to communicate anonymously over I2P. These are tagged with standalone. Some applications, tagged with standalone/mod, require patching to function properly over I2P or to prevent inadvertent disclosure of identifying information such as the user's hostname or external IP address.
service
Third-party essential network service — Services which on the I2P network are analogous to those provided on the public Internet by hosting providers, ISPs, and Google: eepsite indexes and jump services, search engines, email, DNS-style name services, hosting, proxies, etc. These services focus on boosting the usefulness of the network as a whole, and making network content more discoverable.
unmaintained
Unmaintained — This is used to tag plugins, applications, and services which appear to be unmaintained and may be removed from this listing in the future.
Warning: Using an application, plugin, or service with I2P doesn't automatically protect your anonymity. I2P is merely a set of tools which can help you mitigate certain identified threats to anonymity. We do not and cannot make any guarantees about the safety of the applications, plugins, and services listed below. Most applications and plugins must be properly configured, and some will need to be patched — and even then your anonymity might not be assured. Similarly, services could put your anonymity at risk, either by design or through carelessness on their part or your own.
If you have doubts about the suitability of an application, plugin, or service for use with I2P, you are urged to inquire about privacy issues with its maintainers, to search its mailing lists and bug tracker if one exists, and consult trusted, knowledgeable members of the I2P community.
Take responsibility for your own anonymity and safety — always seek expert advice, educate yourself, practice good judgment, be mindful of disclosing personally identifying information, and don't take shortcuts.
Blogging, Forums, and Wikis
El Dorado — Lightweight forum software. [standalone/mod]
Pebble — Another lightweight blogging platform. [plugin, standalone/mod]
phpBB — Most popular open source forum software. [standalone/mod]
Syndie — Distributed forums software, originally developed by jrandom. [plugin, standalone, unmaintained]
JAMWiki — A Java-based MediaWiki clone. No external database needed. Plugin available here. [standalone, plugin]
Decentralized File Storage
Tahoe-LAFS-I2P — Port of the Tahoe-LAFS distributed file system to the I2P network. Controller plugin here. [plugin, standalone]
Development Tools
Version control
Git — Most popular distributed version control system. [standalone]
Monotone — Another distributed version control system. Currently used in I2P development. [standalone]
Domain Naming
susidns — Provides management of addressbooks, which are part of a simple, user-controlled I2P naming system somewhat analogous to the Internet's Domain Name System (DNS). Addressbooks map Base64 destinations to short, usually human-readable “domain” names ending with a .i2p suffix which the I2P router's HTTP client can resolve back to Base64 addresses. (Note: While Base64 destinations are globally unique, addressbook “domain” names only resolve to unique destinations locally.) [bundled]
I2P-Bote — Serverless peer-to-peer email application using a distributed hash table (DHT) for secure mail storage. [plugin]
Postman's anonymous email service — Provides email service within the I2P network via @mail.i2p addresses, and email gateway service between the I2P network and the public Internet via @i2pmail.org addresses. One of the oldest continuous services on I2P. [service]
susimail — Simple web browser-based email interface. Configured to use Postman's email service by default. [bundled]
Sylpheed Claws, Thunderbird, other MUAs — Can be configured to use Postman's email service. See this comparison of MUAs, and configuration settings for SMTP and POP3. [standalone]
File Sharing
BitTorrent clients
I2PSnark — I2P's integrated BitTorrent client. [bundled]
I2PSnarkXL — Modified version of I2PSnark. [standalone]
Robert — A fork of rufus that uses the Basic Open Bridge (BOB) and has many improvements, including using the latest wxwidgets and python. It also supports use of seedless if installed for trackerless torrents and magnet-link like fetching of torrents within I2P. [standalone]
Transmission — Clean, full-featured cross-platform BitTorrent client with official ports for several GUI toolkits. [standalone/mod]
Azureus/Vuze — Has a plugin providing I2P support. [standalone, unmaintained]
BitTorrent trackers and indexers
For a detailed feature comparison of I2P-enabled trackers/indexers, see here.
Bytemonsoon — The code that powered one of the first major tracker/indexer sites on the Internet. Patched for I2P. [standalone/mod]
opentracker — Lightweight tracker/indexer. I2P mod available in the i2p.opentracker branch of the I2P Monotone repository. [standalone/mod]
zzzot — zzz's Java-based open tracker. More info here. [plugin]
ED2K
iMule — I2P port of the aMule ED2K client. [standalone]
Gnutella
I2Phex — Port of the Phex Gnutella client. Website for plugin version here. [plugin, standalone]
jwebcache — Cache for Gnutella peers on I2P. Website for plugin version here. [plugin, standalone]
Network Administration
General-purpose socket utilities
netcat — Unix standard tool for socket relaying. Several clones, ports, and forks have appeared over the years. [standalone]
socat — Like netcat but more powerful. [standalone]
tsocks — Proxy providing simple, transparent SOCKS-ification of network applications. [standalone]
SSH/SCP/SFTP
OpenSSH — Most popular implementation of the Secure Shell (SSH) protocol and related tools. [standalone]
PuTTY — Open source Secure Shell (SSH) client for Windows. [standalone]
Real-time Chat
Instant messaging clients
I2P Messenger — IM client with multiple incarnations. [standalone]
IRC clients
Many IRC clients leak identifying information to servers or other clients, so I2P's IRC and SOCKS IRC client tunnels filter certain inbound and outbound messages to scrub data such as LAN IP addresses, external IP addresses, local hostnames, and the name and version of the IRC client. Two message types in particular, DCC and CTCP, can't be sufficiently anonymized without changes to the protocols or to IRC client/server code, so they are completely blocked, except for CTCP ACTION (the message emitted by the /me command) which isn't inherently dangerous.
I2P's IRC filtering may not cover every possible leak — users should also check if their client is sending their real name or local username. Packet sniffers such as Wireshark are useful here. Eliminating remaining leaks may be as simple as changing the client's default configuration. If that doesn't help, inform the I2P developers; they may be able to solve it via additional filtering.
jIRCii — Small Java-based IRC client. Plugin available here. [plugin, standalone]
XChat — Cross-platform graphical IRC client. [standalone]
irssi — Unixy terminal-based IRC client. [standalone]
WeeChat — Another Unixy terminal-based IRC client. [standalone]
IRC servers
ngIRCd — IRC server developed from scratch. [standalone/mod]
UnrealIRCd — Most popular IRC server. [standalone/mod]
Web Browsing
Anonymous websites
Eepsites — Any website hosted anonymously on I2P, reachable through the I2P router's HTTP proxy. [service]
Deepsites — Distributed anonymous websites hosted using Tahoe-LAFS-I2P, currently only reachable with Tahoe-LAFS-I2P clients or through the Tahoe-LAFS-I2P HTTP proxy. [service]
i2host.i2p.xyz — Website for sponge's jump service. Source code available. [service]
i2jump.i2p.xyz — Another jump service. [service]
identiguy.i2p.xyz — Dynamically updated eepsite index. [service]
stats.i2p — Website for zzz's jump service. [service]
Proxy software
Polipo — SOCKS-enabled caching web proxy with basic filtering capabilities. [standalone]
Privoxy — Privacy-focused non-caching web proxy with advanced filtering capabilities. Excels at removing ads and other junk. [standalone]
Squid — Venerable caching web proxy. [standalone]
Inproxies
Gateways allowing users on the public Internet to access eepsites.
i2p.to — tino's inproxy on the public Internet. [service]
i2p.us — Another inproxy on the public Internet. [service]
i2p.me — Another inproxy on the public Internet. [service]
Outproxies
Gateways allowing I2P users to access content hosted on the public Internet.
false.i2p — Publicly advertised outproxy running Squid, located in Europe. [service]
Website Hosting
Jetty — Lightweight web server and Java servlet container. I2P is tightly integrated with a bundled copy of Jetty which by default is configured to host the user's eepsite. The bundled Jetty also serves the I2P router console and web applications bundled with I2P. [bundled, standalone]
Web servers
In addition to Jetty, any web server should function over I2P without modification so long as it's HTTP-compliant. Some web servers known to currently serve content on the I2P network are:
Apache HTTP Server — Most popular web server on the public WWW. [standalone]
Apache Tomcat — Web server and Java servlet container. More features than Jetty. [standalone]
lighttpd — Fast lightweight web server. [standalone]
nginx — High-performance lightweight web server. [standalone]
OS: Windows 2000/XP/2003/Vista/7/8/10
Post-install work
After running the installer on windows, simply click on the "Start I2P" button which will bring up the router console, which has further instructions.
On Unix-like systems, I2P can be started as a service using the "i2prouter" script, located in the directory you selected for I2P. Changing to that directory in a console and issuing "sh i2prouter status" should tell you the router's status. The arguments "start", "stop" and "restart" control the service. The router console can be accessed at its usual location. For users on OpenSolaris and other systems for which the wrapper (i2psvc) is not supported, start the router with "sh runplain.sh" instead.
When installing for the first time, please remember to adjust your NAT/firewall if you can, bearing in mind the Internet-facing ports I2P uses, described here among other ports. If you have successfully opened your port to inbound TCP, also enable inbound TCP on the configuration page.
Also, please review and adjust the bandwidth settings on the configuration page, as the default settings of 96 KBps down / 40 KBps up are fairly slow.
If you want to reach eepsites via your browser, have a look on the browser proxy setup page for an easy howto.
MAC OS X : Download the 0.9.23 OSX graphical installer file and run java -jar i2pinstall_0.9.23.jar
GNU/Linux/BSD/Solaris : Download the graphical installer file and run java -jar i2pinstall_0.9.23.jar
Packages for : Debian & Ubuntu are available.
Android :Outside I2P:
I2P 0.9.22
Inside I2P:
I2P 0.9.22
Google Play:
I2P 0.9.22
Our F-Droid repository:
I2P 0.9.22
F-Droid:
I2P 0.9.19
Development Builds:
str4d's eepsite
Requires Android 2.3 (Gingerbread) or higher. If you earlier installed I2P, you need to reinstall because we have also changed the release keys. 512 MB RAM minimum; 1 GB recommended. The release and dev versions of the I2P APK are not compatible, as they are signed by zzz and str4d respectively. Uninstall one before installing the other.
https://geti2p.net/en/
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.