aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJon Atack <jon@atack.com>2020-09-16 08:43:26 +0200
committerMarcoFalke <falke.marco@gmail.com>2020-12-17 12:29:23 +0100
commite70ccb0bc4b695cd331aeda6d7aa405fa6d8f2e7 (patch)
tree91a0af940ecb7fe2576e5ee7b6152135b2df90df /doc
parent2c8482d0a279d07a814eaaae231c90d3d2058e55 (diff)
doc: update -externalip documentation in tor.md
Github-Pull: #19961 Rebased-From: a34eceb4cc054b4233e7321de927e8a7a2146301
Diffstat (limited to 'doc')
-rw-r--r--doc/tor.md13
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.