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

Check transport consistency with local connection address before recording observed address #2381

Open
sukunrt opened this issue Jun 19, 2023 · 0 comments
Labels
kind/enhancement A net-new feature or improvement to an existing feature

Comments

@sukunrt
Copy link
Member

sukunrt commented Jun 19, 2023

When we receive observed address in identify we check to see if we are listening on any transport of the reported address. We should also check if conn.LocalMultiaddr() is consistent with the reported address.

I believe this to be the reason that some nodes are advertising their well-known prefix IPv4 Converted IPv6 address. They are learning these addresses from NAT64 peers. Discussion here. Specific scenario here:

@sukunrt sukunrt added the kind/enhancement A net-new feature or improvement to an existing feature label Jun 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement A net-new feature or improvement to an existing feature
Projects
None yet
Development

No branches or pull requests

1 participant