using onlynet=tor with bitcoind

4 replies 180 views
tom2011Member
Posts: 1 · Reputation: 84
#1May 9, 2017, 02:23 PM
got a couple of questions about running bitcoind with this option. from what I read, this setting makes the node connect only through .onion addresses, which is exactly what I want. no normal internet connections at all. first off, how does bitcoind find other nodes to connect to? I saw something about fallback nodes in the wiki, but couldn't find anything in the source code. since bitcoin usually relies on IPs and tor doesn't work that way, how’s that managed? second question: I noticed something on my node: is this happening because the server where bitcoind and tor are running has dualstack? if that’s the case, shouldn’t onlynet prevent those connections? edit: I was pointed to the ipv6 address translation for onion addresses (regarding question 1), and about question 2: looks like onlynet just affects outgoing connections.
4 Reply Quote Share
GigaLaserFull Member
Posts: 59 · Reputation: 458
#2May 9, 2017, 03:54 PM
I did try tor run bitcoind 0.8.6 with the following bitcoin.conf And Port 8333 is blocked by firewall. But that resulted in no connections to Bitcoin network. Is an Onion address seed missing? I added the line addnode=bpdlwholl7rnkrkw.onion to the above config (address from https://en.bitcoin.it/wiki/Fallback_Nodes), and then it got working- 40 connections after some hours. Is this Onion address seed needed? Now, if I remove the addnode line and restart bitcoind, it gets connections again very fast. I guess that is because the Onion address of my node is propagated in the network. But what happens, if I shutdwon the node for maybe a week and start it again without the addnode line ? @fronti would be nice if You could explain a little bit more of You have been pointed to and tell the sources. I am missing some information about Onion node discovery and seeding on https://en.bitcoin.it/wiki/Satoshi_Client_Node_Discovery
1 Reply Quote Share
alpha_maxiFull Member
Posts: 42 · Reputation: 286
#3May 9, 2017, 10:01 PM
Try this (this works for me with 0.10.0): onion=127.0.0.1:9150 #proxy=127.0.0.1:9150 bind=127.0.0.1:8333 This discussion has some good info on how bitcoin does discovery through Tor: https://bitcointalk.org/index.php?topic=989920.0
4 Reply Quote Share
calmwhaleMember
Posts: 3 · Reputation: 135
#4May 10, 2017, 12:53 AM
Hello. I'm looking for precisely the opposite for this: "onlynet=onion" Any suggestions? How to block connections to TOR nodes and only accept other nodes? Can I configure it through the Bitcoin Core Console, in the bitcoin.conf? Thank you!
1 Reply Quote Share
gr3g.0rbitHero Member
Posts: 1025 · Reputation: 2646
#5May 10, 2017, 04:54 AM
You may set onion=0 and listenonion=0 to your bitcoin.conf file or use -noonion and -listenonion=0 as command line args to prevent both incoming and outgoing Tor connections. But although it's on-topic, it would be better if you've opened a new topic in Bitcoin Technical Support board since this thread is 9 years old. If there's any additional questions, go through the link to get to that board and click the small "new topic" button at the right, near "search".
3 Reply Quote Share

Related topics