Bitcoin Forum

Bitcoin => Development & Technical Discussion => Topic started by: GodlyWizard on April 14, 2018, 05:14:49 PM



Title: getconnectioncount
Post by: GodlyWizard on April 14, 2018, 05:14:49 PM
Code:
bitcoin-cli getconnectioncount
Gives me an amount of 86 connections, my node has been running for a couple of months with 100% uptime. educational purposes

Is this a high number of connections? How many does your node have?
I would also like to know if your node is visible on https://bitnodes.earn.com/ or not, mine shows up there around 9/10 times I check.

The same site also says:

Quote
The crawler maintained by Bitnodes connects from these IP addresses: 136.243.139.96, 136.243.139.120, 2a01:4f8:212:3b1f::2

Are these IP addresses usable with the
Code:
-addnode=<ip>
configuration?


Title: Re: getconnectioncount
Post by: starmyc on April 14, 2018, 07:23:41 PM
Code:
bitcoin-cli getconnectioncount
Gives me an amount of 86 connections, my node has been running for a couple of months with 100% uptime. educational purposes

Is this a high number of connections? How many does your node have?

86 connections is an OK number. By default, bitcoind limits the connection count to 125 (source (https://en.bitcoin.it/wiki/Running_Bitcoin)). You can change that limit.

Mine:

Code:
$ bin/bitcoin/bin/bitcoin-cli getconnectioncount
117


I would also like to know if your node is visible on https://bitnodes.earn.com/ or not, mine shows up there around 9/10 times I check.

Yes.

The same site also says:

Quote
The crawler maintained by Bitnodes connects from these IP addresses: 136.243.139.96, 136.243.139.120, 2a01:4f8:212:3b1f::2

Are these IP addresses usable with the
Code:
-addnode=<ip>
configuration?

Well, the 8333 port is open, but I think this must be a custom software that will connect to nodes to retrieve other hosts using the getaddr (https://en.bitcoin.it/wiki/Protocol_documentation#getaddr) call on other nodes, and doing this recursively, periodically checking if nodes it found were still alive. But maybe I'm wrong and this is a full node as well. Only them knows.


Title: Re: getconnectioncount
Post by: aleksej996 on April 14, 2018, 07:59:45 PM
86 is pretty good in my opinion. My node gets around 30, I think, probably due to low network bandwidth.

It is always visible on the bitnodes.earn.com when I check.
You can enable email notifications to tell you when it is down, if you want.

As for adding them directly, I don't know. It is probably unnecessary. You might even be slowing them down or limiting them in some way by doing so.


Title: Re: getconnectioncount
Post by: GodlyWizard on April 17, 2018, 10:18:00 AM
Thank you for the answers!

According to their own feature the first address seems to be a full node. However, the second and third (IPv6) addresses return no info.

https://bitnodes.earn.com/nodes/136.243.139.96-8333/ <-- works

https://bitnodes.earn.com/nodes/136.243.139.120-8333/ <-- does not work

https://bitnodes.earn.com/nodes/2a01:4f8:212:3b1f::2-8333/ <-- does not work

My connection amount seems to vary quite a bit, within a couple of refreshes it changed from 86 to 92 and then to 93 and back to 92.