Bitcoin node over TOR

[vinshet]

I set up my bitcoin node to run over tor with the following in the config file
# Core
conf=<some_path>/.bitcoin/bitcoin.conf
server=1
daemon=1
prune=23552
maxconnections=1000

# TOR
proxy=127.0.0.1:9050
listenonion=1
listen=1
onlynet=onion

#RPC
rpcuser=username
rpcpassword=password

Question 1 :
I see some inbound connections that have IPv4 addresses. These IPv4 addresses do not show up on bitnodes, so I am a bit curious as to what these addresses are.

Question 2:
Is my node running both on IP and TOR?

Question 3:
If I understand correctly when running a node on TOR, DNS seeders are not utilized and it defaults to the harcoded list of .onion addresses. My first outbound peer was not in the list of addresses in the file. Where could this have come from?

Question 4:
I have what is the difference between onion and not_publicly_routable  in the network fields ?

[1714043588]

1714043588

[1714043588]

1714043588

[1714043588]

1714043588

[1714043588]

1714043588

[1714043588]

1714043588

[1714043588]

1714043588

[BlackHatCoiner]

Question 1 :
I see some inbound connections that have IPv4 addresses. These IPv4 addresses do not show up on bitnodes, so I am a bit curious as to what these addresses are.

As said in your other thread,

Due to decentralization, it's possible for few nodes to not be crawled by bitnodes

Question 2:
Is my node running both on IP and TOR?

It's weird that you have both IPv4 and Tor connections. Do the IPv4 allow incoming connections? Try setting listen=0.

Question 3:
If I understand correctly when running a node on TOR, DNS seeders are not utilized and it defaults to the harcoded list of .onion addresses. My first outbound peer was not in the list of addresses in the file. Where could this have come from?

Bitcoin Core contains some IP addresses by default, so this is one guess.

[vinshet]

It's weird that you have both IPv4 and Tor connections. Do the IPv4 allow incoming connections? Try setting listen=0.

Error: Cannot set -listen=0 together with -listenonion=1

[BlackHatCoiner]

Which IPv4 addresses show up? It's weird, I have similar configuration with yours, but I only connect with onion addresses.

[ranochigo]

I see some inbound connections that have IPv4 addresses. These IPv4 addresses do not show up on bitnodes, so I am a bit curious as to what these addresses are.

Likely node that do not accept incoming connections. They do not show up on bitnodes because bitnodes cannot connect to them through the crawlers. Can also be due to the other reasons I outlined in the other thread as well.

Is my node running both on IP and TOR?

You are only connecting to onion addresses through the proxy because you specified oniononly. However, the reason why you're seeing IPV4 nodes is because you didn't bind your node to your Tor instance. As such, peers are still able to connect to you because you are still listening on your local IPV4 address. To prevent this, add bind=127.0.0.1.

If I understand correctly when running a node on TOR, DNS seeders are not utilized and it defaults to the harcoded list of .onion addresses. My first outbound peer was not in the list of addresses in the file. Where could this have come from?

Connections do not necessarily have to be maintained after connections. The primary and intended purpose of your seeds is to establish an initial point of contact to the network and your peers will populate and allow you to connect and get to know other peers.

[vv181]

If I understand correctly when running a node on TOR, DNS seeders are not utilized and it defaults to the harcoded list of .onion addresses.~

AFAIK, the node won't fetch any DNS seed only if you set up a config to disable it. Even if the node is running over Tor, it still fetches the DNS seeders, but the Tor exit nodes will resolve the DNS for the Bitcoin node.

I have what is the difference between onion and not_publicly_routable  in the network fields ?

Onion means, the in/outbound connection is using the Tor network. The other one may come from a local P2P connection, as an example, if you are running Electrs, the electrs connection will result not_publicly_routable. Other than that, it just means that the connection/network isn't routable over the internet.

[bobdole01]

I don't know if you ever found the solution for this but for anyone else with this issue -onlynet=onion is what you likely need..  Everything else didn't work for me.

[Cricktor]

For my Tor-only node I have the following lines related to network connectivity in my bitcoin.conf file:

Code:

...
server=1
daemon=1
daemonwait=1

# Network
#listen=1
listenonion=1
proxy=127.0.0.1:9050
bind=127.0.0.1
onlynet=onion
...

With bitcoin-cli getnetworkinfo the only reachable network is "onion", all other networks are

Code:

...
      "limited": true,
      "reachable": false,
...

Works for me...