I2P_Developers/i2p.www
3
0
Fork 5
Code Issues 27 Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Update the FAQ entry for manual reseeding

Browse Source 
Based on a patch from manas. See http://zzz.i2p/topics/2129?page=1#p12680
This commit is contained in:
str4d
2017-07-28 17:20:48 +00:00
parent 8b69d62afd
commit d8be50b192
1 changed files with 54 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

79
i2p2www/pages/site/faq.html
View File

@ -751,37 +751,66 @@ More information can be found in the
<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 is nothing more than sending plain HTTP GET requests
to fetch a directory listing and download multiple "routerInfo" files
from a predefined reseed URL.
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 firewall limits outbound traffic, and blocked the reseed request.
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>
{% trans %}To reseed an I2P router manually, do the following:{% endtrans %}
<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 %}Stop your I2P router{% endtrans %}
</li>
<li>
{% trans %}Open <a href="http://netdb.i2p2.de/">http://netdb.i2p2.de/</a> using a web browser{% endtrans %}
<!-- DOWN <a href="http://i2pdb.tin0.de/netDb/">http://i2pdb.tin0.de/netDb/</a> or -->
</li>
<li>{% trans %}Save a dozen "routerInfo" files to your I2P "netDb" directory{% endtrans %}
<!-- DOWN
</li><li>Alternate method (easier): Download <a href="http://i2pdb.tin0.de/latest.zip">http://i2pdb.tin0.de/latest.zip</a>
and unzip it into your I2P "netDb" directory.
-->
</li>
<li>
{% trans %}Start your I2P router{% endtrans %}
</li>
<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 %}