diff --git a/apps/routerconsole/jsp/help-advancedsettings.jsi b/apps/routerconsole/jsp/help-advancedsettings.jsi index 9606cfea6e..ebf8c8b54d 100644 --- a/apps/routerconsole/jsp/help-advancedsettings.jsi +++ b/apps/routerconsole/jsp/help-advancedsettings.jsi @@ -1,6 +1,10 @@

Advanced Router Configuration

-

The router configuration options listed below are not available in the user interface, usually because they are rarely used or provide access to advanced settings that most users will not need. This is not a comprehensive list. Some settings will require a restart of the router to take effect. Note that all settings are case sensitive. You will need to edit your router.config file to add options, or, once you have added routerconsole.advanced=true to the router.config file, you may edit settings within the console on the Advanced Configuration page.

+

The router configuration options listed below are not available in the user interface, usually because they are rarely used or provide access to advanced settings that most users will not need. +This is not a comprehensive list. +Some settings will require a restart of the router to take effect. +Note that all settings are case sensitive. +You will need to edit your router.config file to add options, or, once you have added routerconsole.advanced=true to the router.config file, you may edit settings within the console on the Advanced Configuration page.

@@ -9,7 +13,10 @@ - + @@ -18,25 +25,34 @@ - + - + - + - + - + - +
routerconsole.advanced={true|false}
Only set this to true if you know what you are doing!
When set to true, additional functionality will be enabled in the console and the user will be able to edit settings directly on the Advanced Configuration page. Extra display options are provided in the Network Database section, including the Sybil Analysis tool, and there are additional configuration options on the Clients Configuration page. This will also enable the installation of unsigned updates, manual configuration of the news URL, and the installation of plugins. You may also wish to enable the "Advanced" sidebar section on the Summary Bar Configuration page.
When set to true, additional functionality will be enabled in the console and the user will be able to edit settings directly on the Advanced Configuration page. +Extra display options are provided in the Network Database section, including the Sybil Analysis tool, and there are additional configuration options on the Clients Configuration page. +This will also enable the installation of unsigned updates, manual configuration of the news URL, and the installation of plugins. +You may also wish to enable the "Advanced" sidebar section on the Summary Bar Configuration page.
routerconsole.browser={/path/to/browser}
This setting allows the manual selection of the browser which I2P will launch on startup (if the console is configured to launch a browser on startup), overriding the OS default browser.
If you wish to install unsigned (.zip) I2P updates, this should be added to your router.config file unless you have already configured routerconsole.advanced=true, in which case this option is already provisioned.
router.updateUnsignedURL={url}
This setting allows you to configure the update url for the unsigned update feature, if enabled. The url should end with /i2pupdate.zip. Note: do not install unsigned updates unless you trust the source of the update!
This setting allows you to configure the update url for the unsigned update feature, if enabled. +The url should end with /i2pupdate.zip. +Note: do not install unsigned updates unless you trust the source of the update!
routerconsole.enablePluginInstall={true|false}
When set to true, this enables plugin installation on the Plugin Configuration page. Setting routerconsole.advanced=true will also enable this feature. [Enabled by default]
When set to true, this enables plugin installation on the Plugin Configuration page. +Setting routerconsole.advanced=true will also enable this feature. +[Enabled by default]
routerconsole.allowUntrustedPlugins={true|false}
Plugins signed with the cryptographic key of the developer are the recommended format, but if you wish to install unsigned plugins you can set this to true. Note that you may still encounter issues attempting to install an unsigned plugin if the developer has included additional checks in the plugin build process.
Plugins signed with the cryptographic key of the developer are the recommended format, but if you wish to install unsigned plugins you can set this to true. +Note that you may still encounter issues attempting to install an unsigned plugin if the developer has included additional checks in the plugin build process.
routerconsole.showSearch={true|false}
When set to true, a configurable search bar will appear on the console homepage. Additional searches may then be added on the home configuration page.
When set to true, a configurable search bar will appear on the console homepage. +Additional searches may then be added on the home configuration page.
router.buildHandlerThreads={n}
Allocate number of processor threads for building tunnels. If your processor supports hyperthreading or simultaneous multithreading, you may multiply the number of processor cores by 2 to get the maximum number of threads to allocate, otherwise number of processor cores = maximum number of threads available. Note that you may wish to allocate less than the theoretical maximum to ensure you have headroom for other tasks.
Allocate number of processor threads for building tunnels. +If your processor supports hyperthreading or simultaneous multithreading, you may multiply the number of processor cores by 2 to get the maximum number of threads to allocate, otherwise number of processor cores = maximum number of threads available. +Note that you may wish to allocate less than the theoretical maximum to ensure you have headroom for other tasks.
router.hideFloodfillParticipant={true|false}
When set to true, if your router is serving as a floodfill for the network, your floodfill participation will be hidden from other routers.
router.maxParticipatingTunnels={n}
Determines the maximum number of participating tunnels the router can build. To disable participation completely, set to 0.
Determines the maximum number of participating tunnels the router can build. +To disable participation completely, set to 0.
router.networkDatabase.flat={true|false}
When set to true, the router info files stored in your profile's netDB directory will not be split into 64 sub-directories. diff --git a/apps/routerconsole/jsp/help-faq.jsi b/apps/routerconsole/jsp/help-faq.jsi index 82da347150..082afee143 100644 --- a/apps/routerconsole/jsp/help-faq.jsi +++ b/apps/routerconsole/jsp/help-faq.jsi @@ -1,20 +1,29 @@

