893 lines
43 KiB
HTML
893 lines
43 KiB
HTML
{% extends "global/layout.html" %}
|
|
{% block title %}{{ _('Frequently Asked Questions') }}{% endblock %}
|
|
{% block content_nav %}
|
|
<ol>
|
|
<li style="list-style: none; display: inline">
|
|
<h4>{{ _('General') }}</h4>
|
|
</li>
|
|
<li><a href="#systems">{% trans %}What systems will I2P run on?{% endtrans %}</a></li>
|
|
<li><a href="#eepsite">{% trans %}Whats an "eepsite" and how do I configure my browser so I can use them?{% endtrans %}</a></li>
|
|
<li><a href="#peers">{% trans %}My router has very few active peers, is this OK?{% endtrans %}</a></li>
|
|
<li><a href="#active">{% trans %}What do the Active x/y numbers mean in the router console?{% endtrans %}</a></li>
|
|
<li><a href="#vary">{% trans %}My active peers / known peers / participating tunnels / connections / bandwidth vary dramatically over time! Is anything wrong?{% endtrans %}</a></li>
|
|
<li><a href="#proxy_safe">{% trans %}Is using an outproxy safe?{% endtrans %}</a></li>
|
|
<li><a href="#down">{% trans %}Most of the eepsites within I2P are down?{% endtrans %}</a></li>
|
|
<li><a href="#ports">{% trans %}What ports does I2P use?{% endtrans %}</a></li>
|
|
<li><a href="#port32000">{% trans %}Why is I2P listening for connections on port 32000?{% endtrans %}</a></li>
|
|
<li><a href="#bug">{% trans %}I think I found a bug, where can I report it?{% endtrans %}</a></li>
|
|
<li><a href="#jrandom">{% trans %}What happened to *.i2p.net? What happened to jrandom? Is I2P dead?{% endtrans %}</a></li>
|
|
<li><a href="#java">{% trans %}Is installing Java required to use I2P?{% endtrans %}</a></li>
|
|
<li><a href="#question">{% trans %}I have a question!{% endtrans %}</a></li>
|
|
<li style="list-style: none; display: inline">
|
|
<h4>{{ _('Setup') }}</h4>
|
|
</li>
|
|
<li><a href="#reseed">{% trans %}My router has been up for several minutes and has zero or very few connections{% endtrans %}</a></li>
|
|
<li><a href="#slow">{% trans %}Why is I2P so slow?{% endtrans %}</a></li>
|
|
<li><a href="#subscriptions">{% trans %}I'm missing lots of hosts in my addressbook. What are some good subscription links?{% endtrans %}</a></li>
|
|
<li><a href="#myeepsite">{% trans %}How do I set up my own eepsite?{% endtrans %}</a></li>
|
|
<li><a href="#snark">{% trans %}Bittorrent / I2PSnark / Azureus I2P Plugin Questions?{% endtrans %}</a></li>
|
|
<li><a href="#irc">{% trans %}How do I connect to IRC within I2P?{% endtrans %}</a></li>
|
|
<li><a href="#outproxy">{% trans %}I can't access regular Internet sites through I2P.{% endtrans %}</a></li>
|
|
<li><a href="#https">{% trans %}I can't access https:// or ftp:// sites through I2P.{% endtrans %}</a></li>
|
|
<li><a href="#socks">{% trans %}Is it possible to use I2P as a SOCKS proxy?{% endtrans %}</a></li>
|
|
<li><a href="#browserproxy">{% trans %}How do I configure my browser?{% endtrans %}</a></li>
|
|
<li><a href="#remote_webconsole">{% trans %}How can I access the web console from my other machines or password protect it?{% endtrans %}</a></li>
|
|
<li><a href="#remote_i2cp">{% trans %}How can I use applications from my other machines?{% endtrans %}</a></li>
|
|
<li><a href="#manual_reseed">{% trans %}How do I reseed manually?{% endtrans %}</a></li>
|
|
<li><a href="#cpu">{% trans %}My router is using too much CPU?!?{% endtrans %}</a></li>
|
|
<li style="list-style: none; display: inline">
|
|
<h4>{{ _('Misconception') }}</h4>
|
|
</li>
|
|
<li><a href="#proxy_other">{% trans %}How do I access IRC, BitTorrent, or other services on the regular Internet?{% endtrans %}</a></li>
|
|
<li><a href="#exit">{% trans %}Is my router an "exit node"(outproxy) to the regular Internet? I don't want it to be.{% endtrans %}</a></li>
|
|
<li><a href="#badcontent">{% trans %}I am opposed to certain types of content. How do I keep from distributing, storing, or accessing them?{% endtrans %}</a></li>
|
|
<li style="list-style: none; display: inline">
|
|
<h4>{{ _('Errors and Their Solutions') }}</h4>
|
|
</li>
|
|
<li><a href="#compat6x">{% trans %}I'm using FreeBSD and when I start I2P I receive an error about <code>libm.so.4</code>!{% endtrans %}</a></li>
|
|
<li><a href="#protocolfamily">{% trans %}In <code>wrapper.log</code> I see an error stating <code>Protocol family unavailable</code> when I2P is loading{% endtrans %}</a></li>
|
|
</ol>
|
|
{% endblock %}
|
|
|
|
{% block content %}
|
|
<h3 id="systems">{% trans %}What systems will I2P run on?{% endtrans %}
|
|
<span class="permalink">(<a href="#systems">{{ _('link') }}</a>)</span></h3>
|
|
<p>{% trans chart='https://trac.i2p2.de/wiki/java' -%}
|
|
While I2P has been reported to run PCs as meagre as a low-end Pentium II with 64 MB of RAM, you'll have a much better experience on a Pentium III (or better) with 128MB of RAM (or more). A <a href="{{ chart }}">chart comparing the performance</a> of the various JREs can be found at <a href="{{ chart }}">{{ chart }}</a>, but in short: it's at all possible, use Sun/Oracle Java or OpenJDK.
|
|
{%- endtrans %}</p>
|
|
|
|
<p>{% trans -%}
|
|
I2P has been tested on Windows, Linux, FreeBSD (see the note <a href="#compat6x">below</a>), OSX, and OpenSolaris. There is work underway to bring I2P to the Android platform.
|
|
{%- endtrans %}</p>
|
|
|
|
|
|
<h3 id="bug">{% trans %}I think I found a bug, where can I report it?{% endtrans %}
|
|
<span class="permalink">(<a href="#bug">{{ _('link') }}</a>)</span></h3>
|
|
|
|
{% trans -%}
|
|
Here are some places, pick one or more.
|
|
{%- endtrans %}
|
|
<ul>
|
|
<li><a href="https://trac.i2p2.de/report/1">{{ i2pconv('trac.i2p2.i2p') }}</a> ticket (preferred method)</li>
|
|
<li><a href="http://{{ i2pconv('pastethis.i2p') }}/">{{ i2pconv('pastethis.i2p') }}</a> and follow up on IRC in #i2p</li>
|
|
<li>{% trans -%}
|
|
Discuss with the developers on IRC in #i2p-dev
|
|
{%- endtrans %}</li></ul>
|
|
|
|
<p>{% trans -%}
|
|
Please include relevant information from the router logs and wrapper logs.
|
|
{%- endtrans %}</p>
|
|
|
|
<h3 id="subscriptions">{% trans %}I'm missing lots of hosts in my addressbook. What are some good subscription links?{% endtrans %}
|
|
<span class="permalink">(<a href="#subscriptions">{{ _('link') }}</a>)</span></h3>
|
|
<p>{% trans -%}
|
|
The default subscription is to http://www.i2p2.i2p/hosts.txt which is updated rarely.
|
|
If you don't have another subscription, you may often have to use "jump" links which
|
|
is annoying.
|
|
{%- endtrans %}</p>
|
|
|
|
<p>{% trans -%}
|
|
Here are some other public addressbook subscription links. You may wish to add one or two
|
|
to your <a href="http://localhost:7657/susidns/subscriptions.jsp">susidns subscription list</a>.
|
|
You don't need to add all of them, as they sync with each other periodically.
|
|
The links using a cgi-bin application employ various strategies to minimize
|
|
the number of duplicate addresses delivered, so they should be more efficient.
|
|
Note that subscribing to a hosts.txt service is an act of "trust", as a malicious
|
|
subscription could give you incorrect addresses. So think about whether you
|
|
want to trust any of these.
|
|
The operators of these services may have various policies for listing hosts.
|
|
Presence on this list does not imply endorsement.
|
|
{%- endtrans %}</p>
|
|
|
|
<div class="links">
|
|
<ul>
|
|
<li><a href="http://i2host.i2p/cgi-bin/i2hostetag">http://i2host.i2p/cgi-bin/i2hostetag</a></li>
|
|
<li><a href="http://stats.i2p/cgi-bin/newhosts.txt">http://stats.i2p/cgi-bin/newhosts.txt</a></li>
|
|
<li><a href="http://no.i2p/export/alive-hosts.txt">http://no.i2p/export/alive-hosts.txt</a></li>
|
|
</div>
|
|
|
|
|
|
<h3 id="jrandom">{% trans %}What happened to *.i2p.net? What happened to jrandom? Is I2P dead?{% endtrans %}
|
|
<span class="permalink">(<a href="#jrandom">{{ _('link') }}</a>)</span></h3>
|
|
<p>{% trans -%}
|
|
Jrandom was the lead developer of I2P and
|
|
<a href="http://syndie.i2p2.de/">Syndie</a> for several years.
|
|
We do not know if or when jrandom will return.
|
|
The *.i2p.net domains were left in a non-functioning state after a power
|
|
outage at the hosting company.
|
|
{%- endtrans %}</p>
|
|
|
|
<p>{% trans jrandom=site_url('misc/jrandom-awol'), index=site_url() -%}
|
|
See <a href="{{ jrandom }}">this page</a> for jrandom's parting message and additional information
|
|
on the migration of *.i2p.net to <a href="{{ index }}">this website</a>.
|
|
{%- endtrans %}</p>
|
|
|
|
<p>{% trans %}I2P remains in active development.{% endtrans %}</p>
|
|
|
|
<h3 id="cpu">{% trans %}My router is using too much CPU?!?{% endtrans %}
|
|
<span class="permalink">(<a href="#cpu">{{ _('link') }}</a>)</span></h3>
|
|
<p>{% trans -%}
|
|
There are many possible causes of high CPU usage. Here is a checklist:
|
|
{%- endtrans %}</p>
|
|
<ul>
|
|
<li>
|
|
{% 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>
|
|
{% 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>
|
|
{% 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 <a href="http://localhost:7657/config">configuration</a> page.
|
|
{%- endtrans %}</li>
|
|
<li>
|
|
{% 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>
|
|
{% trans -%}
|
|
Has enough memory been set aside for use by I2P? Look at the memory graph on <a href="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>
|
|
{% trans -%}
|
|
Is the CPU usage simply higher than you would like, or is it pegged at 100% for a long time?
|
|
If it's pegged, this could be a bug. Look in the logs for clues.
|
|
{%- endtrans %}
|
|
</li>
|
|
<li>
|
|
{% 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 <a href="{{ jbigi }}">jbigi page</a> for instructions on
|
|
diagnosing, building, and testing methods.
|
|
{%- endtrans %}
|
|
</li>
|
|
<li>
|
|
{% 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
|
|
<a href="http://localhost:7657/confignet.jsp">confignet.jsp</a>,
|
|
or by setting <tt>router.maxParticipatingTunnels=nnn</tt> on
|
|
<a href="http://localhost:7657/configadvanced.jsp">configadvanced.jsp</a>.
|
|
{%- endtrans %}
|
|
</li>
|
|
</ul>
|
|
|
|
<h3 id="badcontent">{% trans %}I am opposed to certain types of content. How do I keep from distributing, storing, or accessing them?{% endtrans %}
|
|
<span class="permalink">(<a href="#badcontent">{{ _('link') }}</a>)</span></h3>
|
|
<p>{% trans -%}
|
|
Hmm. I2P is an anonymous network, so that's a tricky one.
|
|
I2P is designed to withstand censorship, providing a means for everyone to communicate freely.
|
|
The best way to keep your PC free of (encrypted) traffic that you dislike is to not use I2P.
|
|
Freedom of speech has some costs.
|
|
But let's address your question in three parts:
|
|
{%- endtrans %}</p>
|
|
<ul>
|
|
<li>
|
|
{% trans -%}
|
|
<b>Distribution</b> - All traffic on I2P is encrypted in multiple layers. You don't know
|
|
a message's contents, source, or destination.
|
|
All traffic you route is internal to the I2P network, you are not an <a href="#exit">exit node</a> (outproxy).
|
|
Your only alternative is to refuse to route
|
|
<i>any</i> traffic, by setting your share bandwidth or maximum participating tunnels to 0 (see above).
|
|
It would be nice if you didn't do this, you should help the network by routing traffic for others.
|
|
Over 95% of users route traffic for others.
|
|
{%- endtrans %}
|
|
</li>
|
|
<li>
|
|
{% trans -%}
|
|
<b>Storage</b> - I2P does not do distributed storage of content. You must be thinking of
|
|
<a href="http://freenetproject.org/">Freenet</a>.
|
|
Nobody's content is being stored on your computer by running I2P.
|
|
{%- endtrans %}
|
|
</li>
|
|
<li>
|
|
{% trans -%}
|
|
<b>Access</b> - If there are some eepsites you don't like, don't go there.
|
|
Or, use a blocking proxy like Privoxy or some type of "net nanny".
|
|
{%- endtrans %}
|
|
</li>
|
|
</ul>
|
|
|
|
|
|
<h3 id="vary">{% trans %}My active peers / known peers / participating tunnels / connections / bandwidth vary dramatically over time! Is anything wrong?{% endtrans %}
|
|
<span class="permalink">(<a href="#vary">{{ _('link') }}</a>)</span></h3>
|
|
<p>{% trans -%}
|
|
No. This is normal.
|
|
All routers adjust dynamically to changing network conditions and demands.
|
|
{%- endtrans %}</p>
|
|
|
|
<h3 id="reseed">{% trans %}My router has been up for several minutes and has zero or very few connections{% endtrans %}
|
|
<span class="permalink">(<a href="#reseed">{{ _('link') }}</a>)</span></h3>
|
|
<p>{% trans -%}
|
|
You may need to reseed your I2P router. With recent versions of I2P you can go to <a href="http://localhost:7657/configreseed">http://localhost:7657/configreseed</a> and click the <em>Save Changes and Reseed Now</em> button. If this method doesn't work—or you're using a very old version—you may need to <a href="#manual_reseed">reseed manually</a>.
|
|
{%- endtrans %}</p>
|
|
<p>{% trans -%}
|
|
The reseed URL changed a few years ago. If this is your first install and you have installed
|
|
an old (0.6.1.30 or earlier) release, or
|
|
you have not run I2P in a long time, you must change the URL and then
|
|
click "Reseed" on the console to find other routers.
|
|
After your router is running,
|
|
on <a href="http://localhost:7657/configadvanced.jsp">configadvanced.jsp</a>,
|
|
add the line <tt>i2p.reseedURL=http://netdb.i2p2.de/</tt>
|
|
OR <tt>i2p.reseedURL=http://i2pdb.tin0.de/netDb/</tt> (either should work),
|
|
then click "Apply", then click the "reseed" link on the left.
|
|
{%- endtrans %}</p>
|
|
<p>{% trans downloadslist=get_url('downloads_list') -%}
|
|
This works if you are running 0.6.1.27 or later.
|
|
If you are running release 0.6.1.31 or later, you probably don't need to do this.
|
|
If you are running release 0.6.1.26 or earlier, either follow the
|
|
<a href="#manual_reseed">manual reseed instructions</a> below
|
|
or install the <a href="{{ downloadslist }}">latest release</a>.
|
|
Possible alternate method - add
|
|
<tt>wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/</tt>
|
|
to wrapper.config, shutdown the router completely, then start again, then click "reseed".
|
|
Let us know if this works.
|
|
{%- endtrans %}</p>
|
|
<p>{% trans downloadslist=get_url('downloads_list') -%}
|
|
...but you *really* should <a href="{{ downloadslist }}">upgrade</a> to the latest version.
|
|
{%- endtrans %}</p>
|
|
|
|
<h3 id="peers">{% trans %}My router has very few active peers, is this OK?{% endtrans %}
|
|
<span class="permalink">(<a href="#peers">{{ _('link') }}</a>)</span></h3>
|
|
<p>{% trans -%}
|
|
If your router has 10 or more active peers, everything is fine. Changes in releases 0.6.1.31 and 0.6.1.32 improved the
|
|
efficiency of the router and effectively reduced the number of active peers.
|
|
The router <i>should</i> maintain connections to a few peers at all times.
|
|
The best way to stay "better-connected" to the network is to <a href="http://localhost:7657/config">share more bandwidth</a>.
|
|
{%- endtrans %}</p>
|
|
|
|
<h3 id="exit">{% trans %}Is my router an "exit node" to the regular Internet? I don't want it to be.{% endtrans %}
|
|
<span class="permalink">(<a href="#exit">{{ _('link') }}</a>)</span></h3>
|
|
<p>{% trans -%}
|
|
No. Unlike <a href="https://www.torproject.org/">Tor</a>,
|
|
"exit nodes" or "outproxies" are not an inherent part of the network.
|
|
Only volunteers who set up and run separate applications will relay traffic to the regular Internet.
|
|
There are very, very few of these.
|
|
{%- endtrans %}</p>
|
|
|
|
<h3 id="outproxy">{% trans %}I can't access regular Internet sites through I2P.{% endtrans %}
|
|
<span class="permalink">(<a href="#outproxy">{{ _('link') }}</a>)</span></h3>
|
|
<p>{% trans -%}
|
|
See above. There are very few HTTP "outproxies", they are not an inherent part of the network,
|
|
and they may not be up.
|
|
In addition, the old outproxies squid.i2p, true.i2p, and krabs.i2p have vanished.
|
|
The only outproxy at the moment is false.i2p.
|
|
To use it, edit your <a href="http://localhost:7657/i2ptunnel/edit.jsp?tunnel=0">i2ptunnel settings for eepProxy</a>
|
|
and set your outproxy list to 'false.i2p' (only).
|
|
Then stop and restart the eepProxy.
|
|
If it doesn't work, the outproxy is not up. It is not I2P's fault.
|
|
If your primary reason to use an anonymous network is to anonymously access sites
|
|
on the regular Internet, you should probably try <a href="https://www.torproject.org/">Tor</a>.
|
|
{%- endtrans %}</p>
|
|
|
|
<h3 id="https">{% trans %}I can't access https:// or ftp:// sites through I2P.{% endtrans %}
|
|
<span class="permalink">(<a href="#https">{{ _('link') }}</a>)</span></h3>
|
|
<p>{% trans -%}
|
|
Within I2P, there is no need for HTTPS, as all traffic is encrypted end-to-end.
|
|
FTP is not supported for technical reasons.
|
|
{%- endtrans %}</p>
|
|
<p>{% trans -%}
|
|
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.
|
|
{%- endtrans %}</p>
|
|
<p>{% trans -%}
|
|
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 %}</p>
|
|
<p>{% trans -%}
|
|
<b>Update</b>: Thanks to the work of h2ik, there is an https outproxy available for use via I2P. Starting with I2P 0.8.4 <a href="http://localhost:7657/i2ptunnel/edit?tunnel=6">the tunnel</a> is configured out of the box.<br />
|
|
In case the https outproxy is not available in your version of I2P, you can add it easily by doing the following:
|
|
{%- endtrans %}</p>
|
|
<ol>
|
|
<li>
|
|
{% trans -%}
|
|
Open <a href="http://localhost:7657/i2ptunnel/index.jsp">i2p tunnel manager</a>. Scroll down to the bottom.
|
|
{%- endtrans %}
|
|
</li>
|
|
<li>
|
|
{% trans -%}
|
|
Choose <b>CONNECT</b> from <b>New Client Tunnel</b> dropdown list, click <b>Create</b>
|
|
{%- endtrans %}
|
|
</li>
|
|
<li>
|
|
{% trans forum=i2pconv('forum.i2p') -%}
|
|
In the new page, <b>name</b> and <b>describe</b> your new https tunnel as you like.
|
|
The <b>Access Point</b> is your local port for the new https proxy recommended port's <b>4445</b>.
|
|
<b>Outproxy</b> should be the outproxy's .i2p address which supports https.
|
|
See this forum post of <a href="http://{{ forum }}/viewtopic.php?p=31356#31356">h2ik</a>'s for the address.
|
|
Make sure <b>Shared Client</b>, <b>Delay Connect</b>, <b>AutoStart</b> are checked.
|
|
Other options should be left at the defaults. Click Save. In tunnel manger, click the <b>Start</b> button next to your new tunnel.
|
|
{%- endtrans %}
|
|
</li>
|
|
<li>
|
|
{% trans -%}
|
|
In firefox, click through <b>Tools</b>><b>Options</b>><b>Advanced</b>><b>Network</b>><b>Setting</b>.
|
|
Untick <b>Use this proxy for all protocol</b>, set <b>SSL proxy:</b> to localhost:4445.
|
|
{%- endtrans %}
|
|
</li>
|
|
<li>{{ _('Done.') }}</li>
|
|
</ol>
|
|
|
|
|
|
<h3 id="proxy_safe">{% trans %}Is using an outproxy safe?{% endtrans %}
|
|
<span class="permalink">(<a href="#proxy_safe">{{ _('link') }}</a>)</span></h3>
|
|
<p>{% trans threatmodel=site_url('docs/how/threat-model') %}
|
|
This is a question that only you can answer because the correct answer depends on your behaviours, your
|
|
<a href="{{ threatmodel }}">threat model</a>, and how much you trust the outproxy operator.
|
|
{%- endtrans %}</p>
|
|
<p>{% trans -%}
|
|
Like Tor, I2P does not magically encrypt the Internet.
|
|
You are vulnerable to snooping by the outproxy operators.
|
|
The <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ExitEavesdroppers">Tor FAQ</a>
|
|
does a good job of explaining this.
|
|
{%- endtrans %}</p>
|
|
<p>{% trans zzz=i2pconv('zzz.i2p') -%}
|
|
In addition, you may be vulnerable to collusion between the outproxy operator
|
|
and operators of other I2P services, if you use the same tunnels ("shared clients").
|
|
There is additional discussion about this on <a href="http://{{ zzz }}/topics/217">{{ zzz }}</a>.
|
|
{%- endtrans %}</p>
|
|
|
|
<h3 id="proxy_other">{% trans %}How do I access IRC, BitTorrent, or other services on the regular Internet?{% endtrans %}
|
|
<span class="permalink">(<a href="#proxy_other">{{ _('link') }}</a>)</span></h3>
|
|
<p>{% trans -%}
|
|
Unless an outproxy has been set up for the service you want to connect to, this cannot be done.
|
|
There are only three types of outproxies running right now: HTTP, HTTPS, and email. Note that there is not a SOCKS outproxy.
|
|
If this type of service is required, try <a href="https://www.torproject.org/">Tor</a>.
|
|
{%- endtrans %}</p>
|
|
|
|
<h3 id="down">{% trans %}Most of the eepsites within I2P are down?{% endtrans %}
|
|
<span class="permalink">(<a href="#down">{{ _('link') }}</a>)</span></h3>
|
|
<p>{% trans eepstatus='http://'+i2pconv('identiguy.i2p') -%}
|
|
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.
|
|
<a href="{{ eepstatus }}">{{ eepstatus }}</a> tracks active eepsites.
|
|
{%- endtrans %}</p>
|
|
|
|
<h3 id="myeepsite">{% trans %}How do I set up my own eepsite?{% endtrans %}
|
|
<span class="permalink">(<a href="#myeepsite">{{ _('link') }}</a>)</span></h3>
|
|
<p>{% trans -%}
|
|
Click on the <a href="http://localhost:7658/">Website</a> link
|
|
at the top of your router console for instructions.
|
|
{%- endtrans %}</p>
|
|
|
|
<h3 id="slow">{% trans %}Why is I2P so slow?{% endtrans %}
|
|
<span class="permalink">(<a href="#slow">{{ _('link') }}</a>)</span></h3>
|
|
<p>{% trans -%}
|
|
Why are downloads, torrents, web browsing, and everything else so slow on I2P?
|
|
The encryption and routing within the I2P network adds a substantial amount of overhead and limits bandwidth.
|
|
Anonymity isn't free.
|
|
{%- endtrans %}</p>
|
|
<p>{% trans -%}
|
|
In addition, you and everybody else probably need to increase your bandwidth limits.
|
|
Two key settings are the inbound and outbound bandwidth limiters on
|
|
<a href="http://localhost:7657/config.jsp">the configuration page</a>.
|
|
With the default settings of 32KBps you will generally get no better than 15KBps data transfer in I2PSnark.
|
|
Increasing the settings (but keeping within your actual connection limitations)
|
|
will increase the potential transfer rate for I2PSnark and all other applications.
|
|
{%- endtrans %}</p>
|
|
<p>{% trans -%}
|
|
Also, do you have sufficient share bandwidth configured to allow participating tunnels
|
|
to route through your router? Believe it or not, allowing participating traffic
|
|
keeps you well-integrated in the network and helps your own 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, <a href="{{ downloadslist }}">install the latest release</a>.
|
|
{%- endtrans %}</p>
|
|
|
|
<h3 id="snark">{% trans %}Bittorrent / I2PSnark / Azureus I2P Plugin Questions?{% endtrans %}
|
|
<span class="permalink">(<a href="#snark">{{ _('link') }}</a>)</span></h3>
|
|
<p>{% trans forum=i2pconv('forum.i2p') -%}
|
|
See the
|
|
<a href="http://{{ forum }}/viewtopic.php?t=2068">I2P Bittorrent FAQ</a>
|
|
{%- endtrans %}</p>
|
|
|
|
<h3 id="irc">{% trans %}How do I connect to IRC within I2P?{% endtrans %}
|
|
<span class="permalink">(<a href="#irc">{{ _('link') }}</a>)</span></h3>
|
|
<p>{% trans %}
|
|
A tunnel to the main IRC server within I2P, Irc2P, is created when I2P is installed (see
|
|
the <a href="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>. XChat-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).
|
|
{%- endtrans %}</p>
|
|
|
|
<h3 id="remote_webconsole">{% trans %}How can I access the web console from my other machines or password protect it?{% endtrans %}
|
|
<span class="permalink">(<a href="#remote_webconsole">{{ _('link') }}</a>)</span></h3>
|
|
<p>{% trans -%}
|
|
For security purposes, the router's admin console by default only listens
|
|
for connections on the local interface. However, with a little hacking,
|
|
you can make it reachable remotely:
|
|
{%- endtrans %}</p>
|
|
|
|
<ol>
|
|
<li>
|
|
{% trans -%}
|
|
Open <code>~/.i2p/clients.config</code> and replace<br />
|
|
<code>clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/</code><br />
|
|
with <br />
|
|
<code>clientApp.0.args=7657 0.0.0.0 ./webapps/</code>
|
|
{%- endtrans %}
|
|
</li>
|
|
<li>
|
|
{% trans -%}
|
|
Go to <a href="http://localhost:7657/configui">http://localhost:7657/configui</a>
|
|
and add a console username and password if desired.
|
|
{%- endtrans %}
|
|
</li>
|
|
<li>
|
|
{% trans -%}
|
|
Go to <a href="http://localhost:7657/index.jsp">http://localhost:7657/index.jsp</a>
|
|
and hit "Graceful restart", which restarts the JVM and reloads the client applications
|
|
{%- endtrans %}
|
|
</li>
|
|
</ol>
|
|
|
|
<p>{% trans -%}
|
|
After that fires up, you should now be able to reach your console remotely. Reload the router at
|
|
http://127.0.0.1:7657 and you will be prompted for the username and password you specified in step 2
|
|
above if your browser supports the authentication popup. Note: the
|
|
<code>0.0.0.0</code> above specifies an <i>interface</i>, 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.
|
|
{%- endtrans %}</p>
|
|
|
|
<h3 id="remote_i2cp">{% trans %}How can I use applications from my other machines?{% endtrans %}
|
|
<span class="permalink">(<a href="#remote_i2cp">{{ _('link') }}</a>)</span></h3>
|
|
<p>{% trans -%}
|
|
By default, the router I2CP interface (port 7654) binds to address 127.0.0.1. To bind to 0.0.0.0, set the
|
|
router advanced configuration option <tt>i2cp.tcp.bindAllInterfaces=true</tt> and restart.
|
|
{%- endtrans %}</p>
|
|
|
|
<h3 id="eepsite">{% trans %}Whats an "eepsite"?{% endtrans %}
|
|
<span class="permalink">(<a href="#eepsite">{{ _('link') }}</a>)</span></h3>
|
|
<p>{% trans -%}
|
|
An eepsite is a website that is hosted anonymously - you can access it by
|
|
setting your web browser's HTTP proxy to use the web proxy (typically it
|
|
listens on localhost port 4444), and browsing to the site.
|
|
{%- endtrans %}</p>
|
|
|
|
<h3 id="browserproxy">{% trans %}How do I configure my browser?{% endtrans %}
|
|
<span class="permalink">(<a href="#browserproxy">{{ _('link') }}</a>)</span></h3>
|
|
<p>{% trans browserconfig=site_url('about/browser-config') -%}
|
|
The proxy config for different browsers is on a <a href="{{ browserconfig }}">
|
|
separate page</a> with screenshots. More advanced configs with external tools
|
|
are possible but could introduce leaks in your setup.
|
|
{%- endtrans %}</p>
|
|
|
|
|
|
<h3 id="active">{% trans %}What do the Active x/y numbers mean in the router console?{% endtrans %}
|
|
<span class="permalink">(<a href="#active">{{ _('link') }}</a>)</span></h3>
|
|
<p>{% trans -%}
|
|
x is the number of peers you've sent or received a message from
|
|
successfully in the last minute, y is the number of peers seen in the last
|
|
hour or so.
|
|
{%- endtrans %}</p>
|
|
|
|
<h3 id="socks">{% trans %}Is it possible to use I2P as a SOCKS proxy?{% endtrans %}
|
|
<span class="permalink">(<a href="#socks">{{ _('link') }}</a>)</span></h3>
|
|
<p>{% trans -%}
|
|
The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are supported.
|
|
There is no SOCKS outproxy so it is of limited use.
|
|
{%- endtrans %}</p>
|
|
<p>{% trans -%}
|
|
In addition, many applications leak sensitive
|
|
information that could identify you on the Internet. 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.
|
|
{%- endtrans %}</p>
|
|
<p>{% trans socks=site_url('docs/api/socks') -%}
|
|
If you would like more information on the socks proxy application anyway,
|
|
there are some helpful hints on the <a href="{{ socks }}">socks page</a>.
|
|
{%- endtrans %}</p>
|
|
|
|
<h3 id="ports">{% trans %}What ports does I2P use?{% endtrans %}
|
|
<span class="permalink">(<a href="#ports">{{ _('link') }}</a>)</span></h3>
|
|
<p>{% trans -%}
|
|
Okay, here's a rundown of the default ports (everything is configurable
|
|
through various settings, of course):
|
|
{%- endtrans %}</p>
|
|
|
|
|
|
<ul>
|
|
|
|
<li>
|
|
{% trans -%}
|
|
<b>Internet-facing ports</b>
|
|
Note: New installs as of release 0.7.8 do not use port 8887; they select a random port
|
|
between 9000 and 31000 when the program is run for the first time.
|
|
The selected port is shown on the router <a href="http://127.0.0.1:7657/confignet.jsp">configuration page.</a>
|
|
{%- endtrans %}
|
|
<ul>
|
|
<li>
|
|
{% trans -%}
|
|
<b>Outbound UDP from the random port noted on the <a href="http://127.0.0.1:7657/confignet.jsp">configuration page</a> to arbitrary remote UDP ports, allowing replies</b>
|
|
{% endtrans %}
|
|
</li>
|
|
<li>
|
|
{% trans -%}
|
|
<b>Outbound TCP from random high ports to arbitrary remote TCP ports</b>
|
|
{% endtrans %}
|
|
</li>
|
|
<li>
|
|
{% trans -%}
|
|
<b>(optional, but recommended) Inbound UDP to the port noted on <a href="http://127.0.0.1:7657/confignet.jsp">configuration page</a> from arbitrary locations</b>
|
|
{% endtrans %}
|
|
</li>
|
|
<li>
|
|
{% trans -%}
|
|
<b>(optional, but recommended) Inbound TCP to the port noted on <a href="http://127.0.0.1:7657/confignet.jsp">configuration page</a> from arbitrary locations</b><br />
|
|
Inbound TCP may be disabled on the <a href="http://127.0.0.1:7657/confignet.jsp">configuration page.</a>
|
|
{%- endtrans %}
|
|
</li>
|
|
<li>
|
|
{% trans -%}
|
|
<b>Outbound UDP on port 123, allowing replies</b><br />
|
|
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>
|
|
</li>
|
|
|
|
<li>
|
|
{% trans -%}
|
|
<b>Local I2P ports</b>, listening only to local connections by default,
|
|
except where noted:
|
|
{%- endtrans %}
|
|
<ul>
|
|
<li>
|
|
{% trans -%}
|
|
<b>1900:</b> UPnP SSDP UDP multicast listener.
|
|
<i>Cannot be changed. Binds to all interfaces.
|
|
May be disabled on <a href="http://localhost:7657/confignet.jsp">confignet.jsp</a>.</i>
|
|
{%- endtrans %}
|
|
</li>
|
|
<li>
|
|
{% trans -%}
|
|
<b>2827:</b> BOB bridge, a higher level socket API for clients
|
|
<i>Disabled by default.
|
|
May be enabled/disabled on <a href="http://localhost:7657/configclients.jsp">configclients.jsp</a>.
|
|
May be changed in the bob.config file.</i>
|
|
{%- endtrans %}
|
|
</li>
|
|
<li>
|
|
{% trans -%}
|
|
<b>4444:</b> HTTP proxy
|
|
<i>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.</i>
|
|
{%- endtrans %}
|
|
</li>
|
|
<li>
|
|
{% trans -%}
|
|
<b>4445:</b> HTTPS proxy
|
|
<i>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.</i>
|
|
{%- endtrans %}
|
|
</li>
|
|
<li>
|
|
{% trans -%}
|
|
<b>6668:</b> IRC proxy
|
|
<i>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.</i>
|
|
{%- endtrans %}
|
|
</li>
|
|
<li>
|
|
{% trans -%}
|
|
<b>7652:</b> UPnP HTTP TCP event listener.
|
|
<i>Binds to the LAN address.
|
|
May be changed with advanced config i2np.upnp.HTTPPort=nnnn.
|
|
May be disabled on <a href="http://localhost:7657/confignet.jsp">confignet.jsp</a>.</i>
|
|
{%- endtrans %}
|
|
</li>
|
|
<li>
|
|
{% trans -%}
|
|
<b>7653:</b> UPnP SSDP UDP search response listener.
|
|
<i>Binds to all interfaces.
|
|
May be changed with advanced config i2np.upnp.SSDPPort=nnnn.
|
|
May be disabled on <a href="http://localhost:7657/confignet.jsp">confignet.jsp</a>.</i>
|
|
{%- endtrans %}
|
|
</li>
|
|
<li>
|
|
{% trans -%}
|
|
<b>7654:</b> I2P Client Protocol port, used by client apps.
|
|
<i>May be changed to a different port on
|
|
<a href="http://localhost:7657/configclients.jsp">configclients.jsp</a>
|
|
but this is not recommended.
|
|
May be to bind to a different interface or all interfaces, or disabled, on
|
|
<a href="http://localhost:7657/configclients.jsp">configclients.jsp</a>.</i>
|
|
{%- endtrans %}
|
|
</li>
|
|
<li>
|
|
{% trans -%}
|
|
<b>7655:</b> UDP for SAM bridge, a higher level socket API for clients
|
|
<i>Only opened when a SAM V3 client requests a UDP session.
|
|
May be enabled/disabled on <a href="http://localhost:7657/configclients.jsp">configclients.jsp</a>.
|
|
May be changed in the clients.config file with the SAM command line option sam.udp.port=nnnn.</i>
|
|
{%- endtrans %}
|
|
</li>
|
|
<li>
|
|
{% trans -%}
|
|
<b>7656:</b> SAM bridge, a higher level socket API for clients
|
|
<i>Disabled by default for new installs as of release 0.6.5.
|
|
May be enabled/disabled on <a href="http://localhost:7657/configclients.jsp">configclients.jsp</a>.
|
|
May be changed in the clients.config file.</i>
|
|
{%- endtrans %}
|
|
</li>
|
|
<li>
|
|
{% trans -%}
|
|
<b>7657:</b> Your router console
|
|
<i>May be disabled in the clients.config file.
|
|
May also be configured to be bound to a specific interface or all interfaces in that file.</i>
|
|
{%- endtrans %}
|
|
</li>
|
|
<li>
|
|
{% trans -%}
|
|
<b>7658:</b> Your eepsite
|
|
<i>May be disabled in the clients.config file.
|
|
May also be configured to be bound to a specific interface or all interfaces in the jetty.xml file.</i>
|
|
{%- endtrans %}
|
|
</li>
|
|
<li>
|
|
{% trans -%}
|
|
<b>7659:</b> Outgoing mail to smtp.postman.i2p
|
|
<i>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.</i>
|
|
{%- endtrans %}
|
|
</li>
|
|
<li>
|
|
{% trans -%}
|
|
<b>7660:</b> Incoming mail from pop.postman.i2p
|
|
<i>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.</i>
|
|
{%- endtrans %}
|
|
</li>
|
|
<li>
|
|
{% trans -%}
|
|
<b>8998:</b> mtn.i2p2.i2p (Monotone - disabled by default)
|
|
<i>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.</i>
|
|
{%- endtrans %}
|
|
</li>
|
|
<li>
|
|
{% trans -%}
|
|
<b>31000:</b> Local connection to the wrapper control channel port.
|
|
<i>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
|
|
<a href="http://wrapper.tanukisoftware.com/doc/english/prop-port.html">wrapper documentation</a>.
|
|
For more information see <a href="#port32000">below</a>.</i>
|
|
{%- endtrans %}
|
|
</li>
|
|
<li>
|
|
{% trans -%}
|
|
<b>32000:</b> Local control channel for the service wrapper.
|
|
<i>To change, see the
|
|
<a href="http://wrapper.tanukisoftware.com/doc/english/prop-port.html">wrapper documentation</a>.
|
|
For more information see <a href="#port32000">below</a>.</i>
|
|
{%- endtrans %}
|
|
</li>
|
|
</ul>
|
|
</li>
|
|
</ul>
|
|
|
|
|
|
<p>{% trans -%}
|
|
The local I2P ports and the I2PTunnel ports do not need to be reachable from
|
|
remote machines, but *should* be reachable locally. You can also create
|
|
additional ports for I2PTunnel instances via http://localhost:7657/i2ptunnel/
|
|
(and in turn, would need to get your firewall to allow you local access, but
|
|
not remote access, unless desired).
|
|
{%- endtrans %}</p>
|
|
|
|
<p>{% trans -%}
|
|
So, to summarize, nothing needs to be reachable by unsolicited remote peers, but
|
|
if you can configure your NAT/firewall to allow inbound UDP and TCP the <a href="http://localhost:7657/config">outbound facing port</a>, you'll
|
|
get better performance. You will also need to be able to send outbound UDP packets
|
|
to arbitrary remote peers (blocking IPs randomly with something like PeerGuardian
|
|
only hurts you - don't do it).
|
|
{%- endtrans %}</p>
|
|
|
|
<h3 id="port32000">{% trans %}Why is I2P listening on port 32000?{% endtrans %}
|
|
<span class="permalink">(<a href="#port32000">{{ _('link') }}</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
|
|
<a href="http://wrapper.tanukisoftware.com/doc/english/prop-port.html">wrapper documentation</a>.
|
|
{%- endtrans %}</p>
|
|
|
|
<h3 id="manual_reseed">{% trans %}How do I reseed manually?{% endtrans %}
|
|
<span class="permalink">(<a href="#manual_reseed">{{ _('link') }}</a>)</span></h3>
|
|
<p>{% trans -%}
|
|
An I2P router only needs to be seeded once, to join the network for the first
|
|
time. Reseeding involves fetching multiple "RouterInfo" files (bundled into a
|
|
signed zip-file) from at least two predefined server URLs picked from a
|
|
volunteer-run group of clearnet HTTPS servers.
|
|
{%- endtrans %}</p>
|
|
|
|
<p>{% trans -%}
|
|
A typical symptom of a failed reseed is the "Known" indicator (on the left
|
|
sidebar of the router console) displaying a very small value (often less than
|
|
5) which does not increase. This can occur, among other things, if your local
|
|
firewall limits outbound traffic or if the reseed request is blocked entirely.
|
|
{%- endtrans %}</p>
|
|
|
|
<p>{% trans -%}
|
|
If you are stuck behind an ISP firewall or filter, you can use the following
|
|
manual method (non-automated technical solution) to join the I2P network.
|
|
{%- endtrans %}</p>
|
|
|
|
<h4>{% trans %}Joining the I2P Network using a reseed file{% endtrans %}</h4>
|
|
<p>{% trans -%}
|
|
Please contact a known trustworthy friend who has a running I2P router, and ask
|
|
them for help with reseeding your I2P router. Request that they send you a
|
|
reseed file exported from their running I2P router. It is vital that the file is
|
|
exchanged over a secure channel, e.g. encrypted to avoid external tampering (PGP
|
|
Sign, Encrypt and Verified with a trusted public key). The file itself is
|
|
unsigned, so please accept files only from known trusted friends. Never import
|
|
a reseed file if you can not verify its source.
|
|
{%- endtrans %}</p>
|
|
|
|
<p>{% trans filename='i2preseed.zip' %}To import the received {{ filename }} file into your local I2P router:{% endtrans %}</p>
|
|
<ul>
|
|
<li>{% trans url='http://localhost:7657/configreseed' %}Go to <a href="{{ url }}">{{ url }}</a>{% endtrans %}</li>
|
|
<li>{% trans %}Under "Manual Reseed from File" click "Browse..."{% endtrans %}</li>
|
|
<li>{% trans filename='i2preseed.zip' %}Select the {{ filename }} file{% endtrans %}</li>
|
|
<li>{% trans %}Click "Reseed from File"{% endtrans %}</li>
|
|
</ul>
|
|
<p>{% trans url='http://localhost:7657/logs' %}Check the <a href="{{ url }}">log</a> for the following message:{% endtrans %}
|
|
<code>Reseed got 100 router infos from file with 0 errors</code>
|
|
</p>
|
|
|
|
<h4>{% trans %}Sharing a reseed file{% endtrans %}</h4>
|
|
<p>{% trans %}For trusted friends you can use your local I2P router to give them a jump start:{% endtrans %}</p>
|
|
<ul>
|
|
<li>{% trans url='http://localhost:7657/configreseed' %}Go to <a href="{{ url }}">{{ url }}</a>{% endtrans %}</li>
|
|
<li>{% trans %}Under "Create Reseed File" click "Create reseed file"{% endtrans %}</li>
|
|
<li>{% trans filename='i2preseed.zip' %}Securely send the {{ filename }} file to your friend{% endtrans %}</li>
|
|
</ul>
|
|
<p>{% trans -%}
|
|
Do not reveal this file in any case to unknown users, since it contains
|
|
sensitive private data (100 RouterInfo) from your own I2P router! In order to
|
|
protect your anonymity: you may wait a few random hours/days before you share
|
|
the file with your trusted friend. It is also advisable to use this procedure
|
|
sparingly (< 2 per week).
|
|
{%- endtrans %}</p>
|
|
|
|
<h4>{% trans %} General guidelines for manual reseeding of I2P {% endtrans %}</h4>
|
|
<ul>
|
|
<li>{% trans %}Do not publicly publish the reseed file or share these files with a friend of a friend!{% endtrans %}</li>
|
|
<li>{% trans %}This file should be used only for a very limited number of friends (< 3)!{% endtrans %}</li>
|
|
<li>{% trans %}The file is valid only a few days (< 20)!{% endtrans %}</li>
|
|
</ul>
|
|
|
|
<h3 id="compat6x">{% trans %}I'm using FreeBSD and when I start I2P I receive an error about <code>libm.so.4</code>!{% endtrans %}
|
|
<span class="permalink">(<a href="#compat6x">{{ _('link') }}</a>)</span></h3>
|
|
|
|
{% trans %}When trying to start the router using "i2prouter start", you may see output like the following:{% endtrans %}<br />
|
|
<code> $ ./i2prouter start<br />
|
|
Starting I2P Service...<br />
|
|
/libexec/ld-elf.so.1: Shared object "libm.so.4" not found, required by "i2psvc"
|
|
</code>
|
|
<p>{% trans %}
|
|
In order to be inclusive and try to ensure that I2P will run on as many systems
|
|
as possible, up until I2P 0.8.9 we used a <a href="http://wrapper.tanukisoftware.com/">java wrapper</a>
|
|
compiled for FreeBSD 6.x. If you're receiving this error you most likely are missing the necessary compatibility libraries.
|
|
These libraries may be installed by performing the following steps:
|
|
{%- endtrans %}</p>
|
|
<ul>
|
|
<li>
|
|
{% trans %}Switch to the root user with <code>su</code> or log in as <code>root</code>.{% endtrans %}
|
|
</li>
|
|
<li><code>cd /usr/ports/misc/compat6x</code></li>
|
|
<li><code>make install</code></li>
|
|
</ul>
|
|
|
|
<p>{% trans manualwrapper=site_url('misc/manual-wrapper') -%}
|
|
If you cannot install these compatibility libraries (or do not want to), other
|
|
possibilities would be to compile the wrapper for <a href="{{ manualwrapper }}">your
|
|
system</a>, starting I2P with the <code>runplain.sh</code> script, or you can
|
|
replace the wrapper with one from the source tarball.
|
|
{%- endtrans %}</p>
|
|
<p>{% trans -%}
|
|
For the 0.8.9 release of I2P, the wrapper was upgraded to v3.5.12 and compiled on systems running FreeBSD 7.2.
|
|
{%- endtrans %}</p>
|
|
|
|
<h3 id="protocolfamily">{% trans %}In <code>wrapper.log</code> I see an error that states "<code>Protocol family unavailable</code>" when loading the Router Console{% endtrans %}
|
|
<span class="permalink">(<a href="#protocolfamily">{{ _('link') }}</a>)</span></h3>
|
|
<p>{% trans -%}
|
|
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:
|
|
{%- endtrans %}</p>
|
|
<ul>
|
|
<li>
|
|
{% trans %}On Linux based systems, you can <code>echo 0 > /proc/sys/net/ipv6/bindv6only</code>{% endtrans %}
|
|
</li>
|
|
<li>{% trans %}Look for the following lines in <code>wrapper.config</code>.{% endtrans %}<br />
|
|
<code>#wrapper.java.additional.5=-Djava.net.preferIPv4Stack=true<br />
|
|
#wrapper.java.additional.6=-Djava.net.preferIPv6Addresses=false<br />
|
|
</code><br />
|
|
{% trans %}If the lines are there, uncomment them by removing the "#"s. If the lines are not there, add them without the "#"s.{% endtrans %}
|
|
</li>
|
|
</ul>
|
|
{% trans -%}
|
|
Another option would be to remove the <strong>::1</strong> from <code>~/.i2p/clients.config</code>
|
|
{%- endtrans %}
|
|
|
|
<p>{% trans -%}
|
|
<strong>WARNING</strong>: For any changes to <code>wrapper.config</code> to take effect, you must completely
|
|
stop the router and the wrapper. Clicking <em>Restart</em> on your
|
|
router console will NOT reread this file! You must
|
|
click <em>Shutdown</em>, wait 11 minutes, then start I2P.
|
|
{%- endtrans %}</p>
|
|
|
|
<h3 id="java">{% trans %}Is installing Java required to use I2P?{% endtrans %}
|
|
<span class="permalink">(<a href="#java">{{ _('link') }}</a>)</span></h3>
|
|
<p>{% trans alt=site_url('about/alternative-clients') -%}
|
|
While the main I2P client implementation requires Java, there are several
|
|
<a href="{{ alt }}">alternative clients</a> which don't require Java.
|
|
{%- endtrans %}</p>
|
|
|
|
<hr />
|
|
|
|
<h3 id="question">{% trans %}I have a question!{% endtrans %}
|
|
<span class="permalink">(<a href="#question">{{ _('link') }}</a>)</span></h3>
|
|
<p>{% trans forum=i2pconv('forum.i2p') -%}
|
|
Great! Find us on IRC irc.freenode.net #i2p or post to
|
|
the <a href="http://{{ forum }}/">forum</a> and we'll post it here (with
|
|
the answer, hopefully).
|
|
{%- endtrans %}</p>
|
|
|
|
{% endblock %}
|