<li><ahref="#badcontent">{% trans %}I am opposed to certain types of content. How do I keep from distributing, storing, or accessing them?{% endtrans %}</a></li>
<li><ahref="#cpu">{% trans %}My router is using too much CPU?!?{% endtrans %}</a></li>
<li><ahref="#reseed">{% trans %}My router has been up for several minutes and has zero or very few connections{% endtrans %}</a></li>
<li><ahref="#peers">{% trans %}My router has very few active peers, is this OK?{% endtrans %}</a></li>
<li><ahref="#vary">{% trans %}My active peers / known peers / participating tunnels / connections / bandwidth vary dramatically over time! Is anything wrong?{% endtrans %}</a></li>
<li><ahref="#slow">{% trans %}Why is I2P so slow?{% endtrans %}</a></li>
<li><ahref="#protocolfamily">{% trans %}In <code>wrapper.log</code> I see an error stating <code>Protocol family unavailable</code> when I2P is loading{% endtrans %}</a></li>
An eepsite is a website that is hosted anonymously, a hidden service which is accessible through your web browser.
It can be accessed by setting your web browser's HTTP proxy to use the I2P web proxy (typically it listens on localhost port 4444), and browsing to the site.
{% trans %}I can't access regular Internet sites through I2P.{% endtrans %}</a></span>
</h3>
<p>{% trans -%}
I2P is primarily not intended, nor designed, to be used as a proxy to the regular internet.
With that said, there are services which are provided by volunteers that act as proxies to clearnet based content - these are referred to as "outproxies" on the I2P network.
There is an outproxy configured by default in I2P's HTTP client tunnel - false.i2p.
While this service does currently exist, there is no guarantee that it will always be there as it is not an official service provided by the I2P project.
If your main requirement from an anonymous network is the ability to access clearnet resources, we would recommend using <ahref="https://www.torproject.org/">Tor</a>.
{% trans -%}Is using an outproxy safe?{% endtrans %}</a></span>
</h3>
<p>{% trans -%}
I2P does not encrypt the Internet, neither does Tor - for example, through <ahref="https://en.wikipedia.org/wiki/Transport_Layer_Security">Transport Layer Security (TLS)</a>.
I2P and Tor both aim to transport your traffic as-is securely and anonymously over the corresponding network, to its destination.
Any unencrypted traffic generated at your system will arrive at the outproxy (on I2P) or the exit node (on Tor) as unencrypted traffic.
This means that you are vulnerable to snooping by the outproxy operators.
One way to protect your outproxy traffic against this is to ensure that any traffic that will be handled by the outproxy is encrypted with TLS.
I2P is an anonymous network - it is designed to withstand attempts at blocking or censoring of content, thus providing a means for communication that anyone can use.
I2P traffic that transits through your router is encrypted with several layers of encryption.
Except in the case of a serious security vulnerability (of which none are currently known),
it is not possible to know what the contents of the traffic are and thus not possible to distinguish between traffic which one is opposed to or not opposed to.
{% trans %}How do I configure my browser?{% endtrans %}</a></span>
</h3>
<p>{% trans browserconfig=site_url('about/browser-config') -%}
The proxy config for different browsers is on a <ahref="{{ browserconfig }}"> separate page</a> with screenshots.
More advanced configs with external tools, such as the browser plug-in FoxyProxy or the proxy server Privoxy, are possible but could introduce leaks in your setup.
{% trans %}How do I connect to IRC within I2P?{% endtrans %}</a></span>
</h3>
<p>{% trans %}
A tunnel to the main IRC server within I2P, Irc2P, is created when I2P is installed (see the <ahref="http://localhost:7657/i2ptunnel/index.jsp">I2PTunnel configuration page</a>), and is automatically started when the I2P router starts.
To connect to it, tell your IRC client to connect to <code>localhost 6668</code>.
HexChat-like client users can create a new network with the server <code>localhost/6668</code> (remember to tick "Bypass proxy server" if you have a proxy server configured).
Weechat users can use the following command to add a new network:
<li>{% trans -%}Internet-facing ports<br> Note: Since release 0.7.8, new installs do not use port 8887;
a random port between 9000 and 31000 is selected when the program is run for the first time.
The selected port is shown on the router <ahref="http://127.0.0.1:7657/confignet">configuration page</a>.{%- endtrans %}<br>
<b>{% trans %}OUTBOUND{% endtrans %}</b>
<ul>
<li>{% trans -%}UDP from the random port listed on the <ahref="http://127.0.0.1:7657/confignet">configuration page</a> to arbitrary remote UDP ports, allowing for replies{%- endtrans %}</li>
<li>{% trans -%}TCP from random high ports to arbitrary remote TCP ports{%- endtrans %}</li>
<li>{% trans -%}Outbound UDP on port 123, allowing for 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){%- endtrans %}</li>
</ul>
<b>{% trans %}INBOUND{% endtrans %}</b>
<ul>
<li>{% trans -%}(Optional, recommended) UDP to the port noted on the <ahref="http://127.0.0.1:7657/confignet">configuration page</a> from arbitrary locations{%- endtrans %}</li>
<li>{% trans -%}(Optional, recommended) TCP to the port noted on <ahref="http://127.0.0.1:7657/confignet">configuration page</a> from arbitrary locations{%- endtrans %}</li>
<li>{% trans -%}Inbound TCP can be disabled on the <ahref="http://127.0.0.1:7657/confignet">configuration page</a>{%- endtrans %}</li>
<li>{% trans -%}Local I2P ports, listening only to local connections by default, except where noted:{%- endtrans %}<br>
<table>
<tr>
<th>
{% trans %}PORT{% endtrans %}
</th>
<th>
{% trans %}PURPOSE{% endtrans %}
</th>
<th>
{% trans %}DESCRIPTION{% endtrans %}
</th>
</tr>
<tr>
<td>
1900
</td>
<td>
UPnP SSDP UDP multicast listener
</td>
<td>
{% trans %}Cannot be changed. Binds to all interfaces. May be disabled on <ahref="http://127.0.0.1:7657/confignet">confignet</a>.{% endtrans %}
</td>
</tr>
<tr>
<td>
2827
</td>
<td>
BOB bridge
</td>
<td>
{% trans -%}A higher level socket API for clients. Disabled by default. May be enabled/disabled on <ahref="http://127.0.0.1:7657/configclients">configclients</a>.
May be changed in the bob.config file.{%- endtrans %}
</td>
</tr>
<tr>
<td>
4444
</td>
<td>
HTTP proxy
</td>
<td>
{% trans %}May be disabled or changed on the i2ptunnel page in the router console. May also be configured to be bound to a specific interface or all interfaces.{% endtrans %}
</td>
</tr>
<tr>
<td>
4445
</td>
<td>
HTTPS proxy
</td>
<td>
{% trans %}May be disabled or changed on the i2ptunnel page in the router console. May also be configured to be bound to a specific interface or all interfaces.{% endtrans %}
</td>
</tr>
<tr>
<td>
6668
</td>
<td>
IRC proxy
</td>
<td>
{% trans %}May be disabled or changed on the i2ptunnel page in the router console. May also be configured to be bound to a specific interface or all interfaces.{% endtrans %}
</td>
</tr>
<tr>
<td>
7652
</td>
<td>
HTTP TCP event listener
</td>
<td>
{% trans -%}Binds to the LAN address.
May be changed with advanced config <code>i2np.upnp.HTTPPort=nnnn</code>.
May be disabled on <ahref="http://127.0.0.1:7657/confignet">confignet</a>.{%- endtrans %}
</td>
</tr>
<tr>
<td>
7653
</td>
<td>
UPnP SSDP UDP search response listener
</td>
<td>
{% trans -%}Binds to the LAN address.
May be changed with advanced config <code>i2np.upnp.SSDPPort=nnnn</code>.
May be disabled on <ahref="http://127.0.0.1:7657/confignet">confignet</a>.{%- endtrans %}
</td>
</tr>
<tr>
<td>
7654
</td>
<td>
I2P Client Protocol port
</td>
<td>
{% trans -%}Used by client apps.
May be changed to a different port on <ahref="http://127.0.0.1:7657/configclients">configclients</a> but this is not recommended.
May be to bind to a different interface or all interfaces, or disabled, on <ahref="http://127.0.0.1:7657/configclients">configclients</a>.{%- endtrans %}
</td>
</tr>
<tr>
<td>
7655
</td>
<td>
UDP for SAM bridge
</td>
<td>
{% trans -%}A higher level socket API for clients Only opened when a SAM V3 client requests a UDP session.
May be enabled/disabled on <ahref="http://127.0.0.1:7657/configclients">configclients</a>.
May be changed in the <code>clients.config</code> file with the SAM command line option <code>sam.udp.port=nnnn</code>.{%- endtrans %}
</td>
</tr>
<tr>
<td>
7656
</td>
<td>
SAM bridge
</td>
<td>
{% trans -%}A higher level socket API for clients Disabled by default for new installs as of release 0.6.5.
May be enabled/disabled on <ahref="http://127.0.0.1:7657/configclients">configclients</a>.
May be changed in the <code>clients.config</code> file.{%- endtrans %}
</td>
</tr>
<tr>
<td>
7657
</td>
<td>
Your <ahref="http://127.0.0.1:7657">router console</a>
</td>
<td>
{% trans -%}May be disabled in the <code>clients.config</code>file.
May also be configured to be bound to a specific interface or all interfaces in that file.{%- endtrans %}
</td>
</tr>
<tr>
<td>
7658
</td>
<td>
Your <ahref="http://127.0.0.1:7658">eepsite</a>
</td>
<td>
{% trans -%}May be disabled in the <code>clients.config</code> file.
May also be configured to be bound to a specific interface or all interfaces in the <code>jetty.xml</code> file.{%- endtrans %}
</td>
</tr>
<tr>
<td>
7659
</td>
<td>
Outgoing mail to smtp.postman.i2p
</td>
<td>
{% trans -%}May be disabled or changed on the i2ptunnel page in the router console.
May also be configured to be bound to a specific interface or all interfaces.{%- endtrans %}
</td>
</tr>
<tr>
<td>
7660
</td>
<td>
Outgoing mail to smtp.postman.i2p
</td>
<td>
{% trans -%}May be disabled or changed on the i2ptunnel page in the router console.
May also be configured to be bound to a specific interface or all interfaces.{%- endtrans %}
</td>
</tr>
<tr>
<td>
8998
</td>
<td>
mtn.i2p-projekt.i2p (Monotone)
</td>
<td>
{% trans -%}May be disabled or changed on the i2ptunnel page in the router console.
May also be configured to be bound to a specific interface or all interfaces.{%- endtrans %}
</td>
</tr>
<tr>
<td>
31000
</td>
<td>
Local connection to the wrapper control channel port
</td>
<td>
{% trans -%}Outbound 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 <ahref="http://wrapper.tanukisoftware.com/doc/english/prop-port.html">wrapper documentation</a>.
For more information see <ahref="#port32000">below</a>.{%- endtrans %}
</td>
</tr>
<tr>
<td>
32000
</td>
<td>
Local control channel for the service wrapper
</td>
<td>
{% trans -%}To change, see the <ahref="http://wrapper.tanukisoftware.com/doc/english/prop-port.html">wrapper documentation</a>.
For more information see <ahref="#port32000">below</a>.{%- endtrans %}
<li>{% trans -%}My router often displays a message saying "Website Not Found In Addressbook", why do I see this message?{%- endtrans %}
<p>{% trans -%}Human-readable addresses such as <i>http://website.i2p</i> are references to a long, random string known as a <b>destination</b>.
These references are registered and stored at addressbook services such as stats.i2p, which is run by zzz.
You will often encounter a "b32" address. A "b32" is a hash (specifically, a <ahref="https://en.wikipedia.org/wiki/SHA-2">SHA256</a> hash) of the
destination. This hash is appended with ".b32.i2p" and serves as a convenient way to link to your hidden service, without requiring any registration on an addressbook service.{%- endtrans %}</p>
<p>{% trans -%}It is possible to add subscriptions to your router's configuration which may reduce the frequency of these messages.{%- endtrans %}</p></li>
<li>{% trans -%}What is an addressbook subscription?{%- endtrans %}
<p>{% trans -%}This is a list of files hosted on various I2P websites each of which contain a list of I2P hosts and their associated destinations.{%- endtrans %}</p>
<p>{% trans -%}The addressbook is located at <ahref="http://localhost:7657/dns">http://localhost:7657/dns</a> where further information can be found.{%- endtrans %}</p></li>
<li>{% trans -%}What are some good addressbook subscription links?{%- endtrans %}
<p>{% trans -%}You may try the following:{%- endtrans %}</p>
{% trans -%}If you are running a Unix-like Operating System, this is the easiest method for remotely accessing your I2P console.
(Note: SSH server software is available for systems running Windows, for example <ahref="https://github.com/PowerShell/Win32-OpenSSH">https://github.com/PowerShell/Win32-OpenSSH</a>){%- endtrans %}<br>
{% trans %}Once you have configured SSH access to your system, the '-L' flag is passed to SSH with appropriate arguments - for example:{% endtrans %}
<code>
<pre>
ssh -L 7657:localhost:7657 (System_IP)
</pre>
</code>
where '(System_IP)' is replaced with your System's IP address.
This command forwards port 7657 (the number before the first colon) to the remote system's (as specified by the string 'localhost' between the first and second colons) port 7657 (the number after the second colon).
Your remote I2P console will now be available on your local system as 'http://localhost:7657' and will be available for as long as your SSH session is active.
If you would like to start an SSH session without initiating a shell on the remote system, you can add the '-N' flag:
<code>
<pre>
ssh -NL 7657:localhost:7657 (System_IP)
</pre>
</code>
</li>
<li>{% trans %}Configuring your console to be available on a Public IP address with a username & password{% endtrans %}<br>
<ol>
<li>{% trans %}Open <code>~/.i2p/clients.config</code> and replace{% endtrans %}
where you replace (System_IP) with your system's public IP
address</li>
<li>{% trans -%}Go to <ahref="http://localhost:7657/configui">http://localhost:7657/configui</a> and add a console username and password if desired -
Adding a username & password is highly recommended to secure your I2P console from tampering, which could lead to de-anonymization.{%- endtrans %}</li>
<li>{% trans -%}Go to <ahref="http://localhost:7657/index">http://localhost:7657/index</a> and hit "Graceful restart",
which restarts the JVM and reloads the client applications{%- endtrans %}</li>
</ol>
{% trans -%}After that fires up, you should now be able to reach your console remotely.
Load the router console at <code>http://(System_IP):7657</code> and you will be prompted for the username and password you specified in step 2 above if your browser supports the authentication popup.{%- endtrans %}
<br>
{% trans -%}NOTE: You can specify 0.0.0.0 in the above configuration.
This specifies an interface, not a network or netmask.
0.0.0.0 means "bind to all interfaces", so it can be reachable on 127.0.0.1:7657 as well as any LAN/WAN IP.
Be careful when using this option as the console will be available on ALL addresses configured on your system.{%- endtrans %}</li>
Many applications leak sensitive information that could identify you on the Internet and this is a risk that one should be aware of when using the I2P SOCKS proxy.
I2P only filters connection data, but if the program you intend to run sends this information as content, I2P has no way to protect your anonymity.
For example, some mail applications will send the IP address of the machine they are running on to a mail server.
There is no way for I2P to filter this, thus using I2P to 'socksify' existing applications is possible, but extremely dangerous.
Please be aware that the Tor project <ahref="https://blog.torproject.org/bittorrent-over-tor-isnt-good-idea">recommends against using BitTorrent over Tor</a>,
as there are serious anonymity-related issues associated with doing so.
There are no FTP "outproxies" to the Internet—it may not even be possible to set up one.
Any other kind of outproxy may work if it's set up with a standard tunnel.
If you would like to set up some type of outproxy, carefully research the potential risks.
The I2P community may or may not be able to help with the technical aspects, feel free to ask.
As explained several times above, any existing outproxy isn't a core part of the network.
They are services run by individuals and they may or may not be operational at any given time.
{%- endtrans %}
</li>
</ul>
<h2>Troubleshooting</h2>
<h3id="cpu"><spanclass="permalink"><ahref="#cpu">
{% trans %}My router is using a large amount of CPU, what can I do about this?{% endtrans %} </a></span></h3>
<p>{% trans -%}
There are many possible causes of high CPU usage. Here is a checklist:
{%- endtrans %}</p>
<ul>
<li>
<b>{% trans -%}Java Runtime Environment{%- endtrans %}</b><br>
{% trans -%}Try to use either OpenJDK or Sun/Oracle Java if it's available for your system.
You can check which version of java you have installed by typing <code>java -version</code> at a command/shell prompt.
Performance tends to suffer with other implementations of java.{%- endtrans %}
</li>
<li>
<b>{% trans -%}File sharing applications, e.g. BitTorrent{%- endtrans %}</b><br>
{% trans -%}
Are you running a BitTorrent client over I2P? Try reducing the number of torrents, the bandwidth limits,
or try turning it off completely to see if that helps.
{%- endtrans %}
</li>
<li>
<b>{% trans -%}High bandwidth settings{%- endtrans %}</b><br>
{% trans -%}
Are your bandwidth limits set too high? It is possible that too much traffic is going through your I2P router and it is overloaded.
Try reducing the setting for <em>share bandwidth percentage</em> on the <ahref="http://localhost:7657/config">configuration</a> page.
{%- endtrans %}</li>
<li>
<b>{% trans -%}I2P Version{%- endtrans %}</b><br>
{% trans -%}
Make sure that you're running the latest version of I2P to get the benefits of increased performance and bug fixes.
{%- endtrans %}
</li>
<li>
<b>{% trans -%}Memory allocation{%- endtrans %}</b><br>
{% trans -%}
Has enough memory been set aside for use by I2P? Look at the memory graph on <ahref="http://localhost:7657/graphs">the graphs page</a>
to see if the memory usage is "pegged"—the JVM is spending most of its time in garbage collection.
Increase the setting <code>wrapper.java.maxmemory</code> in the file <code>wrapper.config</code>.
{%- endtrans %}
</li>
<li>
<b>{% trans -%}Bursts of high-usage vs. constant 100% usage{%- endtrans %}</b><br>
{% trans -%}
Is the CPU usage simply higher than you would like, or is it pegged at 100% for a long time?
If it is pegged, this could be a bug. Look in the logs for clues.
{%- endtrans %}
</li>
<li>
<b>{% trans -%}Java-related{%- endtrans %}</b><br>
{% trans jbigi=site_url('misc/jbigi') -%}
You may be using the Java-based BigInteger library instead of the native version, especially if you are running on a new or unusual OS or hardware (OpenSolaris, mipsel, etc.).
See the <ahref="{{ jbigi }}">jbigi page</a> for instructions on diagnosing, building, and testing methods.
{%- endtrans %}
</li>
<li>
<b>{% trans -%}Participating tunnels{%- endtrans %}</b><br>
{% trans -%}
If your native jbigi library is working fine, the biggest user of CPU may be routing traffic for participating tunnels.
This uses CPU because at each hop a layer of encryption must be decoded. You can limit participating traffic in two ways -
by reducing the share bandwidth on the <ahref="http://localhost:7657/confignet.jsp">confignet</a> page,
or by setting <tt>router.maxParticipatingTunnels=nnn</tt> on the <ahref="http://localhost:7657/configadvanced.jsp">configadvanced</a> page.
{% trans %}My active peers / known peers / participating tunnels / connections / bandwidth vary dramatically over time! Is anything wrong?{% endtrans %}</a></span>
</h3>
<p>{% trans -%}
No, there isn't anything wrong.
This is normal behavior.
All routers adjust dynamically to changing network conditions and demands.
Routers come online and go offline depending on whether the system it is installed on is operational or not, as well as whether there is an available network connection.
Your router is constantly updating its local Network Database.
Tunnels which your router is participating in expire every 10 minutes and may or may not be rebuilt through your router.
{% trans %}What makes downloads, torrents, web browsing, and everything else slower on I2P as compared to the regular internet?{% endtrans %}</a></span>
</h3>
<p>{% trans -%}
The encryption and routing within the I2P network adds a substantial amount of overhead and limits bandwidth.
We can try to clarify this with the aid of a diagram:
{%- endtrans %}</p>
<imgsrc="/_static/images/i2p_traffic_path.jpg">
<p>{% trans -%}
In this diagram, the path that some I2P traffic takes as it travels through the network is traced.
A user's I2P router is denoted by the box labeled 'A' and an I2P Hidden Service (for example, the http://stats.i2p website) is labelled as 'B'.
Both the client and the server are using 3-hop tunnels, these hops are represented by the boxes labelled 'P', 'Q', 'R', 'X', 'Y', 'Z', 'P_1', 'Q_1', 'R'_1, 'X_1', 'Y_1' and 'Z_1'.
The boxes labelled 'P', 'Q' and 'R' represent an outbound tunnel for A while the boxes labelled 'X_1', 'Y_1', 'Z_1' represent an outbound tunnel for 'B'.
Similarly, the boxes labelled 'X', 'Y' and 'Z' represent and inbound tunnel for 'B' while the boxes labelled 'P_1', 'Q_1' and 'R_1' represent an inbound tunnel for 'A'.
The arrows in between the boxes show the direction of traffic.
The text above and below the arrows detail some example bandwidth between a pair of hops as well as example latencies.
{%- endtrans %}</p>
<p>{% trans -%}
When both client and server are using 3-hop tunnels throughout, a total of 12 other I2P routers are involved in relaying traffic.
6 peers relay traffic from the client to the server which is split into a 3-hop outbound tunnel from 'A' ('P', 'Q', 'R') and a 3-hop inbound tunnel to 'B' ('X', 'Y', 'Z').
Similarly, 6 peers relay traffic from the server to back to the client.
{%- endtrans %}</p>
<p>{% trans -%}
First, we can consider latency - the time that it takes for a request from a client to traverse the I2P network, reach the the server and traverse back to the client.
Adding up all latencies we see that:
{%- endtrans %}</p>
<code>
<pre>
40 + 100 + 20 + 60 + 80 + 10 + 30 ms (client to server)
+ 60 + 40 + 80 + 60 + 100 + 20 + 40 ms (server to client)
-----------------------------------
TOTAL: 740 ms
</pre>
</code>
<p>{% trans -%}
The total round-trip time in our example adds up to 740 ms - certainly much higher than what one would normally see while browsing regular internet websites.
{%- endtrans %}</p>
<p>{% trans -%}
Second, we can consider available bandwidth.
This is determined through the slowest link between hops from the client and server as well as when traffic is being transmitted by the server to the client.
For traffic going from the client to the server, we see that the available bandwidth in our example between hops 'R' & 'X' as well as hops 'X' & 'Y' is 32 KB/s.
Despite higher available bandwidth between the other hops, these hops will act as a bottleneck and will limit the maximum available bandwidth for traffic from 'A' to 'B' at 32 KB/s.
Similarly, tracing the path from server to client shows that there is maximum bandwidth of 64 KB/s - between hops 'Z_1' & 'Y_1, 'Y_1' & 'X_1' and 'Q_1' & 'P_1'.
{%- endtrans %}</p>
<p>{% trans -%}
We recommend increasing your bandwidth limits.
This helps the network by increasing the amount of available bandwidth which will in turn improve your I2P experience.
Bandwidth settings are located on the <ahref="http://localhost:7657/config">http://localhost:7657/config</a> page.
Please be aware of your internet connection's limits as determined by your ISP, and adjust your settings accordingly.
{%- endtrans %}</p>
<p>{% trans -%}
We also recommend setting a sufficient amount of shared bandwidth - this allows for participating tunnels to be routed through your I2P router.
Allowing participating traffic keeps your router well-integrated in the network and improves your transfer speeds.
{%- endtrans %}</p>
<p>{% trans downloadslist=get_url('downloads_list') -%}
I2P is a work in progress. Lots of improvements and fixes are being implemented, and, generally speaking, running the latest release will help your performance.
If you haven't, <ahref="{{ downloadslist }}">install the latest release</a>.
{% trans %}In <code>wrapper.log</code> I see an error that states "<code>Protocol family unavailable</code>" when loading the Router Console{% endtrans %}</a></span>
Often this error will occur with any network enabled java software on some systems that are configured to use IPv6 by default. There are a few ways to solve this:
{% trans %}Why is I2P listening on port 32000?{% endtrans %}</a></span>
</h3>
<p>{% trans -%}
The Tanuki java service wrapper that we use opens this port —bound to localhost— in order to communicate with software running inside the JVM.
When the JVM is launched it is given a key so it can connect to the wrapper.
After the JVM establishes its connection to the wrapper, the wrapper refuses any additional connections.
{%- endtrans %}</p>
<p>{% trans -%}
More information can be found in the <ahref="http://wrapper.tanukisoftware.com/doc/english/prop-port.html">wrapper documentation</a>.
{%- endtrans %}</p>
<h3id="bug"><spanclass="permalink"><ahref="#bug">
{% trans %}I think I found a bug, where can I report it?{% endtrans %}</a></span></h3>
<p>{% trans -%}
You may report any bugs/issues that you encounter on our bugtracker, which is available over both clearnet and I2P.
We have a discussion forum, also available on I2P and clearnet. You can join our IRC channel as well:
either through our IRC network, IRC2P, or on Freenode.{%- endtrans %}</p>
<ul>
<li>{% trans -%}Our Bugtracker:{%- endtrans %}
<ul>
<li>{% trans -%}Clearnet:{%- endtrans %} <ahref="https://trac.i2p2.de/report/1">https://trac.i2p2.de/report/1</a></li>
<li>{% trans -%}On I2P:{%- endtrans %} <ahref="http://trac.i2p2.i2p/report/1">http://trac.i2p2.i2p/report/1</a></li>
