Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

when we do a nat port mapping, explicitly remember the mapped address #386

Merged
merged 1 commit into from
Aug 6, 2018

Conversation

Stebalien
Copy link
Member

related to #383

I won't call this fixed yet but it should help.

related to #383

I won't call this *fixed* yet but it should help.
@ghost ghost assigned Stebalien Aug 2, 2018
@ghost ghost added the status/in-progress In progress label Aug 2, 2018
@Stebalien Stebalien merged commit aca83b9 into master Aug 6, 2018
@ghost ghost removed the status/in-progress In progress label Aug 6, 2018
@Stebalien Stebalien deleted the fix/correct-external-addr branch August 6, 2018 21:52
Stebalien added a commit that referenced this pull request Aug 13, 2018
This reverts commit aca83b9, reversing
changes made to 86b8929.

This was is not the correct fix. We already expose these addresses via the
host's AllAddrs method. The real problem is probably that we just don't ever
tell anyone about them (unless we disconnect and reconnect to our nearby DHT
nodes).

We need an address gossip protocol.
Stebalien added a commit that referenced this pull request Aug 16, 2018
Revert "Merge pull request #386 from libp2p/fix/correct-external-addr"
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant