Switched to AdoptOpenJDK 14.0.1_7 and JavaFX 14
Switched from jpackager to jpackage which is now part of JDK14
Windows launcher executable has changed due to move from jpackager to jpackage
Added socks port to mipseed instructions
Note that the current version of this script uses jdk-13. If this version of Java becomes no longer available for
download, then update the references in java-config.sh to the later version. To locate a recent
JDK download URL, see https://jdk.java.net/13/
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.
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.
Run the `bin/build-all-and-zip.sh` script, which will in turn call the following scripts:
Run the `bin/build-all-and-zip.sh` script, which will in turn call the following scripts:
@ -70,25 +66,25 @@ the jlink tool to build zero-dependency platform-specific launchers.
## Running the GUI
## Running the GUI
To run the Linux router, double-click the app located at `dist/linux-gui/router/i2p-zero`
To run the Linux router, double-click the app located at `dist/linux-gui/router/bin/i2p-zero`
To run the MacOS router, double-click the app located at `dist/mac-gui/router/i2p-zero.app`
To run the MacOS router, double-click the app located at `dist/mac-gui/router/i2p-zero.app`
For Windows, double-click the app located at `dist/windows-gui/router/i2p-zero.exe`
For Windows, double-click the app located at `dist/win-gui/router/i2p-zero.exe`
## Running the command line version
## Running the command line version
To run the Linux router, type:
To run the Linux router, type:
`dist/linux/router/bin/launch.sh`
`dist/linux/router/bin/i2p-zero`
To run the MacOS router, type:
To run the MacOS router, type:
`dist/mac/router/bin/launch.sh`
`dist/mac/router/bin/launch.sh`
For Windows, run:
For Windows, run: (note that the Windows build will run in the background and not show a success message)
`dist/windows/router/bin/launch.bat`
`dist/win/router/i2p-zero.exe`
If it launches successfully, you'll see the message:
If it launches successfully, you'll see the message:
## Note on bundled windows launcher.exe executable
There is a bundled resources/wrapper.exe file in the source tree. This allows the windows distributable to be built
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.
even on a non-windows platform.
This file can be deterministically recreated by
#This file can be deterministically recreated by following these steps on a Windows machine:
downloading javapackager from http://download2.gluonhq.com/jpackager/11/jdk.packager-windows.zip, unzipping it,
1. 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
unzipping the jar file within that, and obtaining the jdk/packager/internal/resources/windows/papplauncher.exe file.
2. Create a new folder, and place inside the `resources/icons.ico` file and the `router` folder from an I2P-zero for Windows GUI build
Then, on Windows, download Resource Hacker version 5.1.7 from http://www.angusj.com/resourcehacker/ and use it to add the
4. Run `certUtil -hashfile i2p-zero/i2p-zero.exe SHA256` to get the SHA256 hash.
resources/icons.ico file to the papplauncher.exe file. Finally, verify that the resulting file is identical to the bundled resources/wrapper.exe file.
5. This hash should exactly match the SHA256 hash of the `resources/launcher.exe` file, which should be `3d5d00eeff5cb9d63ea415c593d67f201a7d024b6378d22d702b001e6693a93a`
The sha256 checksum of the file should be `50c9286b9da7a91b8715de3cbcd141ec44eb199642562f43ce82351609115e06`
6. Create a server tunnel for incoming I2P connections by typing: `router/bin/tunnel-control.sh server.create.vanity 127.0.0.1 8061 none xyz` replacing `xyz` with a 3 alphanumeric character vanity prefix for your public b32.i2p address. This command will take a few minutes to complete, depending on how fast your CPU is. If you do not want a vanity prefix, use the command: `router/bin/tunnel-control.sh server.create 127.0.0.1 8061`
6. Create a server tunnel for incoming I2P connections by typing: `router/bin/tunnel-control.sh server.create.vanity 127.0.0.1 8061 none xyz` replacing `xyz` with a 3 alphanumeric character vanity prefix for your public b32.i2p address. This command will take a few minutes to complete, depending on how fast your CPU is. If you do not want a vanity prefix, use the command: `router/bin/tunnel-control.sh server.create 127.0.0.1 8061`
7. The command above will result in an I2P address being printed to the command line, which will end with `.b32.i2p`. This is your new I2P address.
7. The command above will result in an I2P address being printed to the command line, which will end with `.b32.i2p`. This is your new I2P address.
8. You now need to keep a backup of your private keys to your I2P address on another computer for safekeeping. Do this by taking a backup of the `~/.i2p-zero/config/tunnels.json` file
8. You now need to keep a backup of your private keys to your I2P address on another computer for safekeeping. Do this by taking a backup of the `~/.i2p-zero/config/tunnels.json` file
9. Run monerod by typing the following, replacing `XXXXXXXXXXXXXXXXXXXXXXXXXXXXX.b32.i2p` with your own I2P address that was printed from step 5: `monerod --tx-proxy i2p,127.0.0.1:8060 --add-peer dsc7fyzzultm7y6pmx2avu6tze3usc7d27nkbzs5qwuujplxcmzq.b32.i2p --anonymous-inbound XXXXXXXXXXXXXXXXXXXXXXXXXXXXX.b32.i2p,127.0.0.1 --prune-blockchain --detach`.
9. Run monerod by typing the following, replacing `XXXXXXXXXXXXXXXXXXXXXXXXXXXXX.b32.i2p` with your own I2P address that was printed from step 5: `monerod --tx-proxy i2p,127.0.0.1:8060 --add-peer dsc7fyzzultm7y6pmx2avu6tze3usc7d27nkbzs5qwuujplxcmzq.b32.i2p --anonymous-inbound XXXXXXXXXXXXXXXXXXXXXXXXXXXXX.b32.i2p,127.0.0.1:8061 --prune-blockchain --detach`.
10. (optional) Use software such as wondershaper for Linux to limit bandwidth usage. See this: https://www.ostechnix.com/how-to-limit-network-bandwidth-in-linux-using-wondershaper/
10. (optional) Use software such as wondershaper for Linux to limit bandwidth usage. See this: https://www.ostechnix.com/how-to-limit-network-bandwidth-in-linux-using-wondershaper/
That's it! Do not replace the dsc****.b32.i2p address with yours, only replace the XXXXXXX.b32.i2p one. You are now running a mipseed, which will itself be seeded by dsc_'s mipseed.
That's it! Do not replace the dsc****.b32.i2p address with yours, only replace the XXXXXXX.b32.i2p one. You are now running a mipseed, which will itself be seeded by dsc_'s mipseed.
knaccc
4 years ago