I2P Layer of diva.exchange. Based on i2pd, see https://github.com/PurpleI2P/i2pd https://diva.exchange
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
Konrad Bächler c498a22475 Docker image Tag fix 6 days ago
bin Docker image Tag fix 6 days ago
certificates Added reseed.diva.exchange as a reseed server including public key 2 weeks ago
conf flexible tunnel configuration 1 week ago
htdocs updated startup scripts to ease configuration 1 week ago
network replaced dnsmasq by stubby, added Changelog, updated README 1 month ago
reseed Added reseed.diva.exchange as a reseed server including public key 2 weeks ago
tunnels.conf.d flexible tunnel configuration 1 week ago
tunnels.example.conf.d flexible tunnel configuration 1 week ago
.gitignore Moved from gitlab to codeberg - initial 2 months ago
ChangeLog updated startup scripts to ease configuration 1 week ago
ChangeLog-i2pd * improved Dockerfile: image size now <30MB 1 month ago
Dockerfile Docker image Tag fix 6 days ago
LICENSE Moved from gitlab to codeberg - initial 2 months ago
LICENSE-i2pd Optimized Docker image for size and speed: 1 month ago
README.md README, text clarification 1 week ago
entrypoint.sh develop branch: lean i2p version 1 week ago

README.md

I2P - For Everyone

Two flavours are available:

  • Entry-level experience: I2P and Tor to enable everyone to get started using the i2p and onion network. It’s tagged as “i2p-tor-proxy”.
  • For advanced users: I2P only version - very lean. It’s tagged as “latest”.

The solutions are deployed as docker image.

If you are looking for an entry-level experience, focused on safely browsing the internet: use the docker image tagged as “i2p-tor-proxy”. Read the “Get Started” below.

If you are experienced and looking for an I2P-only container - go for the docker imaged tagged as “latest”. You get the latest stable i2pd (C++ version) release. Lean & fast.

A great tutorial, including “How to setup your system”, is found here: Introduction to “I2P”.

Entry-Level Experience - I2P & Onion: Private Browsing

Enjoy a smooth and private browsing experience on multiple networks (like https://diva.exchange or also onion and i2p sites like http://diva.i2p or http://kopanyoc2lnsx5qwpslkik4uccej6zqna7qq2igbofhmb2qxwflwfqad.onion). Use your favourite browser (like Firefox). Hence it should be suitable for beginners.

Please note: an entry-level setup is only a first - yet necessary - step to protect your privacy. You need to change your behaviour to protect your online privacy (like: use NoScript, AdBlock). Also fingerprinting (a hash of your online footprint) and obviously login data is threatening your privacy. This project helps you to get started with private browsing.

DNS-over-TLS

All DNS queries of this docker container are resolved using DNS-over-TLS (DoT). DoT makes it difficult to spy out DNS queries.

Get Started

Docker (https://www.docker.com/get-started) must be available on your system.

To get your new private browsing experience up and running:

  1. Pull the docker image (in a shell/powershell): docker pull divax/i2p:i2p-tor-proxy or docker pull divax/i2p:latest
  2. Run the Docker container
  3. Adapt your browser proxy settings

As said, this tutorial might be helpful: Introduction to “I2P”.

How to Run the Docker Container

On Linux, OSX and Windows

Run one of the following command in a shell (powershell on Windows).

To run the I2P/TOR/proxy only (entry-level):

docker run --env PORT_TOR=9950 --env PORT_HTTP_PROXY=4544 -p 7170:7070 -p 4544:4444 -p 9950:9050 -p 8080:8080 -d --name i2p-tor-proxy divax/i2p:i2p-tor-proxy

To run I2P only (advanced):

docker run -p 7070:7070 -p 4444:4444 -p 4445:4445 -d --name i2pd divax/i2p:latest

Check the Status of your Container

Check your now-running docker container with docker ps -a (within your shell/powershell) and look for the container “i2pd”.

Entry-Level: How to Adapt the Proxy Settings of Your Browser

Open your favourite browser, like Firefox. Open the settings. Search for “proxy”. Then enable “Automatic proxy configuration URL” and set it to “http://localhost:8080/proxy.pac”.

This proxy configuration (see source code below for details) uses your new docker container to route all your browser traffic through either I2P or Tor. If you now browse the clearnet (like https://diva.exchange) you’ll be using automatically Tor.

If you prefer a weaker configuration you can also use the proxy file proxy-ip2-onion-clearnet.pac and set the “Automatic proxy configuration URL” to “http://localhost:8080/proxy-ip2-onion-clearnet.pac”. This will only route .i2p and .onion addresses through the docker container. Routes to the clearnet won’t be affected.

Advanced: Configuration

The docker container is exposing an http and a socks proxy. By default, the container exposes the http proxy on port 4444 and the socks proxy on port 4445.

The configuration files for I2P are found within the folder ./conf, whereas i2pd.org.conf contains the main I2P configuration. The configuration files for DNS-over-TLS are found within the folder ./network: resolv.conf is containing nameserver information and stubby.yml contains the configuration for DNS-over-TLS. The Tor configuration file is found within the folder ./network: torrc configures the behaviour of the Tor service.

The configuration of a container might be influenced with environment variables: ENABLE_TUNNELS and IP_BRIDGE.

Set ENABLE_TUNNELS to 1 to use the tunnels configuration within the container. Defaults to 0 and therefore tunnels are disabled by default.

IP_BRIDGE points by default to the docker host interface.

Example on how to use environment variables:

docker run --env ENABLE_TUNNELS=1 -p 127.0.0.1:7070:7070 -p 127.0.0.1:4444:4444 -p 127.0.0.1:4445:4445 -d --name i2pd divax/i2p:latest

Advanced: Tunnel Configuration

Tunnels are exposing specific services to the I2P network. Like a web server, an application or a blockchain.

Tunnels might be configured on the host within a folder, like tunnels.conf.d. Then this folder gets mounted into the container as a bind mount. See ./bin/run.sh on how to set up such a bind mount.

Some examples of tunnel configuration files are found within the folder tunnels.example.conf.d. To use such an example just copy the file from tunnels.example.conf.d to tunnels.conf.d and run the container with the bind mount or by executing ENABLE_TUNNELS=1 ./bin/run.sh.

Build from Source

On Linux

To rebuild the docker image and all the contained binaries from source, execute ./bin/build.sh

Source Code

GPLv3 licensed and the source code is available here: https://codeberg.org/diva.exchange/i2p

The source code of the underlying “I2Pd” project is found here: https://github.com/PurpleI2P/i2pd

The source code of the included DNS-over-TLS project, “stubby”, is found here: https://github.com/getdnsapi/stubby

Contact the Developers

Talk to us on Telegram https://t.me/diva_exchange_chat_de (English or German).