-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
NAT hardening #496
Labels
stale
[bot only] Added to stale content; results in auto-close after a week.
Milestone
Comments
This was referenced Jun 30, 2018
Closed
Not sure if this is helpful, just passing it on. https://medium.com/paritytech/why-libp2p-13085ed0c9c8 |
CriesofCarrots
pushed a commit
that referenced
this issue
Feb 28, 2020
mvines
pushed a commit
to mvines/solana
that referenced
this issue
Jun 15, 2020
mvines
pushed a commit
that referenced
this issue
Jun 15, 2020
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
stale
bot
added
the
stale
[bot only] Added to stale content; results in auto-close after a week.
label
Sep 16, 2020
This stale issue has been automatically closed. Thank you for your contributions. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
#494 landed basic support for NATs that honor UPnP to open public UDP ports. Not all NATs to though. This issue is meta issue to spend some read time surveying all the different NAT configurations we want/need to support for both thin and full nodes, and then to file more actionable issues to address.
The text was updated successfully, but these errors were encountered: