i2p connectivity ordering problem for storage nodes #2858

New Issue

tahoe-lafs · 2016-12-29T19:42:04Z

dawuud commented

2016-12-29 19:42:04 +00:00

str4d reports:
tldr; because client connections were made before the server tub was started, the I2P session for the process was started with transient keys instead of the keypair for the server. This meant that the server tub was listening on a transient Destination that did not match the advertised tub.location.

str4d reports: tldr; because client connections were made before the server tub was started, the I2P session for the process was started with transient keys instead of the keypair for the server. This meant that the server tub was listening on a transient Destination that did not match the advertised tub.location.

tahoe-lafs added the

labels 2016-12-29 19:42:04 +00:00

tahoe-lafs added this to the undecided milestone 2016-12-29 19:42:04 +00:00

warner commented

2016-12-29 20:11:44 +00:00

hm, it sounds like the order of startService is important.. maybe to make this work, we need the Tub to be started earlier than anything which might queue a call to getReference.

hm, it sounds like the order of `startService` is important.. maybe to make this work, we need the Tub to be started earlier than anything which might queue a call to `getReference`.

warner added

code-network

and removed

unknown

labels 2016-12-29 20:17:19 +00:00

warner modified the milestone from undecided to 1.12.1

2016-12-29 20:17:19 +00:00

tahoe-lafs added

major

and removed

normal

labels 2017-01-10 17:11:35 +00:00

warner commented

2017-01-17 16:42:32 +00:00

Will this be fixed by the changes in https://github.com/tahoe-lafs/tahoe-lafs/pull/394 ?

Will this be fixed by the changes in <https://github.com/tahoe-lafs/tahoe-lafs/pull/394> ?

Brian Warner <warner@lothar.com> commented

2017-01-18 01:14:21 +00:00

In 998af5c/trunk:

Pass I2P keyfile to foolscap

If no session management is performed, txi2p starts a process-wide session the
first time a connection (client or server) is opened; all subsequent connections
use that session and its configuration properties.

This commit ensures that the same properties are passed to both client and
server endpoints, so that the correct I2P Destination is started regardless of
whether the first connection made by Tahoe-LAFS is for a client or server.

Closes #2858.

In [998af5c/trunk](/tahoe-lafs/trac-2024-07-25/commit/998af5c26ee92cdf8c9b67546c85c296c418685c): ``` Pass I2P keyfile to foolscap If no session management is performed, txi2p starts a process-wide session the first time a connection (client or server) is opened; all subsequent connections use that session and its configuration properties. This commit ensures that the same properties are passed to both client and server endpoints, so that the correct I2P Destination is started regardless of whether the first connection made by Tahoe-LAFS is for a client or server. Closes #2858. ```

tahoe-lafs added the

fixed

label 2017-01-18 01:14:21 +00:00

tahoe-lafs closed this issue

2017-01-18 01:14:21 +00:00

Sign in to join this conversation.