lbt/I2P_Website
1
0
Fork 0
forked from I2P_Developers/i2p.www
Code Issues Pull Requests Packages Projects Releases Wiki Activity

final touches for blog posts

Browse Source
This commit is contained in:
hankhill19580
2019-06-03 01:30:24 +00:00
parent dafe1f2ef4
commit a0abacb9cb
1 changed files with 47 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files

74
i2p2www/blog/2019/06/02/basic-tunnel-tutorial.rst
View File

@@ -3,16 +3,19 @@
:date: 2019-06-02 :date: 2019-06-02
:excerpt: {% trans %}Basic i2ptunnel Setup{% endtrans %} :excerpt: {% trans %}Basic i2ptunnel Setup{% endtrans %}
======================================== ===================================================================
Basic i2p Tunnels Tutorial with Pictures {% trans -%}Basic i2p Tunnels Tutorial with Pictures{%- endtrans %}
======================================== ===================================================================
{% trans -%}
Although the Java i2p router comes pre-configured with a static web server, Although the Java i2p router comes pre-configured with a static web server,
jetty, to provide the user's first eepSite, many require more sophisticated jetty, to provide the user's first eepSite, many require more sophisticated
functionality from their web server and would rather create an eepSite with a functionality from their web server and would rather create an eepSite with a
different server. This is of course possible, and actually is really easy once different server. This is of course possible, and actually is really easy once
you've done it one time. you've done it one time.
{%- endtrans %}
{% trans -%}
Although it is easy to do, there are a few things you should consider before Although it is easy to do, there are a few things you should consider before
doing it. You will want to remove identifying characteristics from your web doing it. You will want to remove identifying characteristics from your web
server, like potentially identifying headers and default error pages that server, like potentially identifying headers and default error pages that
@@ -24,83 +27,100 @@ posed by improperly configured applications see:
`and the i2p applications page here <https://geti2p.net/en/docs/applications/supported>`__. `and the i2p applications page here <https://geti2p.net/en/docs/applications/supported>`__.
Although much of this information is expressed for Tor Onion Services, the same Although much of this information is expressed for Tor Onion Services, the same
procedures and principles apply to hosting applications over i2p. procedures and principles apply to hosting applications over i2p.
{%- endtrans %}
Step One: Open the Tunnel Wizard {% trans -%}Step One: Open the Tunnel Wizard{%- endtrans %}
-------------------------------- -----------------------------------------------------------
{% trans -%}
Go to the i2p web interface at 127.0.0.1:7657 and open the Go to the i2p web interface at 127.0.0.1:7657 and open the
`Hidden Services Manager <http://127.0.0.1:7657/i2ptunnelmgr>`__\ (links to `Hidden Services Manager <http://127.0.0.1:7657/i2ptunnelmgr>`__\ (links to
localhost). Click the button that says "Tunnel Wizard" to begin. localhost). Click the button that says "Tunnel Wizard" to begin.
{%- endtrans %}
|Step One: Open the Tunnel Wizard| |Step One: Open the Tunnel Wizard|
Step Two: Select a Server Tunnel {% trans -%}Step Two: Select a Server Tunnel{%- endtrans %}
-------------------------------- -----------------------------------------------------------
{% trans -%}
The tunnel wizard is very simple. Since we're setting up an http *server*, all The tunnel wizard is very simple. Since we're setting up an http *server*, all
we need to do is select a *server* tunnel. we need to do is select a *server* tunnel.
{%- endtrans %}
|Step Two: Select a Server Tunnel| |Step Two: Select a Server Tunnel|
Step Three: Select an HTTP Tunnel {% trans -%}Step Three: Select an HTTP Tunnel{%- endtrans %}
--------------------------------- ------------------------------------------------------------
{% trans -%}
An HTTP tunnel is the tunnel type that is optimized for hosting HTTP services. An HTTP tunnel is the tunnel type that is optimized for hosting HTTP services.
It has filtering and rate-limiting features enabled that are tailored It has filtering and rate-limiting features enabled that are tailored
specifically to that purpose. A standard tunnel may work as well, but if you specifically to that purpose. A standard tunnel may work as well, but if you
select a atandard tunnel you'll need to take care of those security features select a atandard tunnel you'll need to take care of those security features
yourself. A more in-depth dive into the HTTP Tunnel configuration is available yourself. A more in-depth dive into the HTTP Tunnel configuration is available
in the next tutorial. in the next tutorial.
{%- endtrans %}
|Step Three: Select an HTTP Tunnel| |Step Three: Select an HTTP Tunnel|
Step Four: Give it a name and a description {% trans -%}Step Four: Give it a name and a description{%- endtrans %}
------------------------------------------- ----------------------------------------------------------------------
{% trans -%}
For your own benefit and ability to remeber and distinguish the what you are For your own benefit and ability to remeber and distinguish the what you are
using the tunnel for, give it a good nickname and description. If you need to using the tunnel for, give it a good nickname and description. If you need to
come back and do more management later, then this is how you will identify the come back and do more management later, then this is how you will identify the
tunnel in the hidden services manager. tunnel in the hidden services manager.
{%- endtrans %}
|Step Four: Give it a name and a description| |Step Four: Give it a name and a description|
Step Five: Configure the Host and Port {% trans -%}Step Five: Configure the Host and Port{%- endtrans %}
-------------------------------------- -----------------------------------------------------------------
{% trans -%}
In this step, you point the web server at the TCP port where your web server is In this step, you point the web server at the TCP port where your web server is
listening. Since most web servers listen on port 80 or port 8080, the example listening. Since most web servers listen on port 80 or port 8080, the example
shows that. If you use alternate ports or virtual machines or containers to shows that. If you use alternate ports or virtual machines or containers to
isolate your web services, you may need to adjust the host, port, or both. isolate your web services, you may need to adjust the host, port, or both.
{%- endtrans %}
|Step Five: Configure the Host and Port| |Step Five: Configure the Host and Port|
Step Six: Decide whether to start it automatically {% trans -%}Step Six: Decide whether to start it automatically{%- endtrans %}
-------------------------------------------------- -----------------------------------------------------------------------------
{% trans -%}
I cannot think of a way to elaborate on this step. I cannot think of a way to elaborate on this step.
{%- endtrans %}
|Step Six: Decide whether to start it automatically| |Step Six: Decide whether to start it automatically|
Step Seven: Review your settings {% trans -%}Step Seven: Review your settings{%- endtrans %}
-------------------------------- -----------------------------------------------------------
{% trans -%}
Finally, take a look at the settings you have selected. If you approve, save Finally, take a look at the settings you have selected. If you approve, save
them. If you did not choose to start the tunnel automatically, go to the hidden them. If you did not choose to start the tunnel automatically, go to the hidden
services manager and start it manually when you wish to make your service services manager and start it manually when you wish to make your service
available. available.
{%- endtrans %}
|Step Six: Review your settings| |Step Six: Review your settings|
Appendix: HTTP Server Customization Options {% trans -%}Appendix: HTTP Server Customization Options{%- endtrans %}
------------------------------------------- ----------------------------------------------------------------------
{% trans -%}
i2p provides a detailed panel for configuring the http server tunnel in custom i2p provides a detailed panel for configuring the http server tunnel in custom
ways. I'll finish this tutorial by walking through all of them. Eventually. ways. I'll finish this tutorial by walking through all of them. Eventually.
{%- endtrans %}
|Options page| |Options page 1|
|Options page| |Options page 2|
|Options page| |Options page 3|
|Options page| |Options page 4|
.. |Step One: Open the Tunnel Wizard| image:: /_static/images/00-wizard.png .. |Step One: Open the Tunnel Wizard| image:: /_static/images/00-wizard.png
.. |Step Two: Select a Server Tunnel| image:: /_static/images/01-select.png .. |Step Two: Select a Server Tunnel| image:: /_static/images/01-select.png
@@ -109,8 +129,8 @@ ways. I'll finish this tutorial by walking through all of them. Eventually.
.. |Step Five: Configure the Host and Port| image:: /_static/images/04-port.png .. |Step Five: Configure the Host and Port| image:: /_static/images/04-port.png
.. |Step Six: Decide whether to start it automatically| image:: /_static/images/05-auto.png .. |Step Six: Decide whether to start it automatically| image:: /_static/images/05-auto.png
.. |Step Six: Review your settings| image:: /_static/images/06-finish.png .. |Step Six: Review your settings| image:: /_static/images/06-finish.png
.. |Options page| image:: /_static/images/07-finished.png .. |Options page 1| image:: /_static/images/07-finished.png
.. |Options page| image:: /_static/images/08-finished.png .. |Options page 2| image:: /_static/images/08-finished.png
.. |Options page| image:: /_static/images/09-finished.png .. |Options page 3| image:: /_static/images/09-finished.png
.. |Options page| image:: /_static/images/10-finished.png .. |Options page 4| image:: /_static/images/10-finished.png