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

Closed
opened 2021-07-02 17:37:35 +00:00 by itamarst · 2 comments

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.

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.
itamarst added the
unknown
normal
defect
n/a
labels 2021-07-02 17:37:35 +00:00
itamarst added this to the Support Python 3 milestone 2021-07-02 17:37:35 +00:00
itamarst self-assigned this 2021-07-02 17:37:35 +00:00
Author

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.

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.
GitHub <noreply@github.com> commented 2021-08-04 17:44:40 +00:00
Owner

In 93fbfb61/trunk:

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

i2p integration tests

Fixes ticket:3743
In [93fbfb61/trunk](/tahoe-lafs/trac-2024-07-25/commit/93fbfb61a8335428ad97d592842a5db78d26e30e): ``` Merge pull request #1097 from tahoe-lafs/3743.i2p-integration-tests i2p integration tests Fixes ticket:3743 ```
tahoe-lafs added the
fixed
label 2021-08-04 17:44:40 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#3743
No description provided.