{% extends "global/layout.html" %} {% block title %}I2PTunnel{% endblock %} {% block content %}

{% trans %}Overview{% endtrans %}

{% trans naming=site_url('docs/naming') -%} I2PTunnel is a tool for interfacing with and providing services on I2P. Destination of an I2PTunnel can be defined using a hostname, Base32, or a full 516-byte destination key. An established I2PTunnel will be available on your client machine as localhost:port. If you wish to provide a service on I2P network, you simply create I2PTunnel to the appropriate ip_address:port. A corresponding 516-byte destination key will be generated for the service and it will become avaliable throughout I2P. A web interface for I2PTunnel management is avaliable on localhost:7657/i2ptunnel/. {%- endtrans %}

{% trans %}Default Services{% endtrans %}

{% trans %}Server tunnels{% endtrans %}

{% trans %}Client tunnels{% endtrans %}

{% trans %}Configuration{% endtrans %}

{{ _('I2PTunnel Configuration') }}

{% trans %}Client Modes{% endtrans %}

{% trans %}Standard{% endtrans %}

{% trans -%} Opens a local TCP port that connects to a service (like HTTP, FTP or SMTP) on a destination inside of I2P. The tunnel is directed to a random host from the comma seperated (", ") list of destinations. {%- endtrans %}

HTTP

{% trans -%} A HTTP-client tunnel. The tunnel connects to the destination specified by the URL in a HTTP request. Supports proxying onto internet if an outproxy is provided. Strips HTTP connections of the following headers: {%- endtrans %}

{% trans -%} HTTP client/server tunnels are via I2Ptunnel force-enabling compression via the following http headers: {%- endtrans %}

{% trans -%} Depending on if the tunnel is using an outproxy or not it will append the following User-Agent: {%- endtrans %}

IRC

{% trans -%} Creates a connection to a random IRC server specified by the comma seprated (", ") list of destinations. Only a whitelisted subset of IRC commands are allowed due to anonymity concerns. {%- endtrans %}
{% trans %}Whitelist:{% endtrans %}

SOCKS 4/4a/5

{% trans -%} Enables using the I2P router as a SOCKS proxy. {%- endtrans %}

SOCKS IRC

{% trans -%} Enables using the I2P router as a SOCKS proxy with the command whitelist specified by IRC client mode. {%- endtrans %}

CONNECT

{% trans -%} Creates a HTTP tunnel and uses the HTTP request method "CONNECT" to build a TCP tunnel that usually is used for SSL and HTTPS. {%- endtrans %}

Streamr

{% trans -%} Creates a UDP-server attached to a Streamr client I2PTunnel. The streamr client tunnel will subscribe to a streamr server tunnel. {%- endtrans %}


{% trans %}Server Modes{% endtrans %}

{% trans %}Standard{% endtrans %}

{% trans -%} Creates a destination to a local ip:port with an open TCP port. {%- endtrans %}

HTTP

{% trans -%} Creates a destination to a local HTTP server ip:port. Supports gzip for requests with Accept-encoding: x-i2p-gzip, replies with Content-encoding: x-i2p-gzip in such a request. {%- endtrans %}

HTTP Bidirectional

{% trans -%} Functions as both a I2PTunnel HTTP Server, and a I2PTunnel HTTP client with no outproxying capabilities. An example application would be a web application that does client-type requests, or loopback-testing an eepsite as a diagnostic tool. {%- endtrans %}

IRC

{% trans -%} Creates a destination that filters the reqistration sequence of a client and passes the clients destination key as a hostname to the IRC-server. {%- endtrans %}

Streamr

{% trans -%} A UDP-client that connects to a media server is created. The UDP-Client is coupled with a Streamr server I2PTunnel. {%- endtrans %}

{% endblock %}