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

Changing the max connections per peer so that the seed nodes become public #3095

Merged
merged 1 commit into from
Nov 18, 2024

Conversation

ii-cruz
Copy link
Member

@ii-cruz ii-cruz commented Nov 18, 2024

What's in this pull request?

Changes the max connections per peer. The seed nodes have many connections, and this constant is being exceeded. This leads them to get errors when connecting to peers; thus, we mistakenly assume we are not public.

This fixes #3069.

Pull request checklist

  • All tests pass. The project builds and runs.
  • I have resolved any merge conflicts.
  • I have resolved all clippy and rustfmt warnings.

@ii-cruz ii-cruz added the bug Something isn't working label Nov 18, 2024
@ii-cruz ii-cruz self-assigned this Nov 18, 2024
@hrxi
Copy link
Contributor

hrxi commented Nov 18, 2024

The seed nodes have many connections

If I understand the constants correctly, they're about connections between the exactly same peers. Why does the seed node have more than 3 connections to the same peer?

Is it because the node got shut down but the connection is still there? They are all on the same node, right? Can a TCP connection to localhost persist in Linux if the process has died?

@jsdanielh jsdanielh merged commit 52a4b80 into albatross Nov 18, 2024
7 checks passed
@jsdanielh jsdanielh deleted the iicruz/seed-nodes-autonat-fix branch November 18, 2024 22:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

DHT server mode never reached in CI runs
3 participants