Update tor.md #8415

pull ad90df8e708e8fa8153e56a059 wants to merge 1 commits into bitcoin:master from ad90df8e708e8fa8153e56a059:patch-1 changing 1 files +17 −3

ad90df8e708e8fa8153e56a059 commented at 4:42 AM on July 28, 2016: none

Added description of the "onlynet=onion", "proxyrandomize", and "bind=127.0.0.1" options for Tor only nodes.

Update tor.md

Added description of the "onlynet=onion" and "bind=127.0.0.1" options for Tor only nodes.

3776d60c27

in doc/tor.md:None in 3776d60c27

  81 | +			through a proxy.
  82 | +
  83 |  In a typical situation, where you're only reachable via Tor, this should suffice:
  84 |  
  85 | -	./bitcoind -proxy=127.0.0.1:9050 -externalip=57qr3yd1nyntf5k.onion -listen
  86 | +	./bitcoind -proxy=127.0.0.1:9050 -externalip=57qr3yd1nyntf5k.onion

ad90df8e708e8fa8153e56a059 commented at 5:03 AM on July 28, 2016:

Accidentally removed -listen

jonasschnelli added the label Docs and Output on Jul 28, 2016
in doc/tor.md:None in 3776d60c27
```
  99 | @@ -86,7 +100,7 @@ and open port 8333 on your firewall (or use -upnp).
 100 |  If you only want to use Tor to reach onion addresses, but not use it as a proxy
 101 |  for normal IPv4/IPv6 communication, use:
 102 |  
 103 | -	./bitcoin -onion=127.0.0.1:9050 -externalip=57qr3yd1nyntf5k.onion -discover
 104 | +	./bitcoin -onion=127.0.0.1:9050 -externalip=57qr3yd1nyntf5k.onion -discover -listen -onlynet=onion -bind=127.0.0.1
```
laanwj commented at 7:53 AM on July 28, 2016:

I think there is a slight misunderstanding here. There are two different cases:

Want to be able to connect to .onion peers, but normal IPv4/IPv6 connections go through plainnet

Want to be able to connect to .onion peers only

You change this from (1) to (2), but both are valid use cases, and I think if you make this change you should describe both.
laanwj commented at 8:03 AM on July 28, 2016:

Also for (2) I personally prefer:

./bitcoin -proxy=127.0.0.1:9050 -externalip=57qr3yd1nyntf5k.onion -discover -listen -onlynet=onion -bind=127.0.0.1

This has the same effect, but in the case that there is a bug causing bitcoind to ignore onlynet and try to connect to IPv4/IPv6 anyway, at least it will go through Tor.
ad90df8e708e8fa8153e56a059 commented at 8:11 AM on July 28, 2016: none

Yes, I agree there are definitely 2 distinct use cases. I'll tweak my changes and add a section to make that more clear.
ad90df8e708e8fa8153e56a059 closed this on Jul 28, 2016
DrahtBot locked this on Sep 8, 2021

Contributors

ad90df8e708e8fa8153e56a059

laanwj

Labels

Docs