Version 4 (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

Attachments (3)

Download all attachments as: .zip