Version 5 (modified by anonymous, 9 years ago) (diff)

Echelon's Guide to I2P, v0.3

for all users

After a while on I2P and a lot of time in #i2p-chat I saw more help and information is needed for the users of I2P.Til the official homepage is redone this guide will show you basic information and extendend knowledge to use and understand I2P better. I2P

I2P is a solution to provide anonymous communication in the non-anonymous internet. To accomplish that goal it uses different techniques like encryption and routing data via other users of I2P.

  • Preface - important to read
  • General information
  • Router information - description of the leftern menu
  • Head menu - description of the head menu
  • Bandwidth - basic information for bandwidth settings
  • Configuration - overview over all configuration pages
  • iMule - tips and tricks to iMule


Facts that you must know about I2P

  1. There is NO 100% anonymity!

I2P just tries to reach as near as it could get up to 100% and still be useable by the users.

  1. I2P does not hide the fact you run I2P (it does NOT hide the IP address)!

I2P tries to get rid of the binding IP-destination (service). E.G. you could see all the IPs of the users who run I2P and you get the so called "destination ID" of a service. But you cannot determine which user (which IP or router) runs which destination.

  1. Building up this anonymity costs bandwidth!

Although I2P is P2P friendly you will hardly get faster speeds than 20-40 kb/sec on a single connection. Thats due to the fact of I2P techniques of being anonymous. Do not expect RAW line speeds on I2P!

  1. The I2P net is very dynamic.

If you get decent speed for a download right now, it will change the next 10 minutes. Users join and leave - the more users share bandwith to I2P, the better the experience for each of them will be.

  1. I2P needs special adapted software!

As basicly all existant software is not aware of anonymity (e.g. browsers send out their version and other information to the internet), I2P needs special adapted software. There is already a wide bunch of adapted software available to be used within I2P (look on my eepsite).

  1. I2P is closed-network!

The I2P team (which is not payed for the job it does) does not want to burden the risk of being a outproxy into the usual internet upon every user of I2P. E.g. the risk of being a open proxy for spam emails or DOS attacks of websites or other users browsing illegal webpages through their router. Thats why I2P works ONLY in its own network. You cannot get P2P data from usual network/trackers/webpages.

Router information

Description of the leftern menu in router console

In ths status console window you will always see life stats of your running I2P session.

left menu

I2P - the link under the picture will bring you back to start page of your router

Configuration - important configurations for your I2P router Help - some basic help links

Ident - your identification of your I2P router. DO NOT PUBLISH IT! It is bound to your IP. Version - running I2P version, should be at least 0.7.2 Uptime - I2P running time Now - actual time - sync your clock with ntp. If time differs to much (5 min) your I2P will suffer badly Reachability - reachability of yout I2P ports, discovered by other I2P routers connecting to them

restart/shutdown - buttons to restart or shutdown I2P nicely. Does not accept new tunnels and wait 11 min til all old tunnels are timed out

Peers - list of active UDP/NTCP connection Active - count of I2P routers yours had connection with in 5 min/60 min rate Fast - number of routers in fast tier (see Profiles) High capacity - number of routers in high capacity tier Well integrated - number of known well integrated routers Known - number of seen different router IDs in last 24h

Bandwidth rates of speed in 1s average, 5 min and over all uptime of running session Used - total amount of data sent and received in active session by I2P router

Local destinations list of active destinations (server and clients) on local I2P router. e.g. *shared clients - pool of tunnel for applications not running on seperate destinations *echelon.i2p - in this case my eepsite echelon.i2p

At least the shared clients destination should be up after router startup.

Tunnels in/out Exploratory - number of active exploratoy tunnels (see further down for tunnel information) Client - number of active client tunnels Participating - number of routed tunnels (not starting or ending at one of your destinations)

Congestion Job lag - time waiting for a job to be fullfilled, should be as low as possible Message delay - delay til a message is send out of I2P Tunnel lag - roundtrip time on tunnels Handle backlog - numer of jobs waiting to be fullfilled, should be 0 Rejecting tunnels - reason why no new participating tunnels are accepted


