|Konrad Bächler 86cae276c9||1 month ago|
|bin||1 month ago|
|certificates||3 months ago|
|conf||1 month ago|
|htdocs||2 months ago|
|network||3 months ago|
|tunnels.conf.d||2 months ago|
|tunnels.example.conf.d||2 months ago|
|.gitignore||5 months ago|
|ChangeLog||1 month ago|
|ChangeLog-i2pd||1 month ago|
|Dockerfile||2 months ago|
|LICENSE||5 months ago|
|LICENSE-i2pd||4 months ago|
|README.md||1 month ago|
|entrypoint.sh||2 months ago|
Two flavours are available:
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”.
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.
All DNS queries of this docker container are resolved using DNS-over-TLS (DoT). DoT makes it difficult to spy out DNS queries.
Docker (https://www.docker.com/get-started) must be available on your system.
To get your new private browsing experience up and running:
docker pull divax/i2p:i2p-tor-proxyor
docker pull divax/i2p:latest
As said, this tutorial might be helpful: Introduction to “I2P”.
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 your now-running docker container with
docker ps -a (within your shell/powershell) and look for the container “i2pd”.
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.
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
i2pd.org.conf contains the main I2P configuration. The configuration files for DNS-over-TLS are found within the folder
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
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
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.conf.d and run the container with the bind mount or by executing
To rebuild the docker image and all the contained binaries from source, execute
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
On DIVA.EXCHANGE you’ll find various options to get in touch with the team.
Your donation goes entirely to the project. Your donation makes the development of DIVA.EXCHANGE faster.
Awesome, thank you!