Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Network] GetNeighbors reply should alternate between including public-only versus public/private IPs #5171

Closed
jcnelson opened this issue Sep 12, 2024 · 1 comment

Comments

@jcnelson
Copy link
Member

For a variety of reasons, nodes may need to report private IP ranges to each other on neighbor walk (e.g. so nodes in a cluster can find each other). However, this is useless for downstream nodes. To address this without changing the protocol, the node should alternate (with some configurable probability) between reporting public-only neighbors and a mix of public/private nodes.

@jcnelson jcnelson self-assigned this Sep 12, 2024
@github-project-automation github-project-automation bot moved this to Status: 🆕 New in Stacks Core Eng Sep 12, 2024
@saralab saralab moved this from Status: 🆕 New to Status: ✅ Done in Stacks Core Eng Sep 17, 2024
@saralab saralab closed this as completed Sep 17, 2024
@blockstack-devops
Copy link
Contributor

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@stacks-network stacks-network locked as resolved and limited conversation to collaborators Oct 25, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Status: Status: ✅ Done
Development

No branches or pull requests

3 participants