Changes between Version 3 and Version 4 of I2Pguide

Apr 9, 2010 9:17:49 AM (10 years ago)


  • I2Pguide

    v3 v4  
    4343The 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.
    4444Thats why I2P works ONLY in its own network. You cannot get P2P data from usual network/trackers/webpages.
     47= Router information =
     49Description of the leftern menu in router console
     51In ths status console window you will always see life stats of your running I2P session.
     53left menu       
     55I2P - the link under the picture will bring you back to start page of your router
     57Configuration - important configurations for your I2P router
     58Help - some basic help links
     60Ident - your identification of your I2P router. DO NOT PUBLISH IT! It is bound to your IP.
     61Version - running I2P version, should be at least 0.7.2
     62Uptime - I2P running time
     63Now - actual time - sync your clock with ntp. If time differs to much (5 min) your I2P will suffer badly
     64Reachability - reachability of yout I2P ports, discovered by other I2P routers connecting to them
     66restart/shutdown - buttons to restart or shutdown I2P nicely. Does not accept new tunnels and wait 11 min til all old tunnels are timed out
     68Peers - list of active UDP/NTCP connection
     69Active - count of I2P routers yours had connection with in 5 min/60 min rate
     70Fast - number of routers in fast tier (see Profiles)
     71High capacity - number of routers in high capacity tier
     72Well integrated - number of known well integrated routers
     73Known - number of seen different router IDs in last 24h
     76rates of speed in 1s average, 5 min and over all uptime of running session
     77Used - total amount of data sent and received in active session by I2P router
     79Local destinations
     80list of active destinations (server and clients) on local I2P router.
     82*shared clients - pool of tunnel for applications not running on seperate destinations
     83*echelon.i2p - in this case my eepsite echelon.i2p
     85At least the shared clients destination should be up after router startup.
     87Tunnels in/out
     88Exploratory - number of active exploratoy tunnels (see further down for tunnel information)
     89Client - number of active client tunnels
     90Participating - number of routed tunnels (not starting or ending at one of your destinations)
     93Job lag - time waiting for a job to be fullfilled, should be as low as possible
     94Message delay - delay til a message is send out of I2P
     95Tunnel lag - roundtrip time on tunnels
     96Handle backlog - numer of jobs waiting to be fullfilled, should be 0
     97Rejecting tunnels - reason why no new participating tunnels are accepted