pull down to refresh

218 sats \ 2 replies \ @ek 1 Jan \ parent \ on: How long to get peers over Tor? bitcoin
but I don't know how the peer discovery protocol actually works
Afaik, peers are gossiped around using the addr message, see protocol documentation. This means they'll tell others nodes which nodes they are aware of.
Except bitcoin nodes want port 8333, so I need to get peer nodes to know about whatever port that Proton assigned to me, and have them use that to communicate with me.
I think you are looking for the config option -externalip=<ip>:<port>. It changes the advertised IP address and port. But it might be that nodes prefer connecting to port 8333, at least that I read about that a long time ago. Not sure if still the case.
So in theory, you should be able to set that to the IP address that you have when you're connected to the VPN and curl curl -4 ip.me and to the port Proton assigned to you.
If you use -externalip=<ip>:<port>, -listen=1 and your port forwarding works, you should get incoming connections at some point.
Btw, I created a post in the bitcointalk forum when I did what you're trying to do, maybe the config I posted there helps. But that I am using -discover=1 together with -externalip looks wrong to me now 🤔
edit: found the PR that changed the strong preference to connect to port 8333: https://github.com/bitcoin/bitcoin/pull/23542. so non-default ports should be okay now.
and here's a config generator that might be useful, too: https://jlopp.github.io/bitcoin-core-config-generator
write
preview
218 sats \ 1 reply \ @ek 1 Jan
So in theory, you should be able to set that to the IP address that you have when you're connected to the VPN and curl curl -4 ip.me and to the port Proton assigned to you.
Edit timer ran out before I could fix this sentence. Sentence in proper English:
So in theory, you should be able to set that to the IP address that you have when you're connected to the VPN (you can use curl -4 ip.me for that) and to the port Proton assigned to you.
and here:
you should get incoming connections at some point.
I meant specifically inbound IPv4 connections since I assume that's all we're talking about. You have no problems with inbound connections on Tor, right?
I just found in jlopp's config generator under networking that there is -natpmp. I have no experience with NAT-PMP but sounds like it could be useful for your case.
So maybe a network configuration like this could work (replace IP address with the one from Proton)?
# [network]
# Accept incoming connections from peers.
listen=1
# Specify your own public IP address.
externalip=185.159.159.140
# Use NAT-PMP to map the listening port.
natpmp=1
reply
33 sats \ 0 replies \ @elvismercury OP 1 Jan
These are so helpful, @ek, thank you! I'll let you know how it goes.
reply