client can't connect to introducer via i2p

[Brian Warner]

On 8/31/16 3:10 AM, Vladislav wrote:
> I add 'i2p' : introducer.furl = pb://i2p:557brm5u7uqoamuaf.......... -
> same result

Oops, that's the wrong place for it. Connection-hint types need to go on
the connection-hint, not the TubID.

The first base32 string (right after "pb://", the one that starts with
"557.." in your FURL) is the Foolscap TubID. The TubID is a hash of the
server's expected TLS certificate.

The connection hint is the second (longer) big base32 string, "wlhw.."
in your example, that comes *after* the "@" sign. The connection-hint is
what needs the "i2p:" prefix. My example should have it in the right
place:

>>> [client]
>>> introducer.furl =
>>> pb://557brm5u7uqoamuafn54l7kgega22dp5@i2p:wlhwbsf4njp3mo4pcjavpdu76tdevs3r6h2gn5qpakvozuuolptq.b32.i2p/llchk6qaudgjm3zpz2tmht6zxmlflbrh
         ^- not here (tubid)              ^- yes here (connection hint)

(also, once you get everything running, you might want to move the
introducer to a new address, since this one is now plastered all over
the internet :-)

cheers,
 -Brian