merge of '503d04d73b3794f59dcbd3977cee5b3abf4dad7c'

and 'b7e8308463e8c16a56b37bfbbd1e2b96f147dc07'
This commit is contained in:
hankhill19580
2020-06-07 17:20:29 +00:00
6 changed files with 64 additions and 2 deletions

View File

@@ -0,0 +1,61 @@
================================================================
{% trans -%}Help your Friends Join I2P by Sharing Reseed Bundles{%- endtrans %}
================================================================
.. meta::
:author: idk
:date: 2020-06-07
:category: reseed
:excerpt: {% trans %}Create, exchange, and use reseed bundles{% endtrans %}
{% trans -%}
Most new I2P routers join the network by bootstrapping with the help of
a reseed service. However, reseed services are centralized and
comparatively easy to block, considering the emphasis on de-centralized
and un-blockable connections in the rest of the I2P network. If a new
I2P router finds itself unable to bootstrap, it may be a possible to use
an existing I2P router to generate a working “Reseed bundle” and
bootstrap without the need of a reseed service.
{%- endtrans %}
{% trans -%}
It is possible for a user with a working I2P connection to help a
blocked router join the network by generating a reseed file and passing
it to them via a secret or non-blocked channel. In fact, in many
circumstances, an I2P router that is already connected will not be
affected by reseed blocking at all, so **having working I2P routers
around means that existing I2P routers can help new I2P routers by
providing them with a hidden way of bootstrapping**.
{%- endtrans %}
{% trans -%}Generating a Reseed Bundle{%- endtrans %}
--------------------------------------
- {% trans -%} To create a reseed bundle for others to use, go to the `Reseed
configuration page <http://127.0.0.1:7657/configreseed>`__. You will
see a section that looks like this. Click the button indicated by the
red circle. |Create a Reseed Zip| {%- endtrans %}
- {% trans -%} Now that youve clicked the button, a zip will be generated
containing enough information to bootstrap a new I2P router. Download
it and transfer it to the computer with the new, un-bootstrapped I2P
router. |Downloads a Reseed Zip| {%- endtrans %}
{% trans -%}Performing a Reseed from File{%- endtrans %}
------------------------------------------
- {% trans -%} Obtain an i2preseed.zip file from a friend with an I2P router that is
already running, or from a trusted source somewhere on the internet,
and visit the `Reseed Configuration
page <http://127.0.0.1:7657/configreseed>`__. Click the button that
says “Select zip or su3 file” and navigate to that file. |Select a
Reseed Zip| {%- endtrans %}
- {% trans -%} When youve selected your reseed file, click the “Reseed from File”
button. |Reseed from a Zip File|. Youre done! Your router will now
bootstrap using the zip file, and you will be ready to join the I2P
network. {%- endtrans %}
.. |Create a Reseed Zip| image:: /_static/images/reseed/createreseed.png
.. |Downloads a Reseed Zip| image:: /_static/images/reseed/dlreseed.png
.. |Select a Reseed Zip| image:: /_static/images/reseed/ulreseed.png
.. |Reseed from a Zip File| image:: /_static/images/reseed/filereseed.png

Binary file not shown.

After

Width:  |  Height:  |  Size: 58 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 27 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 59 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 34 KiB

View File

@@ -1,6 +1,6 @@
{% extends "global/layout.html" %} {% extends "global/layout.html" %}
{% block title %}I2CP{% endblock %} {% block title %}I2CP{% endblock %}
{% block lastupdated %}2020-05{% endblock %} {% block lastupdated %}2020-06{% endblock %}
{% block accuratefor %}0.9.46{% endblock %} {% block accuratefor %}0.9.46{% endblock %}
{% block content %} {% block content %}
<p>{% trans -%} <p>{% trans -%}
@@ -749,8 +749,9 @@ I2CP will generate the public key from the private key.
Use for persistent leaseset keys across restarts. Use for persistent leaseset keys across restarts.
See proposals 123, 144, and 145. See proposals 123, 144, and 145.
See also i2cp.leaseSetEncType. See also i2cp.leaseSetEncType.
{%- endtrans %}</td> {%- endtrans %}
Do not confuse with i2cp.leaseSetPrivKey which is for encrypted LS2. Do not confuse with i2cp.leaseSetPrivKey which is for encrypted LS2.
</td>
</tr> </tr>
<tr> <tr>