Forum.i2p. Syndie. I2P-Bote. API - Java Documentation. Download. Dependency Java Runtime 1.6 or higher.
(Oracle Java Version 7, OpenJDK 7, or IcedTea7 recommended, except Raspberry Pi: JDK 8 for ARM, PowerPC: IBM SDK 7) Determine your installed Java version here or type java -version at your command prompt. Clean installs 186bbe30a37802b6201fe129516e2d9515925cfc60e2f68645eb6413ec172953 Download that file and run it. 5b2a1e23273e1d76a071142adc58b836ed300e2c1f2fd80d330ac61632fab173 Download that file and double-click it (if that works) or type java -jar i2pinstall_0.9.16.jar in a terminal to run the installer. Command line (headless) install: Download the 0.9.16 OSX graphical installer file above and run java -jar i2pinstall_0.9.16.jar -console from the command line.
Download that file and double-click it (if that works) or type java -jar i2pinstall_0.9.16.jar in a terminal to run the installer. Download the graphical installer file above and run java -jar i2pinstall_0.9.16.jar -console from the command line. Android source is in monotone and on Github. Naming and Addressbook. This page was last updated in April 2014 and is accurate for router version 0.9.12. Overview I2P ships with a generic naming library and a base implementation designed to work off a local name to destination mapping, as well as an add-on application called the addressbook.
I2P also supports Base32 hostnames similar to Tor's .onion addresses. The addressbook is a web-of-trust driven secure, distributed, and human readable naming system, sacrificing only the call for all human readable names to be globally unique by mandating only local uniqueness. While all messages in I2P are cryptographically addressed by their destination, different people can have local addressbook entries for "Alice" which refer to different destinations.
NOTE: For the reasoning behind the I2P naming system, common arguments against it and possible alternatives see the naming discussion page. Naming System Components There is no central naming authority in I2P. Naming Services. i2ptunnel. Overview I2PTunnel is a tool for interfacing with and providing services on I2P.
Destination of an I2PTunnel can be defined using a hostname, Base32, or a full 516-byte destination key. An established I2PTunnel will be available on your client machine as localhost:port. If you wish to provide a service on I2P network, you simply create I2PTunnel to the appropriate ip_address:port. A corresponding 516-byte destination key will be generated for the service and it will become avaliable throughout I2P. Default Services Server tunnels I2P Webserver - A tunnel pointed to a Jetty webserver run on localhost:7658 for convenient and quick hosting on I2P.
Client tunnels I2P HTTP Proxy - localhost:4444 - A HTTP proxy used for browsing I2P and the regular internet anonymously through I2P. Client Modes Standard Opens a local TCP port that connects to a service (like HTTP, FTP or SMTP) on a destination inside of I2P. A HTTP-client tunnel. SOCKS 4/4a/5 Enables using the I2P router as a SOCKS proxy.
Streamr. I2P.