I2P+ 2.6.0+ released!

Posted by z3d in I2P (edited )

I2P+ is an enhanced version of I2P that aims to deliver a superior user experience. Updated themes, easier to understand configuration and diagnostics, and an enhanced feature set make I2P+ a compelling alternative to the official I2P release. Additionally, I2P+ implements improvements to the routerʼs network performance and, for routers that are firewalled, can significantly increase participating traffic and network responsiveness.

Is I2P+ compatible with I2P?

The changes relate to user interaction and enhanced presentation of the console and webapps, in addition to network performance improvements, leaving the underyling crypto untouched, so it remains 100% compatible with I2P. On the network, an I2P+ router will identify as a normal I2P router. Updating from I2P to I2P+, or from I2P+ to I2P, is as simple as providing the router with the relevant update file and restarting.

Installation

If you're running a manually installed version of I2P (from the Java installer, not the Easy Installer Bundle, nor a Linux repository or .deb file), updating is as simple as dropping the i2pupdate.zip file into your I2P application folder and restarting the router. Note: Do not extract the zip file, simply copy it to the I2P application folder and restart I2P... I2P will extract the zip automatically and update. (Java 1.8 or later required). For information about migrating from a repo or .deb install, visit the I2P+ site linked below.

To enable updates for I2P+, visit the update page at http://127.0.0.1:7657/configupdate and enable unsigned development updates. The default update address will inform you of release updates, or for development updates (aka rolling release), replace the address with: http://skank.i2p/dev/i2pupdate.zip

Note: If you have installed I2P from the Easy Installer Bundle, this will need to be uninstalled first and your configuration directory renamed or deleted - see the included INSTALL.txt file for more info.

New since 2.5.2+

  • Add toggle on /tunnels to show/hide individual tunnels to allow for a condensed summary of bandwidth usage
  • Display floodfill icon in sidebar in network status section when active (requested by postman)
  • Translation status report at http://127.0.0.1:7657/debug?d=6
  • New Javascript-generated SVG identicons in addressbook
  • New configuration option routerconsole.pageTitlePrefix={text} to add a page title prefix to console pages (requested by postman)
  • New content blocker for http server tunnel which allows the configuration of keywords or urls to block when accessed
  • http_blocklist.txt defines the keywords, clients accessing blocked urls logged to http_blocklist_clients.txt to permit permanent blocking via tunnel filter
  • Prevention of access to local addresses when running an http server outproxy tunnel
  • World map displaying distribution of routers in local network database at http://127.0.0.1:7657/netdbmap
  • Various presentational improvements to graphs including improvements to y axis display and progressive downsampling as the display period increases
  • Load graphs concurrently on /graphs and update inline without placeholders on refresh
  • Single graph manipulation inline via AJAX requests (no page reload when changing parameters)
  • Display I2PChat icon in sidebar in Services section when running
  • Differentiate between active seeding and seeding with no peers in I2PSnark
  • Console and webapp theme improvements
  • Console logging improvements
  • New and updated console/webapp translations

More information

4

Comments

You must log in or register to comment.

NotQball wrote

http://skank.i2p/installers/i2pinstall_2.6.0+.exe inside i2p+ also fails on Motrix error 19: If name resolution failed. Similar with other down-loaders including browser.

I2P: 2.6.0-0+ API: 0.9.63 Wrapper: 3.5.51  Built by: dr|z3d Platform: Linux amd64 6.8.9-1kaisen-amd64 Processor: coreibwl  Skylake Core i3/i5/i7  [Jcpuid version: 3] Java: N/A 21 (OpenJDK Runtime Environment 21+-adhoc.nixbld.source) Jetty: 9.3.30.v20211001 Servlet: Jasper JSP 2.3 Engine (3.1) JBigI: Native BigInteger library libjbigi-linux-coreibwl_64.so loaded from resource [version: 4] GMP: 6.1.2 JSTL: standard-taglib 1.2.0 Encoding: UTF-8 Charset: UTF-8

sha256sum i2p+ torrent downloaded: 736f38a5ac5121d33b7576cb1f61e6a9b5a28008b82795fdb31c7fb00dfd9b56

sha512sum i2p+ downloaded:

898866b715e8a32cd87d559a61d48b0d5c644d695807389f0d02bc87561cd949771e09c926df248cb422ca99b78c16dc70d375b2f64c42b4d3d70f631f29d29d

1

z3d OP wrote (edited )

Differences in the sha hashes are a result of infrequent updates to the i2pupdate.zip being served from http://skank.i2p/i2pupdate.zip ... occasionally a new update will appear, either to add new features (in the recent case, more complete translations) or fix bugs. To identify exactly which revision you're running, you can view the hashes on 127.0.0.1:7657/jars.

In addition, for some users a new release will revert them to vanilla I2P, so updating the I2P+ zip available on skank.i2p will sometimes fix this if it's date stamped after the update to vanilla.

As for "corrupt" downloads, if you're in the middle of an update when a new version is uploaded, your download will become corrupted, in which case re-downloading the update should fix. It shouldn't happen for release updates very often, slightly more chance when updating from the /dev/ path as that's sometimes updated several times a day.

1