ipfs/kubo

Can't punch through dual NAT

Open

#2,879 opened on Jun 20, 2016

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Go (13,906 stars) (2,725 forks)batch import
help wantedkind/bugstatus/deferredtopic/libp2ptopic/nat

Description

Dual NATs are more and more popular as ISPs can't get more IPv4 addresses, but I've got multiple reports that go-ipfs has problems with punching through that NAT setup.

We should create tests using different NAT configurations, where two routers might use different port opening protocols and so on.

Contributor guide

Tech stack
go
Domain
backendinfrastructure
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
GoIPFSNAT traversalTesting
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Investigate the current NAT traversal implementation in go ipfs (e.g., libp2p's NAT manager). Look at existing test files for NAT traversal to understand the testing pattern. Set up a dual NAT environment using tools like Docker or network namespaces. Then write tests that simulate two routers with different port mapping protocols (e.g., full cone, restricted cone, port restricted cone, symmetric). Ensure the tests are automated and can be run in CI.