ipfs/kubo

Can't punch through dual NAT

Open

#2,879 创建于 2016年6月20日

在 GitHub 查看
 (2 评论) (0 反应) (0 负责人)Go (13,906 star) (2,725 fork)batch import
help wantedkind/bugstatus/deferredtopic/libp2ptopic/nat

描述

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.

贡献者指南

技术栈
go
领域
backendinfrastructure
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
4
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
3-5 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
GoIPFSNAT traversalTesting
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
25
研究方向
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.