diff options
author | Jon Atack <jon@atack.com> | 2020-09-16 08:43:26 +0200 |
---|---|---|
committer | Jon Atack <jon@atack.com> | 2020-12-16 22:58:14 +0100 |
commit | a34eceb4cc054b4233e7321de927e8a7a2146301 (patch) | |
tree | f7f631fe5c3b658c6c5dd557e7b7af6e864a9c4e | |
parent | dc8a591222f249da81c7eef8aa5961f8d7dd1e23 (diff) | |
download | bitcoin-a34eceb4cc054b4233e7321de927e8a7a2146301.tar.xz |
doc: update -externalip documentation in tor.md
-rw-r--r-- | doc/tor.md | 13 |
1 files changed, 9 insertions, 4 deletions
diff --git a/doc/tor.md b/doc/tor.md index ccf8a226ee..34c5f1b5e7 100644 --- a/doc/tor.md +++ b/doc/tor.md @@ -62,14 +62,19 @@ The directory can be different of course, but virtual port numbers should be equ your bitcoind's P2P listen port (8333 by default), and target addresses and ports should be equal to binding address and port for inbound Tor connections (127.0.0.1:8334 by default). - -externalip=X You can tell bitcoin about its publicly reachable address using - this option, and this can be a .onion address. Given the above - configuration, you can find your .onion address in + -externalip=X You can tell bitcoin about its publicly reachable addresses using + this option, and this can be an onion address. Given the above + configuration, you can find your onion address in /var/lib/tor/bitcoin-service/hostname. For connections coming from unroutable addresses (such as 127.0.0.1, where the - Tor proxy typically runs), .onion addresses are given + Tor proxy typically runs), onion addresses are given preference for your node to advertise itself with. + You can set multiple local addresses with -externalip. The + one that will be rumoured to a particular peer is the most + compatible one and also using heuristics, e.g. the address + with the most incoming connections, etc. + -listen You'll need to enable listening for incoming connections, as this is off by default behind a proxy. |