Bump I2P to 0.9.50
|10 months ago|
|bin||10 months ago|
|org.getmonero.i2p.zero||10 months ago|
|org.getmonero.i2p.zero.gui||1 year ago|
|org.getmonero.util.normalizeZip||2 years ago|
|resources||1 year ago|
|.gitignore||3 years ago|
|LICENSE||3 years ago|
|README.md||10 months ago|
|i2p-zero.iml||3 years ago|
|i2p-zero.png||3 years ago|
|mipseed.md||1 year ago|
|monerod-with-i2p-zero.md||1 year ago|
|screenshot1.png||3 years ago|
|screenshot2.png||3 years ago|
|screenshot3.png||3 years ago|
Zero dependency, small footprint, cross-platform I2P Java Router with GUI, simple tunnel/socks controller and SAM interface
Note that I2P-zero is not a re-implementation of I2P. It uses the exact I2P source code from the official I2P GitHub repository.
I2P-zero is a build script that produces a zero-dependency installation of the official I2P release, and includes a simplified front end interface.
This project will run under Linux, and build native launchers for Linux, MacOS and Windows. The launchers will include the I2P router, a SAM listener, simple tunnel and socks tunnel functionality and a minimal JVM.
Download the latest binary releases for Mac/Windows/Linux here: https://github.com/i2p-zero/i2p-zero/releases
The zero-dependency distribution sizes are as follows:
|OS||Uncompressed size (MB)||Compressed size (MB)||v1.20 Reproducible build SHA-256|
Note: Reproducible builds are currently experimental. Due to JDK differences, Builds on Mac will consistently have different hashes than builds on Linux. Official releases will always be built using Docker.
Building the launchers
All binary releases for Windows, Mac and Linux can be built from either Linux or Mac.
Use the Docker build method for reproducible builds.
To build using Docker on Mac:
First install docker from https://hub.docker.com/editions/community/docker-ce-desktop-mac
containerId=$(docker run -td --rm ubuntu) docker exec -ti $containerId bash -c '\ apt-get update \ && apt-get -y install git wget zip unzip \ && git clone https://github.com/i2p-zero/i2p-zero.git --depth 1 \ && cd i2p-zero && bash bin/build-all-and-zip.sh' docker cp $containerId:/i2p-zero/dist-zip ./ docker container stop $containerId
To build using Docker on Ubuntu:
sudo apt -y install docker docker.io systemctl start docker containerId=$(sudo docker run -td --rm ubuntu) sudo docker exec -ti $containerId bash -c '\ apt-get update \ && apt-get -y install git wget zip unzip \ && git clone https://github.com/i2p-zero/i2p-zero.git --depth 1 \ && cd i2p-zero && bash bin/build-all-and-zip.sh' sudo docker cp $containerId:/i2p-zero/dist-zip ./ sudo docker container stop $containerId
This will result in a dist-zip directory being copied into the current directory. The dist-zip directory will contain the builds for all platforms.
To build without Docker on Ubuntu:
To build without Docker on a freshly installed Ubuntu system, first ensure git is installed:
sudo apt install git
Then, retrieve this project from git:
git clone https://github.com/i2p-zero/i2p-zero.git
Also note that JDKs for Linux, MacOS and Windows will be downloaded, which will total several hundred megabytes. You may need to ensure your system has zip, unzip and bzip2 installed to run the build script.
bin/build-all-and-zip.sh script, which will in turn call the following scripts:
bin/import-packages.shto retrieve the I2P Java sources, OpenJDK and the Ant build tool
bin/build-original-i2p.shto build the I2P project retrieved from the I2P repository
bin/build-launcher.shto convert the I2P JARs to modules, compile the Java source code in this project, and then use the jlink tool to build zero-dependency platform-specific launchers.
bin/zip-all.shto produce the distribution zip files and display their SHA-256 hashes. Note that reproducible builds are currently a work in progress, and that only builds on Linux will show the same hashes as the official releases.
Running the GUI
To run the Linux router, double-click the app located at
To run the MacOS router, double-click the app located at
For Windows, double-click the app located at
Running the command line version
To run the Linux router, type:
To run the MacOS router, type:
For Windows, run: (note that the Windows build will run in the background and not show a success message)
If it launches successfully, you'll see the message:
I2P router launched. Press Ctrl-C to gracefully shut down the router (or send the SIGINT signal to the process).
Note that it may take a short while for new tunnels to be set up.
dist/linux/router/bin/tunnel-control.sh script as follows to create and destroy tunnels:
Get the router reachability status. Returns a string such as "Testing", "Firewalled", "Running", "Error"
Find out if the router is running (where "running" means it has warmed up and is allowing I2P connections to be created). Returns "true" or "false"
Listen for I2P connections and forward them to the specified host and port. Returns the I2P base 32 destination address for the server tunnel created.
Optionally, specify a directory for storing/reading the server key file. If the directory doesn't exist with a file named *.b32.i2p.keys in it, returns a newly created destination address and writes the secret key for the new address to a file called .keys in the specified directory. Otherwise, read the existing secret key from that directory. The server tunnel will listen for I2P connections and forward them to the specified host and port. Note that the base 32 I2P destination address deterministically depends on the contents of the .keys file).
tunnel-control.sh server.create <host> <port> <(optional) directory>
or, if you would like a vanity b32 address for your server tunnel that begins with a 3 character (alphanumeric) prefix, type:
tunnel-control.sh server.create.vanity <host> <port> <directory> <prefix>
If you do not want to specify the directory parameter above, specify
none as the directory. Note that this command may take several minutes to complete.
Check the state of a tunnel. Returns "opening" or "open"
tunnel-control.sh server.state <base 32 I2P address>
tunnel-control.sh client.state <local port>
tunnel-control.sh http.state <local port>
tunnel-control.sh socks.state <local port>
Close the tunnel listening for connections on the specified I2P destination address. Returns "OK".
tunnel-control.sh server.destroy <base 32 I2P address>
Create a tunnel that listens for connections on localhost on the specified port and forwards connections over I2P to the specified destination public key.
tunnel-control.sh client.create <I2P destination> <local port>
Close the tunnel listening for connections on the specified port. Returns "OK".
tunnel-control.sh client.destroy <local port>
Create an http proxy (for accessing .i2p web sites), listening on the specified port
tunnel-control.sh http.create <local port>
Destroy the http proxy listening on the specified port
tunnel-control.sh http.destroy <local port>
Create a socks tunnel, listening on the specified port
tunnel-control.sh socks.create <local port>
Destroy the socks tunnel listening on the specified port
tunnel-control.sh socks.destroy <local port>
Destroy all tunnels. Returns "OK"
List all tunnels. Returns JSON string containing information about all tunnels currently in existence
Start a SAM listener on port 7656. Returns "OK"
Get the external port randomly assigned to this router when first run, which the firewall should allow incoming UDP and TCP connections on. Returns the port number.
Set the bandwidth limit, measured in KBps. Returns "OK".
tunnel-control.sh router.setBandwidthLimitKBps <KBps>
Get the bandwidth limit, measured in KBps
Get bandwidth statistics. Returns a comma separated list of statistics
or, for pleasant viewing on the command line, automatically updating every 2 seconds:
watch "tunnel-control.sh router.getBandwidthStats | tr ',' '\n' | sort"
Get the I2P-zero version
Watch the I2P log for messages
tail -f dist/linux/router/i2p.config/wrapper.log
Note on bundled windows launcher.exe executable
There is a bundled
resources/launcher.exe file in the source tree. This allows the windows distributable to be built
even on a non-windows platform.
#This file can be deterministically recreated by following these steps on a Windows machine:
- Download AdoptOpenJDK14 from https://github.com/AdoptOpenJDK/openjdk14-binaries/releases/download/jdk14-2020-03-09-04-56/OpenJDK14-jdk_x64_windows_hotspot_2020-03-09-04-56.zip
- Create a new folder, and place inside the
resources/icons.icofile and the
routerfolder from an I2P-zero for Windows GUI build
- Run `\bin\jpackage.exe --type app-image --icon icons.ico --name i2p-zero -m org.getmonero.i2p.zero.gui/org.getmonero.i2p.zero.gui.Gui --runtime-image router\runtime
certUtil -hashfile i2p-zero/i2p-zero.exe SHA256to get the SHA256 hash.
- This hash should exactly match the SHA256 hash of the
resources/launcher.exefile, which should be