Abridged I2P FAQ

-

This is a shortened version of the official FAQ. For the full version, please visit https://geti2p.net/faq or http://i2p-projekt.i2p/faq. +

This is a shortened version of the official FAQ. +For the full version, please visit https://geti2p.net/faq or http://i2p-projekt.i2p/faq.

My router has been up for several minutes and has zero or very few connections

-

If after a few minutes of uptime your router is indicating 0 Active Peers and 0 Known Peers, with a notification in the sidebar that you need to check your network connection, verify that you can access the internet. If your internet connection is functional, you may need to unblock Java in your firewall. Otherwise, you may need to reseed your I2P router. Visit the Reseed Configuration page and click the Save Changes and Reseed Now button.

+

If after a few minutes of uptime your router is indicating 0 Active Peers and 0 Known Peers, with a notification in the sidebar that you need to check your network connection, verify that you can access the internet. +If your internet connection is functional, you may need to unblock Java in your firewall. +Otherwise, you may need to reseed your I2P router. Visit the Reseed Configuration page and click the "Save Changes and Reseed Now" button.

My router has very few active peers, is this OK?

-

If your router has 10 or more active peers, everything is fine. The router should maintain connections to a few peers at all times. The best way to stay "better-connected" to the network is to share more bandwidth.

+

If your router has 10 or more active peers, everything is fine. +The router should maintain connections to a few peers at all times. +The best way to stay "better-connected" to the network is to share more bandwidth.

I'm missing lots of hosts in my addressbook. What are some good subscription links?

-

The default subscription is to http://i2p-projekt.i2p/hosts.txt which is seldom updated. If you don't have another subscription, you may often have to use "jump" links which is much slower but ensures that your addressbook is only populated by sites you use (in addition to the default subscription addresses). To speed up browsing on I2P, it's a good idea to add some addressbook subscriptions.

+

The default subscription is to http://i2p-projekt.i2p/hosts.txt which is seldom updated. +If you don't have another subscription, you may often have to use "jump" links which is much slower but ensures that your addressbook is only populated by sites you use (in addition to the default subscription addresses). +To speed up browsing on I2P, it's a good idea to add some addressbook subscriptions.

-

Here are some other public addressbook subscription links. You may wish to add one or two to your susidns subscription list. In the event that addresses conflict in the subscriptions, the lists placed at the top of your susidns configuration will take precedence over those placed further down.

+

Here are some other public addressbook subscription links. +You may wish to add one or two to your susidns subscription list. +In the event that addresses conflict in the subscriptions, the lists placed at the top of your susidns configuration will take precedence over those placed further down.

  • http://stats.i2p/cgi-bin/newhosts.txt
    • @@ -22,59 +31,132 @@
  • http://identiguy.i2p/hosts.txt
-

Note that subscribing to a hosts.txt service is an act of trust, as a malicious subscription could give you incorrect addresses, so be careful subscribing to lists from unknown sources. The operators of these services may have various policies for listing hosts. Presence on this list does not imply endorsement.

+

