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

fix(network): consider MultiAddrNotSupported as a serioud issu.. #2628

Merged

Conversation

RolandSherwin
Copy link
Member

@RolandSherwin RolandSherwin commented Jan 14, 2025

  • Libp2p throws Outgoing conn errors for all the listen addr (including private) of the remote peer even though we try to dial just the global/public addr. This would mean that we get MultiaddrNotSupported error for the private addr of the peer every single time.
  • Thus, just a single MultiaddrNotSupported error here should not be a huge concern and we should not remove the peer based on this.
  • We now remove the peer ONLY IF ALL the addrs have MultiaddrNotSupported

println!("If this was your bootstrap peer, restart your node with a supported multiaddr");
}
// if we can't dial a peer on a given address, we should remove it from the routing table
there_is_a_serious_issue = true
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

as the default value of all_multiaddr_not_supported is to be true, here actually doing the same? then what's the point to change ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We set it to all_multiaddr_not_supported = false below.
Only if the entire Vec<Error> is MultiaddrNotSupported, we really go after this error, else this error is harmless.

@jacderida jacderida merged commit 819d69b into maidsafe:rc-2024.12.1-hotfix5 Jan 14, 2025
23 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants