So, I just set up Bitcoin Core on my Windows 11 Pro machine. Man, it took like a day and a half to sync all the blocks. Now, my Bitcoin folder is sitting at 608GB. I’m connected to 10 peers and it looks like there’s a ton of data being sent and received. Just grabbed the command line guide, gonna check it out later tonight.
Here's my question: I see that I'm getting 10 outbound connections but no inbound ones. Is it necessary for the network to have inbound connections to my computer? I've got an allow rule in Bitdefender for both inbound and outbound traffic for Bitcoin-qt.exe. Shouldn't there be some inbound connections happening?
Thanks for the help!
Mike
If your node connects to my node, they will be exchanging data.
If your nodes initiates the connection to my node, then this connection will be incoming for me and outgoing for you.
After the connection is established, it doesn't matter who initiated it. Data exchange between our nodes will be established and it will be working as expected.
If you want to be able to accept incoming connections, then you can do 2 things:
1. You can open a port on your router to allow incoming connections.
2. You can set up TOR and this will allow you to accept incoming connections without messing up with port forwarding.
Finally, I repeat that since you already have the connections established, you can just ignore the fact that they are outgoing, since you are already participating to the network properly and without any issues.
Allowing incoming connection you are permitting peers to send the request to your node to establish connections with it (default port is 8333) . If you allow solely outbound connections then you node initiate connections with other nodes the setting of which allow them to accept the inbound connections.
You might want to check this page, which list most/all possible configuration for Bitcoin Core, https://jlopp.github.io/bitcoin-core-config-generator.
Using VPN which allow port forwarding also works, although these days it's hard to find VPN which offer that feature due to many abuse.
So, you've got 10 outbound connections, which means your Bitcoin client is actively connecting to other nodes on the network to send and receive data. These outbound connections are crucial for your client to stay updated with the latest blockchain information and to broadcast your transactions to the network. Now, regarding the inbound connections, don't fret if you're seeing a big fat zero there. While it's nice to have inbound connections, they're not essential for your client to function properly. Inbound connections would allow other nodes to directly connect to your client, which can be beneficial for decentralization and network efficiency, but it's not a deal-breaker if you don't have any.
Let me share a quick story from my own Bitcoin journey. When I first started tinkering with Bitcoin nodes, I encountered a similar situation with my connections. I spent hours tweaking firewall settings, wondering why I wasn't seeing any inbound connections. Eventually, I realized that as long as my outbound connections were solid, my client was doing its job just fine. So, if everything seems to be running smoothly on your end and you're not experiencing any issues with transactions or syncing, you're probably good to go!
Okay, thanks all. Seems I'm okay for now. It was just that blurb in the installation instructions that said I needed to allow an incoming connection. Maybe time to rephrase that?