Port 8333

[Sokolik4]

Good day. Once upon a time I opened port 8333 for a Bitcoin client. Then shut down for security reasons.
The question is how dangerous / safe is it to keep the port open?
The question is - my client kept only about 13 connections, although if you monitor the network - the nodes hold more than 1000, how can I fix it?

https://bitnodes.earn.com/
P.S. The computer is very powerful and is connected to a fiber optic network. I would like to support the network
P.S.S. Google translator

[MadGamer]

It's not necessary to open the ports to be a full node, but in that case, you'll have fewer connections.

I don't think it's that dangerous to open them though otherwise, no one would've done it. The only thing I can think of is the ability to run the software remotely but If you don't keep the funds in your full node, you should be fine and also, try to avoid Windows.

[HeRetiK]

Good day. Once upon a time I opened port 8333 for a Bitcoin client. Then shut down for security reasons.
The question is how dangerous / safe is it to keep the port open? [...]

If you have a full node listening at port 8333 there's nothing insecure about it (short of currently unknown security vulnerabilities in the Bitcoin client).

The main reason to keep ports closed for security reasons is to avoid unwanted external access to applications of which you don't know (or don't want) that they are connecting to the internet. If you explicitely want to have an application access the internet and you trust said application there's nothing wrong with opening the required port.

[Pmalek]

I dont much experience regarding your issue but a quick google search came up with the following result, take a look maybe it can help you.
https://bitcoin.stackexchange.com/questions/69076/port-8333-and-issues-to-have-a-connection

[Rath_]

How to make the wallet exchange data immediately with ALL nodes?

It's not possible to connect to all nodes at once. Thirteen connections is still quite a lot (take a look at this discussion). Even if you connect connect to a few hundred nodes, you won't be able to download blocks faster since every block must be verified by your Bitcoin Core instance (the processing power is a huge limit in most cases). The same applies to sharing blocks and filtering data for lightweight clients once you change your -listen parameter to 1.

[Pmalek]

You have been a member here for over a year and should be familiar with the Forum Rules.
https://bitcointalk.org/index.php?topic=703657.0#post_rules
32. Posting multiple posts in a row (excluding bumps and reserved posts by the thread starter) is not allowed.

Dont post multiple posts like you just did, 4 posts within a few minutes one after the other. You can compile all that into one post and quote the previous users in that one post if you need to.

[Sokolik4]

You have been a member here for over a year and should be familiar with the Forum Rules.
https://bitcointalk.org/index.php?topic=703657.0#post_rules
32. Posting multiple posts in a row (excluding bumps and reserved posts by the thread starter) is not allowed.

Dont post multiple posts like you just did, 4 posts within a few minutes one after the other. You can compile all that into one post and quote the previous users in that one post if you need to.

oк.

The only limitation for my computer may be a slow HDD (but soon I want to buy an SSD for a Bitcoin client). But even now my HDD is lightly loaded.
I have fiber and good Internet speed, simultaneous exchange with different nodes should not rest on Internet speed limits
at the same time, many have only 13 connections
http://images.vfl.ru/ii/1541530035/7b981e25/24090812.png
these nodes are connected to 1037 nodes. I only have 13

http://images.vfl.ru/ii/1541529907/10ae5ba5/24090789.png
. I opened port 8333, my computer worked 24/7. my node was visible here -
https://bitnodes.earn.com/
But the other nodes have 1000+ connections, and I have 13 (

[HCP]

at the same time, many have only 13 connections
http://images.vfl.ru/ii/1541530035/7b981e25/24090812.png

That number is NOT the number of connections... it is simply a numerical representation (decimal value of a "bit setting") of the "services" offered by that particular node:

NODE_NETWORK, NODE_BLOOM, NODE_WITNESS (13)
SERVICES

vs.

NODE_NETWORK, NODE_BLOOM, NODE_WITNESS, NODE_NETWORK_LIMITED (1037)
SERVICES

So, in the first node above... the bit setting would be something like 000000001101 = 13... and in the second... 010000001101 = 1037.

[Sokolik4]

at the same time, many have only 13 connections
http://images.vfl.ru/ii/1541530035/7b981e25/24090812.png

That number is NOT the number of connections... it is simply a numerical representation (decimal value of a "bit setting") of the "services" offered by that particular node:

NODE_NETWORK, NODE_BLOOM, NODE_WITNESS (13)
SERVICES

vs.

NODE_NETWORK, NODE_BLOOM, NODE_WITNESS, NODE_NETWORK_LIMITED (1037)
SERVICES

So, in the first node above... the bit setting would be something like 000000001101 = 13... and in the second... 010000001101 = 1037.

In any case, my wallet held about 13 connections only. standard 9 inputs and 13 outputs. And I would like to connect to more nodes.

[apexcrypto]

Here's a decent site to find nodes to connect to:
https://bitnodes.earn.com/nodes/leaderboard/

Pick some, and for each

do: bitcoin-cli addnode <node-address:8333> add  (leave out the < >)

[HCP]

In any case, my wallet held about 13 connections only. standard 9 inputs and 13 outputs. And I would like to connect to more nodes.

Outgoing connections are where you are retrieving blockchain information from... these are the only connections that you can "force" (using "addnode")

Incoming connections are where other nodes are connecting to you, to retrieve blockchain information. You cannot really do much to influence this value, other than allowing incoming connections and possibly setting the "maxconnections" value to something large... although this defaults to 125... "-maxconnections=<n> Maintain at most <n> connections to peers (default: 125)", so if you're only getting 9 incoming, then changing this value won't change much.

You cannot force other nodes to connect to you, and they're likely to prioritise connections based on latency etc... so if there aren't a lot of nodes "near" you (from a network latency perspective) then chances are you won't see many incoming connections.

Just leave your node running with allow incoming connections... people will use it, or not... there isn't much you can do.


Why do you care how many nodes connect to you anyway?