I2pConsoleDocs

Aus i2pwiki.mk16.de
Zur Navigation springen Zur Suche springen

Introduction[Bearbeiten]

This page was last edited by Clipper in 2006.

Definition of information in the I2P Console[Bearbeiten]

This is very much a work in progress. I plan to add explanations for most items available through the console, by looking at code, available documentation, and asking for help. Most of this will be empty, so please add anything you can. Feel free to move or reformat this page as necessary.

Left Panel[Bearbeiten]

configuration[Bearbeiten]

  • The place for configuring your node. Changes to the settings take effect shortly afterwards for most things.
  • Network
    Gives access to the config of the bandwidth limiter. Just look at the documentation below each option, most are well explained.
    Bandwidth limiter

    The first number for both the inbound and outbound limit sets the average amount of bandwidth that I2P is allowed to use, while the second one (the "burst" one) adds an amount to the first setting and increases the allowed average bandwith that I2P can use by this amount. Both settings are average settings and no absolute values. The last option (the timelimit) tells I2P, how long it is allowed to transfer with maximum average (= burst) speed. This timelimit is "recharged", if I2P transfers with below average speed. (correct, anyone? - Yes, it looks like it does it this way.) Example: Given a DSL-6000 Line with 6144KBit/s download speed and 640KBit/s upload speed. This calculates to 750Kbyte/s download speed and 78Kbyte/s upload speed:

    6144KBit/s x 1000 =6144000Bit/s => 6144000Bit/s : 8Bit/byte = 768000byte/s => 768000byte/s : 1024 = 750Kbyte/s 640KBit/s x 1000 =640000Bit/s => 640000Bit/s : 8Bit/byte = 80000byte/s => 80000byte/s : 1024 = 78Kbyte/s Assumed you want to use half of your bandwith for the I2P-network and allow a bit more bandwith for bursting, then you must enter the following settings: Inbound rate: 375 KBps bursting up to 125 KBps for 60 seconds Outbound rate: 39 KBps bursting up to 13 KBps for 60 seconds This settings allow the average download speed to increase up to 375KBps + 125KBps = 500KBps for 60 seconds. And the average upload speed to increase to 39KBps + 13KBps = 52KBps for 60 seconds. The explanation "bursting up to" is a bit confusing. In my opinion it should be written "bursting up (by)". It has confused me for a long time too, until I have made extensive tests. Again, this are average bandwith settings which I2P tries to keep. This means I2P still can use up all of your physical available bandwith to reach this average bandwith settings. And in fact it does. There are constantly peaks up to the maximum (and above) of my available physical bandwith. The bandwith limiter is, in my humble opinion, not very well developed. It is not working like the bandwith limiters in Azureus and other P2P software which have real absolute bandwith settings which the program is not allowed to exceed. For all who are using I2P and P2P software in general cFosSpeed (http://www.cfos.de/speed/cfosspeed_e.htm - external link!) is highly recommended.

    bandwidth share percentage
    The bandwidth share percentage gives a way of specifically limiting tunnels initiated by other nodes. Setting this too low reduces your anonymity since there is not enough traffic from others to hide your own activity. From the amount of bandwith (as set in the bandwidth limiter), a percentage is used as routing capacity for other nodes and the remaining bandwidth for your needs when you are sending and receiving data. For the above example I suggest a setting of 70%. After you have done all your settings you can control the behavior of I2P. On your I2P Router Console open the Graphs link and let it open in the browser. Then let the I2P-Router running for 1 to 2 hours. It should run alone. No other application should use your internet connection during this time and do not do any up- and downloads or surfing via I2P. On the Graphs page you will see a lot of graphs. Interesting are the 2 at the top. The left one bw.sendRate average for 60s shows the reached average upload speeds. The right one bw.recvRate average for 60s shows the reached average download speeds. Most interesting is the left one. This is the limiting speed of you DSL-connection. Under the graph you see two values, average and max. Now after 1 to 2 hours the average value should be somewhere in the range between 27.3KBps (39KBps x 0.7 (70%!)) and 36.4KBps (52KBps x 0.7 (70%)). The max value shoud never exceed the 52KBps. Of course if you are not connected to to many nodes or there is no traffic for other reasons then the average value can be below the 27.3KBps. But meanwhile there are enough nodes on the I2P network producing traffing. In most cases if this happens something is wrong with your connection or with the calculation of your connection speeds. On the other hand if you do up- and downloading or surfing the I2P-net at the same time the average value can even exceed the 39KBps value what is normal in this case. The range given for normal operation (routing + up- and downloading + ...) was 39KBps to 52KBps. But it should never exceed the 52KBps. So at full power the maximum average upload speed can be average = max = 52KBps. That's it! (Hope I have analysed this all correct. Feel free to correct me.)
  • Service
    The place to shutdown or restart your node. You should choose a gracefull restart/shutdown, so that your node waits for all tunnels in which it participates to expire. You can also create a thread dump on this page, which is sometimes needed to find bugs.
    Update
    Options for the automatic update function of I2P.
    Tunnels
    Links to the same page as the one in the Top Panel. See there for an explanation of it's use.
    Logging
    The place to set the loglevel in general or for specific parts of I2P. Also allows you to change the logformat and -file. Mostly interesting for devs.
    Stats
    Allows you to log chosen statistical data to a given logfile. (In which interval?)
    Advanced
    Mostly usefull to set some special settings or to edit a whole bunch at once. Some useful settings, which you can put there:
    consolePassword=abc
    Only allows access to the webinterface of your node after you gave the given password. (user is always "admin")
    syndie.singleUser=true
    Forces Syndie in single-user mode, which is useful for changing the config, if you lost your password...
    i2np.udp.port=8887
    Modify if you need to use a different port than 8887.
    i2np.udp.internalPort=8887
    Unless you're hacking deeper than this FAQ extends, keep equal to "i2np.udp.port".

General[Bearbeiten]

Shows basic information on your I2P node.

  • Ident
    The shortened four character identity for your router on the I2P network
    Version
    Version of the software running on the local machine
    Uptime
    How long the local I2P server has been running
    Now
    The current time, as set on the local computer. This is followed in brackets by the difference in seconds between this time and the correct time (taken from a ntp-server pool, probably "pool.ntp.org". Other sources?)
    Status
    Shows the status of your node's connection to the I2P network, and detects if your firewall or network is interfering with I2P. "OK" means all is well, you can connect to others and others can connect to you. "OK (NAT)" means that i2p detected a supported NAT type and both outbound and inbound connections are possible. I2P should work fine. "ERR-SymmetricNAT" means although you can make connections to other nodes, your address looks different each time. This is due to the way your NAT works (it's a specific dumb type of NAT = router). These NATs are currently not compatible with I2P. "ERR-ClockSkew" means that I2P detected a clockskew of over 30s, which prevents it from operating correctly. "Unknown" means something else went wrong (if I2P didn't just start up) - check that the ports specified on http://www.i2p/faq are open.

Peers[Bearbeiten]

  • See http://www.i2p/how_peerselection for more detailed information on peer selection
  • *; Active
    The number of peers the router is talking to now, followed by the number of active identities it has spoken with recently.
    Fast
    How many active peers the router ranks as fast. A fast peer is one which responds with an above average response time.
    High Capacity
    How many active peers the router ranks as having a high capacity. A high capacity peer is able to handle a larger than average number of tunnels without rejecting new ones or failures.
    Well Integrated
    How many active peers the router ranks as well integrated. A well integrated peer is able to tell us about more new peers than average.
    Failing
    How many peers the router ranks as failing. A peer is marked as failing when it appears to be overloaded and is not efficiently handling traffic.
    Known
    How many routers does your peer know exist.

Bandwidth[Bearbeiten]

These entries describe the amount of bandwidth which has been used. The entries are self explanatory.

Local Destinations[Bearbeiten]

How many client destinations are connected locally. A client destination is a user's entry point to the I2P network - one destination provides access to eepsites, another to IRC, etc. Server destinations, which connect servers to the I2P network, are listed here, too.

Tunnels[Bearbeiten]

Detailed technical information on tunnels can be found here and here. In brief, a tunnel is a one way path for delivering data made up of a number of I2P peers as specified by the tunnel creator. Each peer only gets enough information to allow them to pass messages to the next hop in the tunnel. Inbound tunnels are created to receive data on, and outbound tunnels are created to send data.

  • *; Exploratory
    These tunnels are both used to discover the I2P network, and as a pool of tunnels ready for use by client services. Less stringent criteria are used for selecting peers to participate in exploratory tunnels.
    Client
    These tunnels are used for some I2P service, Irc2P or eepsites for example. The participant peers for these tunnels can be selected to best suit the service they will be used for. This usually means picking fast, high capacity peers.
    Participating
    This shows the number of tunnels where we are an intermediate hop.

Congestion[Bearbeiten]

Shows information on your routers performance

  • *; Job Lag
    How lagged our job queue is over the last minute. (This is an indicator of CPU usage. If it increases, then your CPU is overloaded. If your connection to the internet is getting overloaded by I2P, then the Message Delay should increase instead.)
    Message Delay
    How long it takes us to pump out a message, averaged over the last minute. (This is the delay due to network congestion - when this starts to increase the network is having difficulty handling I2P's traffic? A: Something like that I think. Probably either your connection is overloaded, or the I2P nodes, to which you are connected.)
    Tunnel Lag
    How long it takes us to test our tunnels, averaged over the last 10 minutes. (This gives a broad view of how well the I2P network is performing, from your routers perspective? A: It can also increase, if your local node has problems, but I don't know much about this one.)


Top Panel[Bearbeiten]

This panel includes links to different applications, configuration pages and diagnostic pages running as part of I2P.

First Row - Applications[Bearbeiten]

These applications run on your local host, and give access to services which use the I2P network.

  • *; Susimail
    This is a simple web-based mail client, configured to read mail from a mail service running on the I2P network. Accounts can be created for free at http://hq.postman.i2p/, follow the link to E-Mail related services on the right. Because of it's simplicity, the Susimail client does not add headers to your messages which may compromise your anonymity.
    SusiDNS
    I2P uses hosts files to translate friendly names like to destinations. This is a program which helps manage these hosts files automatically or manually.
    Syndie
    Syndie is an application which provides a way of sharing blogs and message boards between users. These can be synchronized between different Syndie archives anywhere, not necesarily on I2P. By default Syndie will synchronize with archives at three well known locations on I2P - this process can be sped up on the Syndicate page within Syndie.
    I2PSnark
    I2PSnark is a bittorrent client which runs on I2P. BitTorrent is a file sharing application widely used on the internet. (Only torrents from i2p-trackers will work with it, not normal ones)
    My Eepsite
    This is a site which other users can view on our I2P node if they have the appropriate destination. (As a default thats the destination of the "eepsite" tunnel)


Second Row - Console Pages[Bearbeiten]

These links bring you to pages which allow you to re-configure your I2P node, and view detailed information on it.

  • *; I2PTunnel
    This page allows high-level control over I2PTunnels. An I2PTunnel is a way of sending a normal TCP connection through the I2P network. This means it should be possible to run almost any internet based tool through I2P if users set up appropriate I2PTunnels. These should not be confused with the routing tunnels which I2P anonymity is based around.
    Tunnels
    These are the routing tunnels which I2P anonymity is based around. Every tunnel in use is here, with a list of the nodes which make up the tunnel. Clicking Config beside a group of tunnels allows you to modify settings which strike a balance between speed and anonymity. Requiring more hops makes it harder for an attacker to identify traffic coming to or from your server.
    Profiles
    This page lists all the I2P peers that your server knows about. Information you have gathered on each peer is given, that is the peers speed at responding to request, whether they can handle many requests together, and how many other peers they know about.
    NetDB
    This shows everything your I2P server knows about the network. Routing information, and data on each peer is listed.
    Logs
    This page shows the contents of I2P log files. (Note: Anything below critical = "CRIT" is mostly nothing to worry about.)
    Jobs
    This page lists actions which have been scheduled in the I2P router. The number after "ready/waiting jobs:" is a good indicator for CPU-load related and other problems/bugs. If that number get's rather large, your node cannot keep up with the workload, which can either happen due to a too slow CPU or a bug somewhere (probably in the first entry after "ready/waiting jobs", exspecially if that job is already taking a long time to finish).
    Stats
    Statistics on everything within your router can be found here.
    Internals
    This page displays a lot of information, like averages and active tunnel details. (Mostly a duplicate of the "Stats" page? )