i2p.www/i2p2www/pages/site/misc/i2ptunnel-migration.html

{% extends "global/layout.html" %}
{% block title %}{% trans %}I2PTunnel migration{% endtrans %}{% endblock %}
{% block content %}
<h3>{% trans %}I2PTunnel migration{% endtrans %}</h3>

<p>{% trans -%}
After upgrading to the new architecture, you'll have to do a 
little work to get your old I2PTunnel-driven servers running.  
Lets walk through a simple example.  For an I2P Site with the 
old clientApp configuration, you had:
{%- endtrans %}</p>
<pre>
  -e "server localhost 80 myWebPriv.dat"
</pre>

<p>{% trans -%}To provide that same functionality on the new web architecture:{%- endtrans %}</p>
<ul>
<li>{% trans url='http://localhost:7657/i2ptunnel/' %}Jump to <a href="{{ url }}">{{ url }}</a>{% endtrans %}</li>
<li>{% trans %}Click on Add new: [Server tunnel] "GO"{% endtrans %}</li>
<li><ul>
 <li>{% trans %}For the name: <code>"I2P Site"</code>{% endtrans %}</li>
 <li>{% trans %}For the description: <code>"My I2P Site, isn't it pretty?"</code>{% endtrans %}</li>
 <li{% trans %}>For the target host:{% endtrans %} <code>localhost</code></li>
 <li>{% trans %}For the target port:{% endtrans %} <code>80</code></li>
 <li>{% trans -%}
For the private key file: <code>path to "myWebPriv.dat"</code><br /> 
(it is recommended to copy that .dat to your new install dir)
{%- endtrans %}</li>
 <li>{% trans %}Check the "Start automatically?" checkbox{% endtrans %} <code>[X]</code></li>
 <li>{% trans %}Click <code>"Save"</code>{% endtrans %}</li>
</ul></li>
<li>{% trans %}It will come back saying:{% endtrans %}<br />
<pre>
  * Not overwriting existing private keys in /usr/home/jrandom/routers/i2p/myWebPriv.dat
  * Ready!
</pre></li>
</ul>

<p>{% trans -%}
That's it!  Creating a new I2PTunnel server works the same way too, except you
don't need to "copy the old file", obviously.  Behind the scenes, it is all driven
by the <code>i2ptunnel.config</code> file, which you may modify externally (if you do,
hit "Reload config" on the I2PTunnel web page, which will tear down all of your 
existing tunnels and rebuild new ones)
{%- endtrans %}</p>

<p>{% trans -%}
Note that you WILL need to wait until your router is integrated
into the network before you are able to use the /i2ptunnel/ web
interface.  It will say "Please be patient" if you try to 
beforehand, which means that it is still trying to build the 
necessary I2PTunnel sessions it has been configured to create.
{%- endtrans %}</p>
{% endblock %}