153 lines
4.9 KiB
HTML
153 lines
4.9 KiB
HTML
{% extends "global/layout.html" %}
|
|
{% block title %}{{ _('How to Set up a Reseed Server') }}{% endblock %}
|
|
{% block lastupdated %}2023-01{% endblock %}
|
|
{% block content %}
|
|
|
|
<h2>{% trans %}General Information{% endtrans %}</h2>
|
|
|
|
<p>{% trans -%}
|
|
Thank you for volunteering to run an I2P reseed server.
|
|
"Reseeding" is our term for bootstrapping new routers into the network.
|
|
New routers fetch a bundle of peer references, or "router infos", from one or more of a hardcoded list of HTTPS URLs.
|
|
{%- endtrans %}</p>
|
|
|
|
<h2>{% trans %}Requirements{% endtrans %}</h2>
|
|
|
|
<p>{% trans -%}
|
|
A reseed server must be reachable on the public internet.
|
|
It must use TLS, but it may use a self-signed TLS certificate if the reseed administrator is in communication with the router development team.
|
|
The administrator of the reseed server should provide contact information in order to respond to issues and be in touch with the I2P team.
|
|
{%- endtrans %}</p>
|
|
|
|
<h2>{% trans %}More Information{% endtrans %}</h2>
|
|
|
|
<h4><a href="reseed-policy">{% trans -%}To read the reseed policy, follow this link.{% endtrans -%}</a></h4>
|
|
<h4><a href="reseed-debian">{% trans -%}Are you a Debian user? You can find Debian-Specific instructions here.{% endtrans -%}</a></h4>
|
|
<h4><a href="reseed-docker">{% trans -%}Are you a Docker user? You can find Docker-Specific instructions here.{% endtrans -%}</a></h4>
|
|
<!--
|
|
<h4><a href="reseed-plugin">{% trans -%}Would you like to use an I2P Plugin? I2P Plugin instructions are available here.{% endtrans -%}</a></h4>
|
|
<h4><a href="reseed-proxy">{% trans -%}Click here for instructions on using a reverse proxy such as nginx or Apache2.{% endtrans -%}</a></h4>
|
|
-->
|
|
<h4><a href="reseed-old">{% trans -%}To read the old instructions, follow this link.{% endtrans -%}</a></h4>
|
|
|
|
<h2>{% trans %}Installation from Source Code{% endtrans %}</h2>
|
|
|
|
<p>{% trans %}
|
|
These guidelines are based on idk's <a href="https://i2pgit.org/idk/reseed-tools">reseed-tools</a> server.
|
|
They should be very similar to the guidelines for DivaExchange's <a href="https://codeberg.org/diva.exchange/i2p-reseed">i2p-reseed</a> server.
|
|
{% endtrans %}</p>
|
|
|
|
<p>{% trans %}
|
|
Reseed Tools is a pure Go application which can be built statically without CGO.
|
|
It makes use of Go Modules.
|
|
A Makefile is provided with some targets which are convenient helpers for generating binaries, especially for production and release purposes.
|
|
{% endtrans %}</p>
|
|
<p>
|
|
|
|
<strong>
|
|
1.
|
|
</strong>
|
|
{% trans %}Install the build dependencies{% endtrans %}
|
|
</p>
|
|
<pre><code class="language-sh">
|
|
sudo apt-get install go git make
|
|
</code></pre>
|
|
<p>
|
|
|
|
<strong>
|
|
2.
|
|
</strong>
|
|
{% trans %}Clone the source code{% endtrans %}
|
|
</p>
|
|
<pre><code class="language-sh">
|
|
git clone https://i2pgit.org/idk/reseed-tools ~/go/src/i2pgit.org/idk/reseed-tools
|
|
</code></pre>
|
|
<p>
|
|
|
|
<strong>
|
|
3.
|
|
</strong>
|
|
{% trans %}Generate the binaries using the{% endtrans %}
|
|
<code>
|
|
make build
|
|
</code>
|
|
{% trans %}command{% endtrans %}
|
|
</p>
|
|
<pre><code class="language-sh">
|
|
cd ~/go/src/i2pgit.org/idk/reseed-tools
|
|
make build
|
|
</code></pre>
|
|
<p>
|
|
|
|
<strong>
|
|
4.
|
|
</strong>
|
|
{% trans %}Install the binary and the config files{% endtrans %}
|
|
</p>
|
|
<pre><code class="language-sh">
|
|
sudo make install
|
|
</code></pre>
|
|
<h2>{% trans %}
|
|
Running the Service
|
|
{% endtrans %}</h2>
|
|
<p>
|
|
|
|
<strong>
|
|
1.
|
|
</strong>
|
|
{% trans %}First, ensure that the I2P service is already running. The longer the better, if you have to re-start the service, or if the service has very few peers, allow it to run for 24 hours before advancing to step{% endtrans %}
|
|
<strong>
|
|
2.
|
|
</strong>
|
|
</p>
|
|
<pre><code class="language-sh">
|
|
sudo systemctl start i2p
|
|
# or, if you use sysvinit
|
|
sudo service i2p start
|
|
</code></pre>
|
|
<p>
|
|
|
|
<strong>
|
|
2.
|
|
</strong>
|
|
{% trans %}Once your I2P router is Well-Integrated, start the reseed service.{% endtrans %}
|
|
</p>
|
|
<pre><code class="language-sh">
|
|
sudo systemctl start reseed
|
|
# or, if you use sysvinit
|
|
sudo service reseed start
|
|
</code></pre>
|
|
<p>
|
|
{% trans %}Your reseed will auto-configure with a self-signed certificate on port{% endtrans %}
|
|
<code>
|
|
:8443
|
|
</code>
|
|
. {% trans %}The certificates themselves are available in{% endtrans %}
|
|
<code>
|
|
/var/lib/i2p/i2p-config/reseed
|
|
</code>
|
|
. {% trans %}When you are ready, you should copy the{% endtrans %}
|
|
<code>
|
|
*.crt
|
|
</code>
|
|
{% trans %}files from that directory and share them with the I2P community on{% endtrans %}
|
|
<a href="http://zzz.i2p">
|
|
<code>
|
|
zzz.i2p
|
|
</code>
|
|
</a>
|
|
. {% trans %}These will allow I2P users to authenticate your reseed services and secure the I2P network.{% endtrans %}
|
|
</p>
|
|
<p>
|
|
{% trans %}Contact us via email zzz at mail.i2p (alternatively, post in the reseed section on the zzz.i2p forum)
|
|
Provide us with details about your new reseed server:{% endtrans %}
|
|
<ul>
|
|
<li>{% trans %}Reseed website URL{% endtrans %}</li>
|
|
<li>{% trans %}Public SSL certificate{% endtrans %}</li>
|
|
<li>{% trans %}Public reseed su3 certificate{% endtrans %}</li>
|
|
<li>{% trans %}Your contact email{% endtrans %}</li>
|
|
<li>{% trans %}A statement that you agree to the privacy policy above{% endtrans %}</li>
|
|
</ul>
|
|
<p>
|
|
{% endblock %}
|