ipv6 seed node(s) #258

Closed
opened 1 year ago by duke · 1 comments
duke commented 1 year ago
Owner

Currently we have no ipv6 seed nodes. This isn't a huge deal, but if someone wanted to use -onlynet=ipv6 then that won't work well, because they would have no valid seeds to start syncing with. This is somewhat related to the new BIP155 code that was recently merged to the dev branch. That code changes the format of peers.dat, so even if a node knows about some ipv6 peers, those peers will be lost the first time they start their node on the latest code, when the new BIP155 code creates a new peers.dat file.

A workaround is to upgrade to the new BIP155 code first, without using -onlynet and wait until some ipv6 peers exist in your peers.dat. Then the node could be restarted with -onlynet=ipv6 and it will use those existing ipv6 peers.

Currently we have no ipv6 seed nodes. This isn't a huge deal, but if someone wanted to use `-onlynet=ipv6` then that won't work well, because they would have no valid seeds to start syncing with. This is somewhat related to the new BIP155 code that was recently merged to the dev branch. That code changes the format of peers.dat, so even if a node knows about some ipv6 peers, those peers will be lost the first time they start their node on the latest code, when the new BIP155 code creates a new peers.dat file. A workaround is to upgrade to the new BIP155 code first, without using `-onlynet` and wait until some ipv6 peers exist in your peers.dat. Then the node could be restarted with `-onlynet=ipv6` and it will use those existing ipv6 peers.
onryo self-assigned this 1 year ago
duke commented 1 year ago
Poster
Owner

this was done by @onryo, closing

this was done by @onryo, closing
duke closed this issue 1 year ago
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.