-
Notifications
You must be signed in to change notification settings - Fork 949
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
rendezvous: Example "discovering with identify" doesn't work #5388
Comments
Local addresses aren't considered external addresses unless manually added, so this is kind of expected. |
Still wouldn't it be easier to understand in the example if we explicitly register the address instead of vaguely suggest that having the protocol |
Hi @caementarius and thanks for the interest! Want to submit a PR addressing that? |
If it seems relevant enough yes why not. |
This pr closes libp2p#5388 by explicitly adding the local observed address, noting this is out of protocol behaviour in non-example cases Pull-Request: libp2p#5496.
Summary
When launching the
rendezvous
example and trying to discover peers withidentify
, the peer abort because it can't register without knowing any external address.Steps to reproduce
Expected behavior
As suggested in this comment, the protocol
identify
could allow to know and set an external address automatically and then the registration should be successfull.Then the discovering would work as described.
Actual behavior
The peer aborts when registering because it doesn't know any external address.
Relevant log output
Possible Solution
As suggested in this post, we could use the observed address as a potential
ExternalAddress
.Then we could either use it directly or use
autonat
to probe it and obtain aConfirmedExternalAddress
Version
libp2p version
0.53.2
Would you like to work on fixing this bug ?
Yes
The text was updated successfully, but these errors were encountered: