Skip to content
This repository has been archived by the owner on May 11, 2022. It is now read-only.

Understand handling of ipv6 #42

Open
willscott opened this issue Feb 19, 2020 · 1 comment
Open

Understand handling of ipv6 #42

willscott opened this issue Feb 19, 2020 · 1 comment

Comments

@willscott
Copy link
Contributor

there's some potential for a node with a global ipv6 address to attempt to auto-nat from another node also behind the same organizational firewall. In these cases, it may believe itself to be dialable when it fact it isn't.
We should at least test to ensure this is rare, or see if there are reasonable prefix sanity checks to limit the ability for this to happen.
@willscott
Copy link
Contributor Author

Heuristics to mitigate this include #46 and #47

willscott pushed a commit that referenced this issue Mar 13, 2020
@Stebalien
Merge pull request #42 from libp2p/dependabot/go_modules/github.com/l…
4d09550 
…ibp2p/go-libp2p-core-0.3.1

Bump github.com/libp2p/go-libp2p-core from 0.3.0 to 0.3.1
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@willscott