source: apps/routerconsole/jsp/help-sidebar.jsi @ 93511c0

Last change on this file since 93511c0 was 93511c0, checked in by str4d <str4d@…>, 4 years ago

HTML tag validity bugfixes

  • Property mode set to 100644
File size: 6.7 KB
Line 
1<h2>Summary Bar Information</h2><p>
2Many of the stats on the summary bar may be
3<a href="configstats.jsp">configured</a> to be
4<a href="graphs.jsp">graphed</a> for further analysis.
5</p><h3>General</h3><ul>
6<li class="tidylist"><b>Local Identity:</b>
7The first four characters (24 bits) of your 44-character (256-bit) Base64 router hash.
8The full hash is shown on your <a href="netdb.jsp?r=.">router info page</a>.
9Never reveal this to anyone, as your router info contains your IP.</li>
10<li class="tidylist"><b>Version:</b>
11The version of the I2P software you are running.</li>
12<%
13/* <li class="tidylist"><b>Now:</b>
14The current time (UTC) and the skew, if any. I2P requires your computer's time be accurate.
15If the skew is more than a few seconds, please correct the problem by adjusting
16your computer's time.</li> */
17%>
18<li class="tidylist"><b>Reachability:</b>
19The router's view of whether it can be contacted by other routers.
20See <a href="#confignet">below</a> for more information.
21</li></ul><h3>Peers</h3><ul>
22<li class="tidylist"><b>Active:</b>
23The first number is the number of peers you've sent or received a message from in the last few minutes.
24This may range from 8-10 to several hundred, depending on your total bandwidth,
25shared bandwidth, and locally-generated traffic.
26The second number is the number of peers seen in the last hour or so.
27Do not be concerned if these numbers vary widely.
28<a href="configstats.jsp#router.activePeers">[Enable graphing]</a>.</li>
29<li class="tidylist"><b>Fast:</b>
30This is the number of peers you use for building client tunnels. It is generally in the
31range 8-30. Your fast peers are shown on the <a href="profiles.jsp">profiles page</a>.
32<a href="configstats.jsp#router.fastPeers">[Enable graphing]</a></li>
33<li class="tidylist"><b>High Capacity:</b>
34This is the number of peers you use for building some of your exploratory tunnels. It is generally in the
35range 8-75. The fast peers are included in the high capacity tier.
36Your high capacity peers are shown on the <a href="profiles.jsp">profiles page</a>.
37<a href="configstats.jsp#router.highCapacityPeers">[Enable graphing]</a></li>
38<li class="tidylist"><b>Well Integrated:</b>
39This is the number of peers you use for network database inquiries.
40These are usually the "floodfill" peers.
41Your well integrated peers are shown on the bottom of the <a href="profiles.jsp">profiles page</a>.</li>
42<li class="tidylist"><b>Known:</b>
43This is the total number of routers you know about.
44They are listed on the <a href="netdb.jsp">network database page</a>.
45This may range from under 100 to 1000 or more.
46This number is not the total size of the network;
47it may vary widely depending on your total bandwidth,
48shared bandwidth, and locally-generated traffic.
49I2P does not require a router to know every other router.</li>
50</ul><h3>Bandwidth in/out</h3>
51<p>Should be self-explanatory. All values are in bytes per second, not bits per second.
52Change your bandwidth limits on the <a href="config">configuration page</a>.
53Bandwidth is <a href="graphs.jsp">graphed</a> by default.</p>
54<h3>Local destinations</h3>
55<p>The local applications connecting through your router.
56These may be clients started through <a href="i2ptunnel/index.jsp">I2PTunnel</a>
57or external programs connecting through SAM, BOB, or directly to I2CP.</p>
58
59<h3>Tunnels in/out</h3>
60<p>The actual tunnels are shown on the <a href="tunnels.jsp">the tunnels page</a>.</p>
61<ul><li class="tidylist"><b>Exploratory:</b>
62Tunnels built by your router and used for communication with the floodfill peers,
63building new tunnels, and testing existing tunnels.</li>
64<li class="tidylist"><b>Client:</b>
65Tunnels built by your router for each client's use.</li>
66<li class="tidylist"><b>Participating:</b>
67Tunnels built by other routers through your router.
68This may vary widely depending on network demand, your
69shared bandwidth, and amount of locally-generated traffic.
70The recommended method for limiting participating tunnels is
71to change your share percentage on the <a href="config">configuration page</a>.
72You may also limit the total number by setting <tt>router.maxParticipatingTunnels=nnn</tt> on
73the <a href="configadvanced.jsp">advanced configuration page</a>. <a href="configstats.jsp#tunnel.participatingTunnels">[Enable graphing]</a>.</li>
74<li class="tidylist"><b>Share ratio:</b>
75The number of participating tunnels you route for others, divided by the total number of hops in
76all your exploratory and client tunnels.
77A number greater than 1.00 means you are contributing more tunnels to the network than you are using.</li>
78</ul>
79
80<h3>Congestion</h3>
81<p>Some basic indications of router overload:</p><ul>
82<li class="tidylist"><b>Job lag:</b>
83How long jobs are waiting before execution. The job queue is listed on the <a href="jobs.jsp">jobs page</a>.
84Unfortunately, there are several other job queues in the router that may be congested,
85and their status is not available in the router console.
86The job lag should generally be zero.
87If it is consistently higher than 500ms, your computer is very slow, or the
88router has serious problems.
89<a href="configstats.jsp#jobQueue.jobLag">[Enable graphing]</a>.</li>
90<li class="tidylist"><b>Message delay:</b>
91How long an outbound message waits in the queue.
92This should generally be a few hundred milliseconds or less.
93If it is consistently higher than 1000ms, your computer is very slow,
94or you should adjust your bandwidth limits, or your (bittorrent?) clients
95may be sending too much data and should have their transmit bandwidth limit reduced.
96<a href="configstats.jsp#transport.sendProcessingTime">[Enable graphing]</a> (transport.sendProcessingTime).</li>
97<li class="tidylist"><b>Tunnel lag:</b>
98This is the round trip time for a tunnel test, which sends a single message
99out a client tunnel and in an exploratory tunnel, or vice versa.
100It should usually be less than 5 seconds.
101If it is consistently higher than that, your computer is very slow,
102or you should adjust your bandwidth limits, or there are network problems.
103<a href="configstats.jsp#tunnel.testSuccessTime">[Enable graphing]</a> (tunnel.testSuccessTime).</li>
104<li class="tidylist"><b>Handle backlog:</b>
105This is the number of pending requests from other routers to build a
106participating tunnel through your router.
107It should usually be close to zero.
108If it is consistently high, your computer is too slow,
109and you should reduce your share bandwidth limits.</li>
110<li class="tidylist"><b>Accepting/Rejecting:</b>
111Your router's status on accepting or rejecting
112requests from other routers to build a
113participating tunnel through your router.
114Your router may accept all requests, accept or reject a percentage of requests,
115or reject all requests for a number of reasons, to control
116the bandwidth and CPU demands and maintain capacity for
117local clients.</li></ul>
Note: See TracBrowser for help on using the repository browser.