libp2p's UPnP implementation fails to transverse multiple NATs due to lack of IGD-PCP support
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.9k
- Forks
- 1.3k
- Avg merge
- 13d 21h
- Merged PRs (30d)
- 1
Description
libp2p is not accounting for multiple NATs. This can be tested on a home network - if you are behind a home router that supports UPnP, create a virtual network with VMware or VirutalBox that is virtual NAT of devices - a VM here will be behind two NATs which can be used to test IGD-PCP support or other hole punching methods.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, or entry point is named. Reproduce the failure with a home router and a VMware or VirtualBox virtual NAT, then inspect the existing UPnP implementation and the feasibility of IGD-PCP or another hole-punching method. Done means libp2p can account for multiple NATs in this setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100