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

[net/libp2p] Use raw Identify observed addresses to discover external addresses #7338

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

dmitry-markin
Copy link
Contributor

Instead of using libp2p-provided external address candidates, susceptible to address translation issues, use litep2p-backend approach based on confirming addresses observed by multiple peers as external.

Fixes #7207.

@dmitry-markin dmitry-markin added the T0-node This PR/Issue is related to the topic “node”. label Jan 26, 2025
@dmitry-markin
Copy link
Contributor Author

/cmd prdoc --audience node_dev --bump patch

Copy link
Contributor

@skunert skunert left a comment

Choose a reason for hiding this comment

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

Logic looks good to me!

substrate/client/network/src/peer_info.rs Outdated Show resolved Hide resolved
Err(address)
}
} else {
Ok(address.with(Protocol::P2p(self.local_peer_id)))
Copy link
Contributor

Choose a reason for hiding this comment

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

Not too familiar with this, is it a common scenario to receive an identify report without PeerId? Or more exceptional?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

They typically don't include the peer ID, but it is not stated in libp2p spec whether they are allowed to include the peer ID. Unfortunately, it's a real nightmare in libp2p & litep2p, as it's always not clear whether a multiaddress in some specific place includes or does not include the peer ID.

const MIN_ADDRESS_CONFIRMATIONS: usize = 2;
/// Number of times observed address is received from different peers before it is confirmed as
/// external.
const MIN_ADDRESS_CONFIRMATIONS: usize = 3;
Copy link
Contributor

Choose a reason for hiding this comment

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

We are now waiting for 3 confirmations in an LRU of 32 addresses. Are we losing precision somehow with this setup? Should we bump MAX_EXTERNAL_ADDRESSES to a higher value, or are we able to discover addresses just like before?

Copy link
Contributor Author

@dmitry-markin dmitry-markin Jan 27, 2025

Choose a reason for hiding this comment

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

There was a bug, and when we received the address for the first time we inserted an empty hash map, and only after that counted confirmations. So it was always 3 confirmations, just the information about the first peer ID we got the address from was lost.

Copy link
Contributor

@lexnv lexnv left a comment

Choose a reason for hiding this comment

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

LGTM! Nice job here 🙏

substrate/client/network/src/peer_info.rs Outdated Show resolved Hide resolved
substrate/client/network/src/peer_info.rs Show resolved Hide resolved
Comment on lines +293 to +295
let oldest = (self.address_confirmations.len() >=
self.address_confirmations.limiter().max_length() as usize)
.then(|| {
Copy link
Member

Choose a reason for hiding this comment

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

This code looks slightly horrible :D (Some upstream change that also returns the removed item on insert would be nice)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T0-node This PR/Issue is related to the topic “node”.
Projects
Status: No status
Development

Successfully merging this pull request may close these issues.

Fresh full node start results in spam of 🔍 Discovered new external address for our node
4 participants