Bitcoin Forum
January 24, 2019, 11:48:55 AM *
News: Latest Bitcoin Core release: 0.17.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 [2]  All
  Print  
Author Topic: Bitcoin full nodes with IPv4 and IPv6 - Why most peers are on IPv4?  (Read 3387 times)
.anto.
Full Member
***
Offline Offline

Activity: 162
Merit: 100


View Profile
February 01, 2016, 01:49:40 PM
 #21

My implementation would be to connect to as many nodes as possible until there are none able to connect to or the outbound connections are full.

For example, with IPv6, it would search the local database for all IPv6 nodes and attempt to connect to all of them. Then it would ask for peers and connect to any IPv6 that it's peers gives to it. After either all 8 outbound connections are taken or there are no remaining IPv6 nodes that can be connected to after searching through the databases described above, it will make outbound connections to IPv4 nodes if any outbound slots are available. It would accept any incoming connections from both IPv4 and IPv6.
I would imagine that you need to modify a lot of other places in the current Bitcoin software. So the risk of breaking other parts in the system that might not even be related to the main purpose of the changes, will be higher.

So I still think that the risk is lower if we would just separate the MAX_OUTBOUND_CONNECTIONS for individually IPv4 and IPv6. Because in this case, the parts that will be broken is very likely the additional ones related to IPv6. I hope that they will do very minimal modifications on the parts related to IPv4.
1548330536
Hero Member
*
Offline Offline

Posts: 1548330536

View Profile Personal Message (Offline)

Ignore
1548330536
Reply with quote  #2

1548330536
Report to moderator
PLAY NOW
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1548330536
Hero Member
*
Offline Offline

Posts: 1548330536

View Profile Personal Message (Offline)

Ignore
1548330536
Reply with quote  #2

1548330536
Report to moderator
1548330536
Hero Member
*
Offline Offline

Posts: 1548330536

View Profile Personal Message (Offline)

Ignore
1548330536
Reply with quote  #2

1548330536
Report to moderator
.anto.
Full Member
***
Offline Offline

Activity: 162
Merit: 100


View Profile
February 03, 2016, 09:59:35 AM
 #22

I still suspect that there is something wrong in Bitcoin package related to the handling of IPv6.

I have installed and set up bitcoind on my PC at home that I am using as NAS backup. I set only to run on IPv6, i.e. onlynet=ipv6. It has been running for more than a day now. But there are only 2 IPv6 peers connected to it and all 8 outgoing connections have been used. This has happened after about an hour after restarting bitcoind, so no change after that. When I checked it just now, there were 29 unique IPv6 peers recorded on the debug.log. And out of that 29 IPv6 peers, 16 of them opened port 8333.

On IPv4, I usually get more than 20 peers (8 of them outgoing peers) within an hour after I restart bitcoind. I expected that my node gets more IPv6 peers than 10 after runing more than a day. So it looks like the propagation of peers on IPv6 is very much lower. But I still don't believe that it is because there are less IPv6 peers. But let's see how this look like in the next 2 days.
Pages: « 1 [2]  All
  Print  
 
Jump to:  

Bitcointalk.org is not available or authorized for sale. Do not believe any fake listings.
Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!