|
|
@ -96,38 +96,6 @@ random, one-time, transient I2P addresses for itself for outbound connections |
|
|
to make it harder to discriminate, fingerprint or analyze it based on its I2P |
|
|
to make it harder to discriminate, fingerprint or analyze it based on its I2P |
|
|
address. |
|
|
address. |
|
|
|
|
|
|
|
|
## Additional configuration options related to I2P |
|
|
|
|
|
|
|
|
|
|
|
``` |
|
|
|
|
|
-debug=i2p |
|
|
|
|
|
``` |
|
|
|
|
|
|
|
|
|
|
|
Set the `debug=i2p` config logging option to see additional information in the |
|
|
|
|
|
debug log about your I2P configuration and connections. Run `hush-cli help |
|
|
|
|
|
logging` for more information. |
|
|
|
|
|
|
|
|
|
|
|
``` |
|
|
|
|
|
-onlynet=i2p |
|
|
|
|
|
``` |
|
|
|
|
|
|
|
|
|
|
|
Make automatic outbound connections only to I2P addresses. Inbound and manual |
|
|
|
|
|
connections are not affected by this option. It can be specified multiple times |
|
|
|
|
|
to allow multiple networks, e.g. onlynet=onion, onlynet=i2p. |
|
|
|
|
|
|
|
|
|
|
|
I2P support was added to Hush in version 3.9.3 and there may be fewer I2P |
|
|
|
|
|
peers than Tor or IP ones. Therefore, using I2P alone without other networks may |
|
|
|
|
|
make a node more susceptible to [Sybil |
|
|
|
|
|
attacks](https://en.bitcoin.it/wiki/Weaknesses#Sybil_attack). You can use |
|
|
|
|
|
`hush-cli -addrinfo` to see the number of I2P addresses known to your node. |
|
|
|
|
|
|
|
|
|
|
|
Another consideration with `onlynet=i2p` is that the initial blocks download |
|
|
|
|
|
phase when syncing up a new node can be very slow. This phase can be sped up by |
|
|
|
|
|
using other networks, for instance `onlynet=onion`, at the same time. |
|
|
|
|
|
|
|
|
|
|
|
In general, a node can be run with both onion and I2P hidden services (or |
|
|
|
|
|
any/all of IPv4/IPv6/onion/I2P/CJDNS), which can provide a potential fallback if |
|
|
|
|
|
one of the networks has issues. |
|
|
|
|
|
|
|
|
|
|
|
## I2P-related information |
|
|
## I2P-related information |
|
|
|
|
|
|
|
|
There are several ways to see your I2P address if accepting |
|
|
There are several ways to see your I2P address if accepting |
|
|
@ -135,6 +103,7 @@ incoming I2P connections (`-i2pacceptincoming`): |
|
|
- in the "Local addresses" output of CLI `-netinfo` |
|
|
- in the "Local addresses" output of CLI `-netinfo` |
|
|
- in the "localaddresses" output of RPC `getnetworkinfo` |
|
|
- in the "localaddresses" output of RPC `getnetworkinfo` |
|
|
- in the debug log (grep for `AddLocal`; the I2P address ends in `.b32.i2p`) |
|
|
- in the debug log (grep for `AddLocal`; the I2P address ends in `.b32.i2p`) |
|
|
|
|
|
- in the i2p/i2pd web console under "SAM Sessions" |
|
|
|
|
|
|
|
|
To see which I2P peers your node is connected to, use `hush-cli -netinfo 4` |
|
|
To see which I2P peers your node is connected to, use `hush-cli -netinfo 4` |
|
|
or the `getpeerinfo` RPC (e.g. `hush-cli getpeerinfo`). |
|
|
or the `getpeerinfo` RPC (e.g. `hush-cli getpeerinfo`). |
|
|
|
