I2P Router Help and Support

Further Assistance

If you would like to help improve or translate the documentation, or help with other aspects of the project, please see the documentation for volunteers.

Further assistance is available here:

• FAQ on i2p-projekt.i2p

You may also try I2P Forum or I2P's IRC network.

Sidebar Information

Many of the stats on the sidebar may be configured to be graphed for further analysis. You may also customize the sections that appear on the Sidebar and their positioning on the Sidebar Configuration page.

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. Your upstream share amount (KBps Out) will determine your overall contribution to the network.

Peers

• 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.
• Fast: This is the number of peers your router has available for building client tunnels. These peers are shown on the profiles page.
• High Capacity: This is the number of peers your router has available for building your exploratory tunnels which are used to determine network performance. The fast peers are included in the high capacity tier. These peers are shown on the profiles page.
• Integrated: This is the number of peers your router will use for network database inquiries. These are usually the floodfill routers responsible for maintaining network integrity. These peers are shown on the profiles page.
• Known: This is the total number of peers that are known by your router. This may range from under 100 to several thousand. 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.

Network Help

While I2P will work fine behind most firewalls, your speeds and network integration will generally improve if the I2P port is forwarded for both UDP and TCP.  If you think you have opened up your firewall and I2P still thinks you are firewalled, remember that you may have multiple firewalls, for example both software packages and external hardware routers.  If there is an error, the logs may also help diagnose the problem.

• OK: Your UDP port does not appear to be firewalled.
• Firewalled: Your UDP port appears to be firewalled.  As the firewall detection methods are not 100% reliable, this may occasionally be displayed in error.  However, if it appears consistently, you should check whether both your external and internal firewalls are open for your port.  I2P will work fine when firewalled, there is no reason for concern. When firewalled, the router uses "introducers" to relay inbound connections.  However, you will get more participating traffic and help the network if you open your firewall.  If you think you have already done so, remember that you may have both a hardware and a software firewall, or be behind an additional, institutional firewall you cannot control.  Also, some routers cannot correctly forward both TCP and UDP on a single port, or may have other limitations or bugs that prevent them from passing traffic through to I2P.
• Testing: The router is currently testing whether your UDP port is firewalled.
• Hidden: The router is not configured to publish its address, therefore it does not expect incoming connections.  Hidden mode is automatically enabled for added protection in certain countries.
• WARN - Firewalled and Fast: You have configured I2P to share more than 128KBps of bandwidth, but you are firewalled.  While I2P will work fine in this configuration, if you really have over 128KBps of bandwidth to share, it will be much more helpful to the network if you open your firewall.
• WARN - Firewalled and Floodfill: You have configured I2P to be a floodfill router, but you are firewalled.  For best participation as a floodfill router, you should open your firewall.
• WARN - Firewalled with Inbound TCP Enabled: You have configured inbound TCP, however your UDP port is firewalled, and therefore it is likely that your TCP port is firewalled as well. If your TCP port is firewalled with inbound TCP enabled, routers will not be able to contact you via TCP, which will hurt the network. Please open your firewall or disable inbound TCP above.
• WARN - Firewalled with UDP Disabled: You have configured inbound TCP, however you have disabled UDP.  You appear to be firewalled on TCP, therefore your router cannot accept inbound connections.  Please open your firewall or enable UDP.
• ERR - Clock Skew: Your system's clock is skewed, which will make it difficult to participate in the network.  Correct your clock setting if this error persists.
• ERR - Private TCP Address: You must never advertise an unroutable IP address such as 127.0.0.1 or 192.168.1.1 as your external address. Correct the address or disable inbound TCP on the Network Configuration page.
• ERR - SymmetricNAT: I2P detected that you are firewalled by a Symmetric NAT. I2P does not work well behind this type of firewall. You will probably not be able to accept inbound connections, which will limit your participation in the network.
• ERR - UDP Port In Use - Set i2np.udp.internalPort=xxxx in advanced config and restart: I2P was unable to bind to the configured port noted on the advanced network configuration page .  Check to see if another program is using the configured port. If so, stop that program or configure I2P to use a different port.  This may be a transient error, if the other program is no longer using the port.  However, a restart is always required after this error.
• ERR - UDP Disabled and Inbound TCP host/port not set: You have not configured inbound TCP with an address and port on the Network Configuration page, however you have disabled UDP.  Therefore your router cannot accept inbound connections.  Please configure a TCP host and port on the Network Configuration page or enable UDP.
• ERR - Client Manager I2CP Error - check logs: This is usually due to a port 7654 conflict. Check the logs to verify.  Do you have another I2P instance running? Stop the conflicting program and restart I2P.

Clock Skew

The skew (offset) of your computer's clock relative to the network-synced time. 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.

Abridged I2P FAQ

This is a shortened version of the official FAQ. For the full version, please visit geti2p.net/faq or 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.

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 connected to the network is to share more bandwidth.

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

The default subscription is to i2p-projekt.i2p which is seldom updated. If you don't have another subscription, you may use "jump" links which are slower, but ensure that your addressbook only contains the default addresses and sites that you use. 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 subscription list.

• http://stats.i2p/cgi-bin/newhosts.txt
• http://notbob.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.

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 public SOCKS outproxy.

How do I configure my browser to access I2P websites?

You will need to configure your browser to use the HTTP proxy server 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 and browsing to the website.

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. 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 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.

HexChat-like client users can create a new network with the server 127.0.0.1/6668, or you can connect with the command /server 127.0.0.1 6668. Different IRC clients may require a different command, consult the client documentation.

What ports does I2P use?