bitcoind onlynet=tor | Bitcointalksearch.org

nc50lc

legendary

Activity: 2534

Merit: 6080

Self-proclaimed Genius

Quote from: RodMor on April 04, 2024, 12:56:07 PM

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?

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".

RodMor

newbie

Activity: 3

Merit: 0

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!

cr1776

legendary

Activity: 4214

Merit: 1313

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://bitcointalksearch.org/topic/how-does-the-protocol-broadcast-hidden-services-989920

5cMXezpBtm

full member

Activity: 233

Merit: 100

I did try tor run bitcoind 0.8.6 with the following bitcoin.conf

Code:

upnp=0
debug=0
shrinkdebugfile=1
proxy=127.0.0.1:9050
externalip=xxxxxx.onion
listen=1
onlynet=tor

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

fronti

legendary

Activity: 2912

Merit: 1309

just a few questions if I run a bitcoind with the

Code:

onlynet=tor

option
I understand from the description that this option only use .onion which is what I want. No connection to normal net.

- how do the bitcoind discover other nodes it is connected too
  i see in the wiki that there are some fallback nodes, but did not find in the source.
  as bitcoin normaly relay on ip addresses and tor not, how this is handled?

- then second question:
  i noticed this on my node:

Code:

bitcoin-cli getpeerinfo
....
   "addr" : "[2a01:4f8:210:5046::2]:40394",
   "addrlocal" : "XXXX.onion:8333",
   "services" : "00000000",
   "lastsend" : 1423857231,
...

is this because the server bitcoind and tor run has dualstack?
If yes, shouldn't onlynet block such connections?

Edit.
in the meantime i was pointed to the ipv6 address translation for the onion addresses (question 1)
and question 2: onlynet ony affect outgoing connections...

Topic: bitcoind onlynet=tor (Read 1988 times)