forked from I2P_Developers/i2p.www
add a way to do full-size screenshots in the blog
This commit is contained in:
@@ -38,6 +38,8 @@ Go to the I2P web interface at 127.0.0.1:7657 and open the
|
||||
localhost). Click the button that says "Tunnel Wizard" to begin.
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|Step One: Open the Tunnel Wizard|
|
||||
|
||||
{% trans -%}Step Two: Select a Server Tunnel{%- endtrans %}
|
||||
@@ -48,6 +50,8 @@ The tunnel wizard is very simple. Since we're setting up an http *server*, all
|
||||
we need to do is select a *server* tunnel.
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|Step Two: Select a Server Tunnel|
|
||||
|
||||
{% trans -%}Step Three: Select an HTTP Tunnel{%- endtrans %}
|
||||
@@ -62,6 +66,8 @@ yourself. A more in-depth dive into the HTTP Tunnel configuration is available
|
||||
in the next tutorial.
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|Step Three: Select an HTTP Tunnel|
|
||||
|
||||
{% trans -%}Step Four: Give it a name and a description{%- endtrans %}
|
||||
@@ -74,6 +80,8 @@ come back and do more management later, then this is how you will identify the
|
||||
tunnel in the hidden services manager.
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|Step Four: Give it a name and a description|
|
||||
|
||||
{% trans -%}Step Five: Configure the Host and Port{%- endtrans %}
|
||||
@@ -86,6 +94,8 @@ 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.
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|Step Five: Configure the Host and Port|
|
||||
|
||||
{% trans -%}Step Six: Decide whether to start it automatically{%- endtrans %}
|
||||
@@ -95,6 +105,8 @@ isolate your web services, you may need to adjust the host, port, or both.
|
||||
I cannot think of a way to elaborate on this step.
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|Step Six: Decide whether to start it automatically|
|
||||
|
||||
{% trans -%}Step Seven: Review your settings{%- endtrans %}
|
||||
@@ -107,6 +119,8 @@ services manager and start it manually when you wish to make your service
|
||||
available.
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|Step Six: Review your settings|
|
||||
|
||||
{% trans -%}Appendix: HTTP Server Customization Options{%- endtrans %}
|
||||
@@ -117,6 +131,8 @@ 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.
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|Options page 1|
|
||||
|
||||
.. |Step One: Open the Tunnel Wizard| image:: /_static/images/00-wizard.png
|
||||
|
@@ -182,6 +182,8 @@ At the bottom of the "I2P Hidden Services" section of the page, select an HTTP
|
||||
Service from the drop-down and click "Create."
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|config stuff|
|
||||
|
||||
{% trans -%}
|
||||
@@ -193,6 +195,8 @@ are the tunnel name and the target host:port. **The target host:port is**
|
||||
i2p. However, there are probably a few things that we can improve.
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|host stuff|
|
||||
|
||||
{% trans -%}
|
||||
@@ -204,6 +208,8 @@ to the bottom, save the tunnel configuration, and return to the tunnel
|
||||
configuration.
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|key stuff|
|
||||
|
||||
{% trans -%}
|
||||
@@ -213,6 +219,8 @@ provide anonymous access to others by an alternate gateway, it may be good to
|
||||
reduce the number of hops the tunnel takes on the I2P network.
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|tunnel stuff|
|
||||
|
||||
{% trans -%}
|
||||
@@ -222,6 +230,8 @@ blinding or encrypted leasesets. If you were to choose encrypted leasesets, you
|
||||
would not be accessible to anyone unless you shared a key with them in advance.
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|leaseset stuff|
|
||||
|
||||
{% trans -%}
|
||||
@@ -230,6 +240,8 @@ site or find yourself subject to DDOS attacks. Here you can configure various
|
||||
kinds of connection limits.
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|rate limiting stuff|
|
||||
|
||||
{% trans -%}
|
||||
@@ -244,12 +256,16 @@ local IP address instead of them all appearing to the server to be from
|
||||
127.0.0.1.
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|coarse blocking stuff|
|
||||
|
||||
{% trans -%}
|
||||
You can probably leave these next few options to the defaults.
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|Reduced tunnel stuff|
|
||||
|
||||
{% trans -%}
|
||||
@@ -258,6 +274,8 @@ what I'm prepared to do in this document, for more information see the format
|
||||
specification for now.
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|granular blocking stuff|
|
||||
|
||||
{% trans -%}Multi-Home an Application{%- endtrans %}
|
||||
@@ -270,6 +288,8 @@ to multihome your application, you will need to return to the tunnel menu and
|
||||
change the location of your private key file to it's own, non-shared location.
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|multihoming key stuff|
|
||||
|
||||
{% trans -%}
|
||||
@@ -307,6 +327,8 @@ Your base32 address is visible on the main i2ptunnel configuration page and it
|
||||
looks like this:
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|base32 stuff|
|
||||
|
||||
{% trans -%}
|
||||
@@ -327,6 +349,8 @@ followed by ?i2paddresshelper=, followed by the Local Destination of the tunnel
|
||||
you just created, which you can see here:
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|local destination stuff|
|
||||
|
||||
{% trans -%}
|
||||
|
@@ -51,6 +51,8 @@ Since you are setting up this tunnel for the SSH server, you need to select the
|
||||
"Server" tunnel type.
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|Use the wizard to create a "Server" tunnel|
|
||||
|
||||
{% trans -%}
|
||||
@@ -58,12 +60,16 @@ You should fine-tune it later, but the Standard tunnel type is easiest to start
|
||||
with.
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|Of the "Standard" variety|
|
||||
|
||||
{% trans -%}
|
||||
Give it a good description:
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|Describe what it is for|
|
||||
|
||||
{% trans -%}
|
||||
@@ -76,6 +82,8 @@ And tell it where the SSH server will be available.
|
||||
Look over the results, and save your settings.
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|Save the settings.|
|
||||
|
||||
{% trans -%}Advanced Settings{%- endtrans %}
|
||||
@@ -87,6 +95,8 @@ advanced settings. One thing you'll definitely want to change is to set it up
|
||||
for interactive connections intstead of bulk connections.
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|Configure your tunnel for interactive connectionss|
|
||||
|
||||
{% trans -%}
|
||||
@@ -97,6 +107,8 @@ count might help. A few backup tunnels are probably a good idea. You might have
|
||||
to dial-it-in a bit.
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|If you're not concerned about anonymity, then reduce tunnel length.|
|
||||
|
||||
{% trans -%}
|
||||
@@ -109,6 +121,8 @@ tunnels is "Reduce on Idle" which will reduce the number of tunnels that run
|
||||
when the serve has experienced extended inactivity.
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|Reduce on idle, if you chose a high number of tunnels|
|
||||
|
||||
{% trans -%}Using i2pd{%- endtrans %}
|
||||
@@ -185,6 +199,8 @@ First, start the tunnel configuration wizard from the hidden services manager
|
||||
and select a client tunnel.
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|Use the wizard to create a client tunnel|
|
||||
|
||||
{% trans -%}
|
||||
@@ -192,12 +208,16 @@ Next, select the standard tunnel type. You will fine-tune this configuration
|
||||
later.
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|Of the Standard variety|
|
||||
|
||||
{% trans -%}
|
||||
Give it a good description.
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|Give it a good description|
|
||||
|
||||
{% trans -%}
|
||||
@@ -208,6 +228,8 @@ I generally `Tox <https://tox.chat>`__ it to myself, any off-the-record
|
||||
should be sufficient for most people.
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|Find the destination you want to connect to|
|
||||
|
||||
{% trans -%}
|
||||
@@ -215,6 +237,8 @@ Once you've found the base64 destination you want to connect to transmitted to
|
||||
your client device, then paste it into the client destination field.
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|Affix the destination|
|
||||
|
||||
{% trans -%}
|
||||
@@ -222,12 +246,16 @@ Lastly, set a local port to connect your ssh client to. This will local port
|
||||
will be connected to the base64 destination and thus the SSH server.
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|Choose a local port|
|
||||
|
||||
{% trans -%}
|
||||
Decide whether you want it to start automatically.
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|Decide if you want it to autostart|
|
||||
|
||||
.. _advanced-settings-1:
|
||||
@@ -242,6 +270,8 @@ server, you should check the "Generate key to enable persistent client tunnel
|
||||
identity" radial button.
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|Configure it to be interactive|
|
||||
|
||||
.. _using-i2pd-1:
|
||||
@@ -321,6 +351,8 @@ First, retrieve the persistent client tunnel destination and transmit it to the
|
||||
server.
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|Get the client destination|
|
||||
|
||||
{% trans -%}
|
||||
@@ -329,6 +361,8 @@ you'll only be able to connect to the server tunnel from that specific client
|
||||
tunnel and no one else will be able to connect to that destination.
|
||||
{%- endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|And paste it onto the server whitelist|
|
||||
|
||||
{% trans -%}
|
||||
|
@@ -20,6 +20,8 @@ adds overhead to the familiar experience of using the internet so that you can
|
||||
have privacy, but this means that for many or most I2P services, your data will
|
||||
need to go through 12 hops by default.{% endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|Diagram of I2P Connection|
|
||||
`Analysis of tools for online anonymity <https://www.researchgate.net/publication/289531182_An_analysis_of_tools_for_online_anonymity>`__
|
||||
|
||||
@@ -46,6 +48,8 @@ Configuration” (“Configure Bandwidth” button in the “Applications and
|
||||
Configuration” section of I2P Router Console, or
|
||||
http://localhost:7657/config).{% endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|I2P Bandwidth Configuration|
|
||||
|
||||
{% trans %}If you see a shared bandwidth limit of 48 KBps, which is very low, then you
|
||||
@@ -65,6 +69,8 @@ service provider or bcause you installed I2P before version 0.9.38, you can
|
||||
re-launch it from the 'Setup' link on the 'Help & FAQ' page, or simply access
|
||||
the wizard directly at http://localhost:7657/welcome{% endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|Can you find “Setup”?|
|
||||
|
||||
{% trans %}Using the Wizard is straightforward, simply keep clicking “Next”. Sometimes
|
||||
@@ -72,6 +78,8 @@ M-Lab’s chosen measurement servers are down and the test fails. In such case,
|
||||
click “Previous” (do not use your web browser’s “back” button), then
|
||||
try it again.{% endtrans %}
|
||||
|
||||
.. class:: screenshot
|
||||
|
||||
|Bandwidth Test Results|
|
||||
|
||||
{% trans %}Running I2P continuously{% endtrans %}
|
||||
|
@@ -572,6 +572,13 @@ div#content .inner ul.DREAD {
|
||||
overflow: auto;
|
||||
}
|
||||
|
||||
#post .screenshot img {
|
||||
max-width: 95% !important;
|
||||
min-height: unset;
|
||||
float: unset;
|
||||
padding-right: unset;
|
||||
}
|
||||
|
||||
.system-messages {
|
||||
background-color: rgba(171, 204, 113, 0.7);
|
||||
border: 1px dashed rgb(208, 14, 14);
|
||||
|
Reference in New Issue
Block a user