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

move go-libp2p-nat here #1513

Merged
merged 46 commits into from
May 20, 2022
Merged

move go-libp2p-nat here #1513

merged 46 commits into from
May 20, 2022

Conversation

marten-seemann
Copy link
Contributor

This was also not on the list in #1187, but I can't see a reason to not consolidate this repo as well.

jbenet and others added 30 commits September 30, 2015 18:42
Some hardware doesn't support UPnP with durations.
If we use same NAT agent and call for the same permanent mapping
again we get the same mapping, no harm done.

If router dies, we will remap again.
Just pros, no cons.
Otherwise, we'll try to port-map localhost.
only map *usable* addresses
NATs only care about TCP/UDP and ports. Using multiaddrs here made this library
really hard to work with correctly.

Furthermore, this library doesn't _actually_ support specifying the internal IP
address. However, we'd still _act_ like the internal IP address mattered. This
caused all sorts of mismatches.
remove all uses of multiaddrs
1. It was unused.
2. It was broken. Attempting to register a notification listener would have
   registered the notifier itself.
3. We need to switch to some consistent event/notification system anyways so
   we're going to replace this code no matter what.

(found by @pornin)
@marten-seemann marten-seemann mentioned this pull request May 20, 2022
65 tasks
Copy link
Member

@Stebalien Stebalien left a comment

Choose a reason for hiding this comment

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

Yeah, we had three levels of indirection...

@marten-seemann marten-seemann merged commit 4c153be into master May 20, 2022
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.

10 participants