Opened at 2021-07-02T17:37:35Z

Closed at 2021-08-04T17:44:40Z

#3743 closed defect (fixed)

Integration tests for i2p, since it's unclear if it actually works

Reported by: itamarst Owned by: itamarst
Priority: normal Milestone: Support Python 3
Component: unknown Version: n/a
Keywords: Cc:
Launchpad Bug:

Description

It's unclear if I2P support works without better automated testing. It seems like the way I2P works is:

  1. You install a router.
  2. The router talks to reseed server, to find some initial peers.
  3. After that it's a peer-to-peer network.

Setting up a router _without_ any reseed servers would hopefully allow for integration testing with local I2P network, since the router would know about the address of things using it to listen. Probably.

Change History (2)

comment:1 Changed at 2021-07-02T18:11:20Z by itamarst

Apparently i2pd might be easier to setup than the Java one, e.g there's a purple2ip/i2pd Docker image that's only 10MB. You can specify reseed urls, and which routers to trust. Setting both those to empty list should prevent talking to anyone else. Maybe.

comment:2 Changed at 2021-08-04T17:44:40Z by GitHub <noreply@…>

  • Resolution set to fixed
  • Status changed from new to closed

In 93fbfb61/trunk:

Merge pull request #1097 from tahoe-lafs/3743.i2p-integration-tests

i2p integration tests

Fixes ticket:3743

Note: See TracTickets for help on using tickets.