[GH-ISSUE #4888] [Feature Request] 想请教一下，关于对P2P的扩展问题是否可行？

gitea-mirror commented

2026-05-05 14:28:00 -06:00

Owner

Copy link

Originally created by @wyt990 on GitHub (Jul 20, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/4888

Describe the feature request

这种p2p模式可以不受服务器带宽的影响，直接传输，但是需要在内网和访问端都安装frpc，这不太方便，有没有一种方法可以在访问端不安装frpc访问内网，我的想法是，内网安装frpc使用两个端口连接到frps端，并使用一个端口A与frps保持连接进行信息交换，同时frps记录frpc的另一个端口B，当访客需要访问这个内网的frpc时，frps就将访问引导到这个端口B，使用这个端口B直接与内网进行连接，这样就可以避免frps进行转发影响传输效率。只是探讨一下这种思路是否可行？

Describe alternatives you've considered

No response

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @wyt990 on GitHub (Jul 20, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/4888 ### Describe the feature request 这种p2p模式可以不受服务器带宽的影响，直接传输，但是需要在内网和访问端都安装frpc，这不太方便，有没有一种方法可以在访问端不安装frpc访问内网，我的想法是，内网安装frpc使用两个端口连接到frps端，并使用一个端口A与frps保持连接进行信息交换，同时frps记录frpc的另一个端口B，当访客需要访问这个内网的frpc时，frps就将访问引导到这个端口B，使用这个端口B直接与内网进行连接，这样就可以避免frps进行转发影响传输效率。只是探讨一下这种思路是否可行？ ### Describe alternatives you've considered _No response_ ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 14:28:00 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:28:03 -06:00

Author

Owner

Copy link

@itsKV commented on GitHub (Jul 20, 2025):

@wyt990 Have you tried SSH command for hole punching? I think this is what you want.
Refer local and remote port forwarding of native ssh command.

@itsKV commented on GitHub (Jul 20, 2025): @wyt990 Have you tried SSH command for hole punching? I think this is what you want. Refer local and remote port forwarding of native ssh command.

gitea-mirror commented

2026-05-05 14:28:04 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Aug 4, 2025):

Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (Aug 4, 2025): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

No Branch/Tag specified