Author

Topic: not_publicly_routable on getpeerinfo (Read 158 times)

newbie
Activity: 27
Merit: 2
November 12, 2022, 12:33:38 PM
#5
How do those nodes connect to me (or me to them) without me knowing their ip address?

Since those IP are private IP address (as defined by rfc1918[1]), it's possible those nodes actively scan the local network.

After establishing that part, each node in the network do also share each other information and the node may keep the information in their own known-node local databases, so other or you can connect to each other. For a further detailed explanation, you can refer to: https://developer.bitcoin.org/devguide/p2p_network.html

So when I'm connected to a  not publicly routeable node, does that mean I'm connected to it through another node?

No. It means it can't be accessed through outside local network since the node has private IP address[2]. Bitcoin Core getpeerinfo only show directly connected node.

[1] https://www.rfc-editor.org/rfc/rfc1918
[2] https://networkengineering.stackexchange.com/a/40336

Super, this is really informative, thanks for sharing those links, OP try and take a look at the second link as well, very informative and well detailed
legendary
Activity: 2870
Merit: 7490
Crypto Swap Exchange
November 12, 2022, 04:50:18 AM
#4
How do those nodes connect to me (or me to them) without me knowing their ip address?

Since those IP are private IP address (as defined by rfc1918[1]), it's possible those nodes actively scan the local network.

After establishing that part, each node in the network do also share each other information and the node may keep the information in their own known-node local databases, so other or you can connect to each other. For a further detailed explanation, you can refer to: https://developer.bitcoin.org/devguide/p2p_network.html

So when I'm connected to a  not publicly routeable node, does that mean I'm connected to it through another node?

No. It means it can't be accessed through outside local network since the node has private IP address[2]. Bitcoin Core getpeerinfo only show directly connected node.

[1] https://www.rfc-editor.org/rfc/rfc1918
[2] https://networkengineering.stackexchange.com/a/40336
newbie
Activity: 2
Merit: 4
November 11, 2022, 03:45:46 PM
#3
After establishing that part, each node in the network do also share each other information and the node may keep the information in their own known-node local databases, so other or you can connect to each other. For a further detailed explanation, you can refer to: https://developer.bitcoin.org/devguide/p2p_network.html

So when I'm connected to a  not publicly routeable node, does that mean I'm connected to it through another node?
legendary
Activity: 1932
Merit: 1273
November 09, 2022, 05:46:26 AM
#2
How do those nodes connect to me (or me to them) without me knowing their ip address?

Bitcoin Core have hardcoded DNS seed and node IPs. If you are running a brand new node, that information is where your node relies upon to get in into the network.

After establishing that part, each node in the network do also share each other information and the node may keep the information in their own known-node local databases, so other or you can connect to each other. For a further detailed explanation, you can refer to: https://developer.bitcoin.org/devguide/p2p_network.html
newbie
Activity: 2
Merit: 4
November 09, 2022, 05:00:06 AM
#1
Good, I'm a bit new to the topic of nodes, and I have a doubt when obtaining the pairs connected to my node.

https://imgur.com/a/hj0bXQt

As you can see, when I get the list of connected peers, some of them have a not_publicly_routable network and as ip addresses 172.26.0.1 and 172.26.0.2, which are private networks.
How do those nodes connect to me (or me to them) without me knowing their ip address?
Jump to: