Inconsistent Reseeding Across Systems & I2CP Streaming Issues (i2p‑core 2.7.0)

I2P router issues
Post Reply
Vin
Posts: 1
Joined: 15 Jul 2025 16:49

Inconsistent Reseeding Across Systems & I2CP Streaming Issues (i2p‑core 2.7.0)

Post by Vin »

Hello,

I’m running an embedded I2P router (i2p‑core 2.7.0, i2p‑streaming 2.7.0, i2p‑router 2.7.0) and seeing two separate issues. The code snippet is at https://github.com/Vin-Nan/I2p, and I’ve attached the Java classes and router.config for reference.
  • Inconsistent Reseeding Across Systems
    Problem: on some hosts the router stalls or fails to fetch router infos during reseed. The .cer and .sig files are identical to those from a standalone router(I2P-2.9.0) and checksum‑verified.
    Logs (example):

    Code: Select all

    Reseeding from https://i2p.ghativega.in/i2pseeds.su3?netid=2
    Error reseeding: java.io.IOException: unknown signer: arnavbhatt288@mail.i2p for content type: reseed
    Reseed got no router infos from https://i2p.ghativega.in/i2pseeds.su3?netid=2
    Reseed got 0 router infos from https://i2p.ghativega.in/i2pseeds.su3?netid=2 with 1 errors
    Reseeding from https://i2pseed.creativecowpat.net:8443/i2pseeds.su3?netid=2
    Reseed got no router infos from https://i2pseed.creativecowpat.net:8443/i2pseeds.su3?netid=2
    …
    Reseeding from https://reseed.diva.exchange/i2pseeds.su3?netid=2
    Reseed got no router infos from https://reseed.diva.exchange/i2pseeds.su3?netid=2
    Reseed got 0 router infos from https://reseed.diva.exchange/i2pseeds.su3?netid=2 with 1 errors
    Reseed failed – check network connection
    
    I’ve added the EmbeddedRouter class,SysSettings (which handles path and directory creation), and the router.config file in the repo here https://github.com/Vin-Nan/I2p . I’d appreciate your feedback on these components and any suggestions for troubleshooting or improving the reseeding process.
  • Intermittent Delays & Connection Failures via I2CP Streaming API

    On systems where the embedded router works, I’ve encountered some issues:
    • Message delivery is occasionally delayed; RTT goes up to 35 seconds or more.
    • NoRouteToHostException occurs even when the peer is reachable.
    • Connections sometimes fail to establish or close unexpectedly.
    To keep the connection alive, I have scheduled a keepAlive task executor which pings every 90 sec over the connection.
    I’m using I2CP with the Streaming API for HTTP‑like communication via client/server sockets. I’ve also added the I2pClient.java class in the repo—please let me know if you spot anything that needs fixing or can suggest best practices when working with the I2P APIs.
All components are on version 2.7.0:
  • net.i2p:i2p
  • net.i2p.client:streaming
  • net.i2p:router
This is also the latest stable release of I2P’s ministreaming.

Thanks in advance for any pointers or suggestions.
Post Reply