Note that subscribing to a hosts.txt service is an act of trust, as a malicious subscription could give you incorrect addresses, so be careful subscribing to lists from unknown sources. +The operators of these services may have various policies for listing hosts. +Presence on this list does not imply endorsement.

How do I access IRC, BitTorrent, or other services on the regular Internet?

-

Unless an outproxy has been set up for the service you want to connect to, this is not possible. There are only three types of outproxies running right now: HTTP, HTTPS, and email. Note that there is currently no publicly listed SOCKS outproxy. If this type of service is required, try Tor.

+

Unless an outproxy has been set up for the service you want to connect to, this is not possible. +There are only three types of outproxies running right now: HTTP, HTTPS, and email. +Note that there is currently no publicly listed SOCKS outproxy. +If this type of service is required, try Tor.

How do I configure my browser to access .i2p websites?

-

You will need to configure your browser to use the HTTP proxy server (by default on host: 127.0.0.1 port: 4444). See the Browser Proxy Configuration Guide for a more detailed explanation.

+

You will need to configure your browser to use the HTTP proxy server (by default on host: 127.0.0.1 port: 4444). +See the Browser Proxy Configuration Guide for a more detailed explanation.

What is an eepsite?

-

An eepsite is a website that is hosted anonymously on the I2P network - you can access it by configuring your web browser to use I2P's HTTP proxy (see above) and browsing to the .i2p suffixed website (e.g. http://i2p-projekt.i2p). Also ensure your browser is configured to resolve DNS remotely when using the proxy to avoid DNS leaks.

+

An eepsite is a website that is hosted anonymously on the I2P network - you can access it by configuring your web browser to use I2P's HTTP proxy (see above) and browsing to the .i2p suffixed website (e.g. http://i2p-projekt.i2p). +Also ensure your browser is configured to resolve DNS remotely when using the proxy to avoid DNS leaks.

Most of the eepsites are down?

-

If you consider every eepsite that has ever been created, yes, most of them are down. People and eepsites come and go. A good way to get started in I2P is check out a list of eepsites that are currently up. http://identiguy.i2p tracks active eepsites.

+

If you consider every eepsite that has ever been created, yes, most of them are down. +People and eepsites come and go. +A good way to get started in I2P is check out a list of eepsites that are currently up. +http://identiguy.i2p tracks active eepsites.

How do I connect to IRC within I2P?

-

A tunnel to the main IRC server network within I2P, Irc2P, is created when I2P is installed (see the I2P Tunnel Manager), and is automatically started when the I2P router starts. To connect to it, tell your IRC client to connect to server: 127.0.0.1 port: 6668.

+

A tunnel to the main IRC server network within I2P, Irc2P, is created when I2P is installed (see the I2P Tunnel Manager), and is automatically started when the I2P router starts. +To connect to it, tell your IRC client to connect to server: 127.0.0.1 port: 6668.

-

XChat-like client users can create a new network with the server 127.0.0.1/6668 (remember to tick Bypass proxy server if you have a proxy server configured), or you can connect with the command /server 127.0.0.1 6668. Different IRC clients may vary the syntax.

+

HexChat-like client users can create a new network with the server 127.0.0.1/6668 (remember to tick "Bypass proxy server" if you have a proxy server configured), or you can connect with the command /server 127.0.0.1 6668. +Different IRC clients may require a different command, consult your IRC client's manual for more information.

What ports does I2P use?

- + - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - - - - + + + + + + + + + + + + + + + - + - +
LOCAL PORTS
These are the local I2P port mappings, listening only to local connections by default, except where noted. Unless you require access from other machines, they should only be accessible from localhost.
These are the local I2P port mappings, listening only to local connections by default, except where noted. +Unless you require access from other machines, they should only be accessible from localhost.
PortFunctionNotes
1900UPnP SSDP UDP multicast listenerCannot be changed. Binds to all interfaces. Can be disabled on the Network Configuration page.
2827BOB bridgeA higher level socket API for clients. Can be enabled/disabled on the Client Configuration page. Can be changed in the bob.config file. [Disabled by default]
4444HTTP proxyCan be disabled or changed in the I2P Tunnel Manager. Can also be configured to bind to a specific interface or all interfaces.
4445HTTPS proxyCan be disabled or changed in the I2P Tunnel Manager. Can also be configured to bind to a specific interface or all interfaces.
6668IRC proxyCan be disabled or changed in the I2P Tunnel Manager. Can also be configured to bind to a specific interface or all interfaces.
7652UPnP HTTP TCP event listenerBinds to the LAN address. Can be changed with advanced config i2np.upnp.HTTPPort=nnnn. Can be disabled on the Network Configuration page.
7653UPnP SSDP UDP search response listenerBinds to all interfaces. Can be changed with advanced config i2np.upnp.SSDPPort=nnnn. Can be disabled on the Client Configuration page.
7654I2P Client Protocol portUsed by client apps. Can be changed to a different port on the Client Configuration page but this is not recommended. Can be bound to a different interface or all interfaces, or disabled, on the Client Configuration page.
7655UDP for SAM bridgeA higher level socket API for clients. Only opened when a SAM V3 client requests a UDP session. Can be enabled/disabled on the Client Configuration page. Can be changed in the clients.config file with the SAM command line option sam.udp.port=nnnn.
7656SAM bridgeA higher level socket API for clients. Can be enabled/disabled on the Client Configuration page. Can be changed in the clients.config file. [Disabled by default]
7657I2P Router Console (Web interface)Can be disabled in the clients.config file. Can also be configured to bind to a specific interface or all interfaces in that file. If you make the Router Console available over the network, you might wish to enforce an access password to prevent unauthorized access.
7658I2P Web ServerCan be disabled in the clients.config file. Can also be configured to bind to a specific interface or all interfaces in the jetty.xml file.
1900UPnP SSDP UDP multicast listenerCannot be changed. +Binds to all interfaces. +Can be disabled on the Network Configuration page.
2827BOB bridgeA higher level socket API for clients. +Can be enabled/disabled on the Client Configuration page. +Can be changed in the bob.config file. [Disabled by default]
4444HTTP proxyCan be disabled or changed in the I2P Tunnel Manager. +Can also be configured to bind to a specific interface or all interfaces.
4445HTTPS proxyCan be disabled or changed in the I2P Tunnel Manager. +Can also be configured to bind to a specific interface or all interfaces.
6668IRC proxyCan be disabled or changed in the I2P Tunnel Manager. +Can also be configured to bind to a specific interface or all interfaces.
7652UPnP HTTP TCP event listenerBinds to the LAN address. Can be changed with advanced config i2np.upnp.HTTPPort=nnnn. +Can be disabled on the Network Configuration page.
7653UPnP SSDP UDP search response listenerBinds to all interfaces. +Can be changed with advanced config i2np.upnp.SSDPPort=nnnn. +Can be disabled on the Client Configuration page.
7654I2P Client Protocol portUsed by client apps. Can be changed to a different port on the Client Configuration page but this is not recommended. +Can be bound to a different interface or all interfaces, or disabled, on the Client Configuration page.
7655UDP for SAM bridgeA higher level socket API for clients. +Only opened when a SAM V3 client requests a UDP session. +Can be enabled/disabled on the Client Configuration page. +Can be changed in the clients.config file with the SAM command line option sam.udp.port=nnnn.
7656SAM bridgeA higher level socket API for clients. +Can be enabled/disabled on the Client Configuration page. +Can be changed in the clients.config file. [Disabled by default]
7657I2P Router Console (Web interface)Can be disabled in the clients.config file. +Can also be configured to bind to a specific interface or all interfaces in that file. +If you make the Router Console available over the network, you might wish to enforce an access password to prevent unauthorized access.
7658I2P Web ServerCan be disabled in the clients.config file. +Can also be configured to bind to a specific interface or all interfaces in the jetty.xml file.
7659Outgoing mail to smtp.postman.i2pCan be disabled or changed in the I2P Tunnel Manager. Can also be configured to bind to a specific interface or all interfaces.
7660Incoming mail from pop.postman.i2pCan be disabled or changed in the I2P Tunnel Manager. Can also be configured to bind to a specific interface or all interfaces.
8998mtn.i2p2.i2p (I2P's Monotone DVCS)Can be disabled or changed in the I2P Tunnel Manager. Can also be configured to bind to a specific interface or all interfaces. [Disabled by default]
31000Local connection to wrapper control channel portOutbound to 32000 only, does not listen on this port. Starts at 31000 and will increment until 31999 looking for a free port. To change, see the wrapper documentation.
32000Local control channel for the service wrapperTo change, see the wrapper documentation.
7659Outgoing mail to smtp.postman.i2pCan be disabled or changed in the I2P Tunnel Manager. +Can also be configured to bind to a specific interface or all interfaces.
7660Incoming mail from pop.postman.i2pCan be disabled or changed in the I2P Tunnel Manager. +Can also be configured to bind to a specific interface or all interfaces.
8998mtn.i2p2.i2p (I2P's Monotone DVCS)Can be disabled or changed in the I2P Tunnel Manager. +Can also be configured to bind to a specific interface or all interfaces. [Disabled by default]
31000Local connection to wrapper control channel portOutbound to 32000 only, does not listen on this port. +Starts at 31000 and will increment until 31999 looking for a free port. +To change, see the wrapper documentation.
32000Local control channel for the service wrapperTo change, see the wrapper documentation.
INTERNET FACING PORTS
I2P selects a random port between 9000 and 31000 to communicate with other routers when the program is run for the first time, or when your external IP address changes when running in Laptop Mode. The selected port is shown on the Network Configuration page.
I2P selects a random port between 9000 and 31000 to communicate with other routers when the program is run for the first time, or when your external IP address changes when running in Laptop Mode. +The selected port is shown on the Network Configuration page.
Outbound UDP from the random port noted on the Network Configuration page to arbitrary remote UDP ports, allowing replies.
Outbound TCP from random high ports to arbitrary remote TCP ports.
Inbound UDP to the port noted on the Network Configuration page from arbitrary locations (optional, but recommended).
Inbound TCP to the port noted on the Network Configuration page from arbitrary locations (optional, but recommended). Inbound TCP may be disabled on the Network Configuration page.
Inbound TCP to the port noted on the Network Configuration page from arbitrary locations (optional, but recommended). +Inbound TCP may be disabled on the Network Configuration page.
Outbound UDP on port 123, allowing replies: this is necessary for I2P's internal time sync (via SNTP - querying a random SNTP host in pool.ntp.org or another server you specify).
diff --git a/apps/routerconsole/jsp/help-legal.jsi b/apps/routerconsole/jsp/help-legal.jsi index 986379ae0f..3cc5af9a28 100644 --- a/apps/routerconsole/jsp/help-legal.jsi +++ b/apps/routerconsole/jsp/help-legal.jsi @@ -12,23 +12,17 @@

On top of the I2P router are a series of client applications, each with their own set of licenses and dependencies:

    -
  • I2PTunnel - a GPL'ed application written by mihi -that lets you tunnel normal TCP/IP traffic over I2P (such as the http proxy and the irc proxy), with a browser-based front end.
    • +
  • I2PTunnel - a GPL'ed application written by mihi that lets you tunnel normal TCP/IP traffic over I2P (such as the http proxy and the irc proxy), with a browser-based front end.
  • Susimail, a GPL'ed browser based mail client written by susi23.
    • -
  • The addressbook application, -written by Ragnarok helps maintain your hosts.txt files, with a front end written by susi23.
    • -
  • The SAM bridge by human (public domain), an API -which other client applications (such the I2P Tahoe-LAFS cloud filesystem) can use to interface with I2P.
    • -
  • jbigi - an optimized library for doing large number calculations which uses the -LGPL licensed GMP library, tuned for various PC architectures.
    • -
  • Launchers for windows users are built with Launch4J, -and the installer is built with IzPack.
    • -
  • The I2P Router Console, built from a streamlined Jetty Web Server instance -which allows you to deploy standard JSP/Servlet web applications in your router.
    • -
  • Jetty makes use of Apache's javax.servlet -(javax.servlet.jar) implementation. This product includes software developed by the Apache Software Foundation.
    • +
  • The addressbook application, written by Ragnarok helps maintain your hosts.txt files, with a front end written by susi23.
    • +
  • The SAM bridge by human (public domain), an API which other client applications (such the I2P Tahoe-LAFS cloud filesystem) can use to interface with I2P.
    • +
  • jbigi - an optimized library for doing large number calculations which uses the LGPL licensed GMP library, tuned for various PC architectures.
    • +
  • Launchers for windows users are built with Launch4J, and the installer is built with IzPack.
    • +
  • The I2P Router Console, built from a streamlined Jetty Web Server instance which allows you to deploy standard JSP/Servlet web applications in your router.
    • +
  • Jetty makes use of Apache's javax.servlet (javax.servlet.jar) implementation. +This product includes software developed by the Apache Software Foundation.
  • Source for the I2P code and most bundled client applications can be found on our download page.
-

For details on other applications available, as well as their licenses, please see the -license policy. Additional licenses can be found in the licenses sub-directory of your I2P installation.

+

For details on other applications available, as well as their licenses, please see the license policy. +Additional licenses can be found in the licenses sub-directory of your I2P installation.

diff --git a/apps/routerconsole/jsp/help-sidebar.jsi b/apps/routerconsole/jsp/help-sidebar.jsi index 3c3014b3c4..c39a732749 100644 --- a/apps/routerconsole/jsp/help-sidebar.jsi +++ b/apps/routerconsole/jsp/help-sidebar.jsi @@ -1,6 +1,7 @@

Summary Bar Information

-

Many of the stats on the summary bar may be configured to be graphed for further analysis. You may also customize the sections that appear on the Summary Bar and their positioning on the Summary Bar Configuration page. +

Many of the stats on the summary bar may be configured to be graphed for further analysis. +You may also customize the sections that appear on the Summary Bar and their positioning on the Summary Bar Configuration page.

Router Info

@@ -8,20 +9,34 @@
  • Local Identity: -If you hover over the Router Info heading, your truncated router identity will be shown (the first four characters (24 bits) of your 44-character (256-bit) Base64 router hash). The full hash is shown on your Network Database entry. Never reveal this to anyone, as your router identity is uniquely linked to your IP address in the network database.
    • +If you hover over the "Router Info" heading, your truncated router identity will be shown (the first four characters (24 bits) of your 44-character (256-bit) Base64 router hash). +The full hash is shown on your Network Database entry. +Never reveal this to anyone, as your router identity is uniquely linked to your IP address in the network database.
  • Version: -The version of the I2P software you are running. If a new version is available, you will be notified in the Summary Bar. It is recommended to keep your router up to date to ensure optimal performance and security. Router updates are usually made available on average every 2-3 months. +The version of the I2P software you are running. +If a new version is available, you will be notified in the Summary Bar. +It is recommended to keep your router up to date to ensure optimal performance and security. +Router updates are usually made available on average every 2-3 months.
  • Clock Skew: -The skew (offset) of your computer's clock relative to the network-synced time (if known). I2P requires your computer's time be accurate. If the skew is more than a few seconds, please correct the problem by adjusting your computer's time. If I2P cannot connect to the internet, a reading of 0ms may be indicated. Note: This is only displayed in the Router Information (advanced) section. You may add this section to your Summary Bar on the Summary Bar Configuration page. +The skew (offset) of your computer's clock relative to the network-synced time (if known). +I2P requires your computer's time be accurate. +If the skew is more than a few seconds, please correct the problem by adjusting your computer's time. +If I2P cannot connect to the internet, a reading of 0ms may be indicated. +Note: This is only displayed in the "Router Information (advanced)" section. +You may add this section to your Summary Bar on the Summary Bar Configuration page.
  • Memory: -This indicates the amount of RAM I2P is using, and the total amount available, allocated by Java. The usage will likely vary considerably within a short timeframe, but if the usage is consistently high relative to the available RAM, this may indicate that you need to increase the ram allocated to the JVM. You can allocate more RAM by editing your wrapper.config file which is normally located in the I2P application directory. You will need to edit the wrapper.java.maxmemory parameter, which by default is set to 128(MB). Note: Memory usage is only displayed in the Router Information (advanced) section or on the Memory Usage Bar, both of which may be added to your Summary Bar on the Summary Bar Configuration page. +This indicates the amount of RAM I2P is using, and the total amount available, allocated by Java. +The usage will likely vary considerably within a short timeframe, but if the usage is consistently high relative to the available RAM, this may indicate that you need to increase the ram allocated to the JVM. +You can allocate more RAM by editing your wrapper.config file which is normally located in the I2P application directory. +You will need to edit the wrapper.java.maxmemory parameter, which by default is set to 128(MB). +Note: Memory usage is only displayed in the "Router Information (advanced)" section or on the "Memory Usage Bar", both of which may be added to your Summary Bar on the Summary Bar Configuration page.
    • <% @@ -38,29 +53,55 @@ The router's view of whether it can be contacted by other routers. See [Enable graphing]. +Active: The first number is the number of peers your router has sent or received a message from in the last few minutes. +This may range from 8-10 to several hundred, depending on your total bandwidth, shared bandwidth, and locally-generated traffic. +The second number is the number of peers seen in the last hour or so. +Do not be concerned if these numbers vary widely. +[Enable graphing].
  • -Fast: This is the number of peers your router has available for building client tunnels. It is generally in the range 8-30. Your fast peers are shown on the Profiles page. [Enable graphing] +Fast: This is the number of peers your router has available for building client tunnels. +It is generally in the range 8-30. Your fast peers are shown on the Profiles page. +[Enable graphing]
  • High Capacity: -This is the number of peers your router has available for building your exploratory tunnels which are used to determine network performance. It is generally in the range 8-75. The fast peers are included in the high capacity tier.Your high capacity peers are shown on the Profiles page. [Enable graphing] +This is the number of peers your router has available for building your exploratory tunnels which are used to determine network performance. +It is generally in the range 8-75. +The fast peers are included in the high capacity tier. +Your high capacity peers are shown on the Profiles page. +[Enable graphing]
  • -Integrated: This is the number of peers your router will use for network database inquiries. These are usually the "floodfill" routers which are responsible for maintaining network integrity. Your well integrated peers are shown on the bottom of the Profiles page. +Integrated: This is the number of peers your router will use for network database inquiries. +These are usually the "floodfill" routers which are responsible for maintaining network integrity. +Your well integrated peers are shown on the bottom of the Profiles page.
  • -Known: This is the total number of peers that are known by your router. They are listed on the Network Database page. This may range from under 100 to 1000 or more. This number is not the total size of the network; it may vary widely depending on your total bandwidth, shared bandwidth, and locally-generated traffic. I2P does not require a router to know every other router in the network. +Known: This is the total number of peers that are known by your router. +They are listed on the Network Database page. +This may range from under 100 to 1000 or more. +This number is not the total size of the network; it may vary widely depending on your total bandwidth, shared bandwidth, and locally-generated traffic. +I2P does not require a router to know every other router in the network.

Bandwidth In/Out

-

This section indicates your average bandwidth speeds and total usage for the session. All values are in bytes per second, not bits per second. You may change your bandwidth limits on the Bandwidth Configuration page. The more bandwidth you make available, the more you help the network and improve your own anonymity, so please take the time to review the settings. If you are unsure of your network's speed, using a service such as SpeedTest or similar will give you a good indication of your bandwidth capability. Your upstream share amount (KBps Out) will determine your overall contribution to the network. Bandwidth is graphed by default.

+

This section indicates your average bandwidth speeds and total usage for the session. +All values are in bytes per second, not bits per second. +You may change your bandwidth limits on the Bandwidth Configuration page. +The more bandwidth you make available, the more you help the network and improve your own anonymity, so please take the time to review the settings. +If you are unsure of your network's speed, using a service such as SpeedTest or similar will give you a good indication of your bandwidth capability. +Your upstream share amount (KBps Out) will determine your overall contribution to the network. +Bandwidth is graphed by default.

Local Destinations

-

These are the local services provided by your router. They may be clients started through the Tunnel Manager or external programs connecting through SAM, BOB, or directly to I2CP. By default, most of your client services (mail, http proxy, IRC) will share the same set of tunnels (for performance reasons) and be listed as Shared Clients and Shared Clients(DSA). However, if you experience a tunnel failure, all your services will go offline at the same time, so in some scenarios you may wish to configure client services to use their own set of tunnels. This can be done by unchecking the Share tunnels with other clients… option listed under Shared Clients on the configuration page of the relevant client service in the Tunnel Manager, after which you will need to restart the client service from the main Tunnel Manager page.

+

These are the local services provided by your router. +They may be clients started through the Tunnel Manager or external programs connecting through SAM, BOB, or directly to I2CP. +By default, most of your client services (mail, http proxy, IRC) will share the same set of tunnels (for performance reasons) and be listed as "Shared Clients" and "Shared Clients(DSA)". +However, if you experience a tunnel failure, all your services will go offline at the same time, so in some scenarios you may wish to configure client services to use their own set of tunnels. +This can be done by unchecking the "Share tunnels with other clients…" option listed under "Shared Clients" on the configuration page of the relevant client service in the Tunnel Manager, after which you will need to restart the client service from the main Tunnel Manager page.

Tunnels

@@ -74,23 +115,37 @@ This is the number of peers your router has available for building your explorat Client: Tunnels built by your router for each client's use.
  • -Participating: Tunnels built by other routers through your router. This may vary widely depending on network demand, your shared bandwidth, and amount of locally-generated traffic. The recommended method for limiting participating tunnels is to change your share percentage on the Bandwidth Configuration page. You may also limit the total number by setting router.maxParticipatingTunnels=nnn on the Advanced configuration page. [Enable graphing]. +Participating: Tunnels built by other routers through your router. +This may vary widely depending on network demand, your shared bandwidth, and amount of locally-generated traffic. +The recommended method for limiting participating tunnels is to change your share percentage on the Bandwidth Configuration page. +You may also limit the total number by setting router.maxParticipatingTunnels=nnn on the Advanced configuration page. +[Enable graphing].
  • -Share Ratio: The number of participating tunnels you route for others, divided by the total number of hops in all your exploratory and client tunnels. A number greater than 1.00 means you are contributing more tunnels to the network than you are using. +Share Ratio: The number of participating tunnels you route for others, divided by the total number of hops in all your exploratory and client tunnels. +A number greater than 1.00 means you are contributing more tunnels to the network than you are using.

    • Congestion

    -

    Note: This section is not enabled by default. You may enable it on the Summary Bar Configuration page.

    +

    Note: This section is not enabled by default. +You may enable it on the Summary Bar Configuration page.

    Some basic indications of router overload:

    • -Job Lag: How long jobs are waiting before execution. The job queue is listed on the Jobs page. Unfortunately, there are several other job queues in the router that may be congested, and their status is not available in the router console. The job lag should generally be zero. If it is consistently higher than 500ms, your computer is very slow, your network is experiencing connectivity issues, or the router has serious problems. [Enable graphing]. +Job Lag: How long jobs are waiting before execution. +The job queue is listed on the Jobs page. +Unfortunately, there are several other job queues in the router that may be congested, and their status is not available in the router console. +The job lag should generally be zero. +If it is consistently higher than 500ms, your computer is very slow, your network is experiencing connectivity issues, or the router has serious problems. +[Enable graphing].
    • -Message Delay: How long an outbound message waits in the queue. This should generally be a few hundred milliseconds or less. If it is consistently higher than 1000ms, your computer is very slow, or you should adjust your bandwidth limits, or your (Bittorrent?) clients may be sending too much data and should have their transmit bandwidth limit reduced. [Enable graphing] (transport.sendProcessingTime). +Message Delay: How long an outbound message waits in the queue. +This should generally be a few hundred milliseconds or less. +If it is consistently higher than 1000ms, your computer is very slow, or you should adjust your bandwidth limits, or your (Bittorrent?) clients may be sending too much data and should have their transmit bandwidth limit reduced. +[Enable graphing] (transport.sendProcessingTime).
      • <% @@ -105,7 +160,9 @@ This is the number of peers your router has available for building your explorat %>
    • -Accepting/Rejecting: Your router's status on accepting or rejecting requests from other routers to build a participating tunnel through your router. Your router may accept all requests, accept or reject a percentage of requests, or reject all requests for a number of reasons, to control the bandwidth and CPU demands and maintain capacity for local clients. Note: It will take at least 10 minutes from your router starting for it to accept building participating tunnels in order to ensure your router is stable and successfully bootstrapped to the network. +Accepting/Rejecting: Your router's status on accepting or rejecting requests from other routers to build a participating tunnel through your router. +Your router may accept all requests, accept or reject a percentage of requests, or reject all requests for a number of reasons, to control the bandwidth and CPU demands and maintain capacity for local clients. +Note: It will take at least 10 minutes from your router starting for it to accept building participating tunnels in order to ensure your router is stable and successfully bootstrapped to the network.