-onion does not default to -proxy #14722

1. 
   qubenix commented at 9:29 pm on November 13, 2018: contributor

   According to help menu:

   -onion=ip:port Use separate SOCKS5 proxy to reach peers via Tor hidden services, set -noonion to disable (default: -proxy)

   I would expect that if -proxy is set, but -onion is not, -proxy setting would be used for onion connections.

   Instead, according to getnetworkinfo, the default Tor port (127.0.0.1:9050) is listed for onion, but ipv{4,6} both have the -proxy setting. I inspected the traffic and saw that indeed it is not honoring my -proxy setting.

   Bitcoin Core Daemon version v0.17.0.1-9e87d82e7

   OS: Qubes OS, Whonix 14 VM

2. fanquake added the label P2P on Nov 13, 2018
3. 
   laanwj commented at 12:05 pm on November 14, 2018: member

   This is really strange. I have a hard time thinking of where that proxy even comes from. I think tor control might be erroneously overriding the proxy. Can you try running with -listenonion=0?
4. 
   qubenix commented at 2:57 pm on November 14, 2018: contributor

   listenonion=0 does use my custom proxy setting for onions.

   It would be interesting to me if Tor control was to blame as I just recently created Whonix’s onion-grater profile for bitcoind.

   Here is the comms with Whonix’s control port:

   0PROTOCOLINFO 1
   1250-PROTOCOLINFO 1
   2250-AUTH METHODS=NULL
   3250-VERSION Tor="0.3.4.8 (git-5da0e95e4871a0a1)"
   4250 OK
   5AUTHENTICATE
   6250 OK
   7ADD_ONION NEW:RSA1024 Port=18333,127.0.0.1:18333
   8250-ServiceID=hzyiu6fm6rdkifa7
   9250 OK
   

5. qubenix referenced this in commit 1e7013fa6e on Nov 14, 2018
6. 
   qubenix commented at 3:59 pm on November 14, 2018: contributor

   I just found this:

   https://github.com/bitcoin/bitcoin/blob/2e8f9dc2bbb1200218feaf80344d35dca1cd6b25/src/torcontrol.cpp#L525-L532

7. qubenix referenced this in commit f7cfb6f015 on Nov 15, 2018
8. qubenix referenced this in commit 3474736b8c on Nov 15, 2018
9. qubenix referenced this in commit 38640a021a on Nov 15, 2018
10. 
    roshii commented at 6:51 pm on September 25, 2019: none

    For the record, I do face similar issue running v0.18.1 and as described in https://github.com/bitcoin/bitcoin/pull/16940
11. 
    nyxnor commented at 11:13 pm on October 2, 2022: none

    Also using Whonix. I believe this was solved. From -getinfo or getnetworkinfo I see the proxies set correctly to the different networks.
12. fanquake closed this on Oct 3, 2022

    ---

13. bitcoin locked this on Oct 3, 2023

Contributors
qubenix laanwj roshii nyxnor

Labels
P2P