The configuration of your I2P is not a trivial job and takes some time and knowledge to do it the perfect way. For luck I2P runs fairly well in default setup - as long as your PC have sufficient ressources to run I2P. Nevertheless you should at least setup the core settings bandwidth and connectivity on this page.

For more advanced setup and tweaks of your I2P router you need to select the links on the upper menu on site and adapt those settings to your needs and wishes.

configuration submenu

First point "Network" is already open and contains the bandwidth and connectivity settings you should already have aopted to your needs. Second point Service contains options to start and stop I2P and the setting to open a browser on startup. Next point Update tweaks the automatic update of your I2P router. Tunnels page let you tweak current destinations for active I2P session only. On clients page you are able to enable SAM bridge or disable unwanted webapps. Peers page is ment to manual adjust single values for single routers, including shitlisting. Keyring page prepares the functionality to encrypt your destination IDs and let user add a public key to local keyring. On logging page the behaviour of the logs page is controlled. Same on stats page for stats logging and graphs. Last entry advanced finally shows you the box for all config line options.


On this page you set all the connectivity options and transports for your I2P router. It has been made fairly easy with UPnP in version 0.7.4 and above - default settings are fine for nearly all users and UPnP pokes a hole into firewalls. Nevertheless you can disable UPnP and make all settings as you like. Remember to click on "Save changes" to save all changes you made on this page. You need to restart I2P for this changes to take effect! First box is set by default and enables UPnP, the link behind shows you the actual state of UPnP. Remove the check will disable UPnP. The IP configuration will try to guess your external reachable IP address and use this and the default port to connect to other I2P nodes, and to let other I2P nodes connect to your node. The options are quite self explaining:

  • use all automatic - let I2P get IP and port on its own
  • disable UPnP IP address detection - IP address is not detected by UPnP
  • Ignore local interface IP address - local IP addresses like will be ignored
  • Use SSU IP address detection only - IP address is only detected by SSU
  • Specify hostname or IP - you can set your IP address or hostname (dyndns) by hand in this box
  • hidden mode - your router will not publish any IP reachability information into the net, it will prevent participating traffic on your router, setting this option will restart your I2P router

UDP configuration will only let you select the port on which other I2P routers could connect to your I2P router via the UDP transport.

TCP configuration is nearly the same as IP configuration.

  • use auto-detected IP address - will detect and list your IP address here
  • always use auto-detected IP address - will use always auto detected IP address and will result in the not-firewalled mode.
  • specify hostname or IP - set your IP by hand in this box if auto detected IP is the wrong one, dyndns is fine, to.
  • disable inbound - disables your inbound TCP transwort which results in the firewalled mode - no other I2P router connects to your TCP port.
  • completely diasable- disables out and incoming TCP connects, setting this option will restart your I2P router.

As for TCP port selection you can select the same port as for UDP or you can enter a specific port on which other routers connect via TCP transport to your router.

In quite common setups the default settings of port 8887 and all other on auto with UPnP active is the best solution. Changing the ports will let to be your router be unique - mostly all routers use the default ports, a different port makes you be seen easy. The specify IP by hand for IP and TCP is only useful if you got more than one interface in your setup and you want I2P to bind to one special. The hidden mode is kinda special. Remember one of the main points on the preface site - I2P does NOT hide your IP. It publishes your IP and port information to the other routers for them to be able to connect to your router. This information is needed to built up a network and route tunnels via reachable routers. Nevertheless you can prohibite the distribution of your IP/port information and use only the information you get from first preseeding and on connecting to the routers you got from preseeding. This will NOT prohibite the routers you connect to from getting known of the fact you are connecting to them, but your IP/port will not be distributed across other routers and no other router will connect to you and will not try to route participating traffic across your router. The hidden node breaks a important part of the network for your router and will reduce the speed with which you participate in the I2P network and it will not cover your traffic with some participating traffic by other users.

Attachments (3)

Download all attachments as: .zip