69 lines
2.6 KiB
HTML
69 lines
2.6 KiB
HTML
{% extends "global/layout.html" %}
|
|
{% block title %}{% trans %}Reseed Hosts{% endtrans %}{% endblock %}
|
|
{% block lastupdated %}{% trans %}September 2021{% endtrans %}{% endblock %}
|
|
{% block accuratefor %}1.5.0{% endblock %}
|
|
{% block content %}
|
|
|
|
|
|
<h2 id="about">{% trans %}About Reseed Hosts{% endtrans %}</h2>
|
|
|
|
<p>{% trans -%}
|
|
Reseed hosts are needed for new routers to integrate with the I2P network.
|
|
During the bootstrapping process, reseed hosts provide an initial set of nodes for
|
|
a new router to make connections with. Occasionally an already integrated router
|
|
may need to go through the reseed process if it is experiencing connection issues with the network.
|
|
This is most often caused by its known nodes not being available.
|
|
{%- endtrans %}</p>
|
|
|
|
<p>{% trans -%}
|
|
Reseeding is done over an encrypted connection and all of the bootstrap
|
|
information is signed by the reseed host you connect to. This makes it impossible
|
|
for an unauthenticated source to provide false information.
|
|
{%- endtrans %}</p>
|
|
|
|
|
|
<h2 id="running">{% trans %}Running a Reseed host{% endtrans %}</h2>
|
|
<p>
|
|
{% trans -%}Operating a reseed server will be familair for most sysadmins who have experience with
|
|
I2P. More reseed hosts result in more resilient I2P network connections for new
|
|
participating routers. It also makes it harder to prevent new routers from connecting to the I2P network.
|
|
{%- endtrans %}
|
|
</p>
|
|
|
|
<ul>
|
|
<li><a href="{{ site_url('get-involved/guides/reseed') }}">Reseed Contributors Guide</a></li>
|
|
<li><a href="https://i2pgit.org/idk/reseed-tools">Reseed Software and Documentation</a></li>
|
|
</ul>
|
|
|
|
<h2 id="other">{% trans %}Other Ways Of Reseeding{% endtrans %}</h2>
|
|
|
|
<p>
|
|
{% trans -%}
|
|
Other options for reseeding include file-based reseeds, where a user
|
|
with a running I2P router generates a reseed file for a friend and transfers it
|
|
to them as a .zip file. Using cloud-based infrastructure helps to resist
|
|
censorship, which aids people in situations where reseeds may be restricted.
|
|
{%- endtrans %}
|
|
</p>
|
|
|
|
<ul>
|
|
<li><a href="{{ site_url('blog/post/2020/06/07/file-based-reseed') }}">File Based Reseed</a></li>
|
|
<li><a href="https://homepage.np-tokumei.net/post/notes-i2p-reseed-over-cloudflare/">I2P Reseed Over Cloudflare</a></li>
|
|
<li><a href="https://homepage.np-tokumei.net/post/notes-censorship-resistant-i2p-reseeding/">Censorship Resistant I2P Reseeding</a></li>
|
|
</ul>
|
|
|
|
<h2 id="thank you">{% trans %}Thank You Reseed Operators{% endtrans %}</h2>
|
|
<p>
|
|
{%-trans -%}
|
|
If you are running a reseed server, thank you for helping to
|
|
make the I2P network stronger and more resilient than ever.
|
|
{%- endtrans-%}
|
|
</p>
|
|
<p>
|
|
{%-trans -%}
|
|
Thank you.
|
|
{%- endtrans-%}
|
|
</p>
|
|
|
|
{% endblock %}
|