DragonX/hush3
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Removed RPCs we do not have from TOR, i2p, and CJDNS docs

Browse Source
This commit is contained in:
jahway603
2025-02-26 23:42:31 -05:00
parent ca8711f50c
commit babb4a39c2
3 changed files with 3 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
doc/cjdns.md
View File

@@ -106,10 +106,7 @@ details.
## CJDNS-related information in Hush ## CJDNS-related information in Hush
There are several ways to see your CJDNS address in Hush: There are several ways to see your CJDNS address in Hush:
- in the "Local addresses" output of CLI `-netinfo`
- in the "localaddresses" output of RPC `getnetworkinfo` - in the "localaddresses" output of RPC `getnetworkinfo`
To see which CJDNS peers your node is connected to, use `hush-cli -netinfo 4` To see which CJDNS peers your node is connected to, use `hush-cli getpeerinfo`
or the `getpeerinfo` RPC (i.e. `hush-cli getpeerinfo`). RPC.
You can use the `getnodeaddresses` RPC to fetch a number of CJDNS peers known to your node; run `hush-cli help getnodeaddresses` for details.

6
doc/i2p.md
View File

@@ -100,15 +100,11 @@ address.
There are several ways to see your I2P address if accepting There are several ways to see your I2P address if accepting
incoming I2P connections (`-i2pacceptincoming`): incoming I2P connections (`-i2pacceptincoming`):
- 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" - 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 getpeerinfo`
or the `getpeerinfo` RPC (e.g. `hush-cli getpeerinfo`).
To see which I2P addresses your node knows, use the `getnodeaddresses 0 i2p`
RPC. RPC.
## Compatibility ## Compatibility

4
doc/tor.md
View File

@@ -16,7 +16,6 @@ configure Tor.
## How to see information about your Tor configuration via Hush ## How to see information about your Tor configuration via Hush
There are several ways to see your local onion address in Hush: There are several ways to see your local onion address in Hush:
- 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 Tor address ends in `.onion`) - in the debug log (grep for "AddLocal"; the Tor address ends in `.onion`)
@@ -27,9 +26,6 @@ CLI `-addrinfo` returns the number of addresses known to your node per
network. This can be useful to see how many onion peers your node knows, network. This can be useful to see how many onion peers your node knows,
e.g. for `-onlynet=onion`. e.g. for `-onlynet=onion`.
To fetch a number of onion addresses that your node knows, for example seven
addresses, use the `getnodeaddresses 7 onion` RPC.
## 1. Run Hush behind a Tor proxy ## 1. Run Hush behind a Tor proxy
The first step is running Hush behind a Tor proxy. This will already anonymize all The first step is running Hush behind a Tor proxy. This will already anonymize all