[GH-ISSUE #4270] One port for multiple remote connections

gitea-mirror commented

2026-05-05 14:10:11 -06:00

Owner

Copy link

Originally created by @storm66-ag on GitHub (Jun 7, 2024).
Original GitHub issue: https://github.com/fatedier/frp/issues/4270

Describe the feature request

Hello Guys!
Will be great if the lot of remote frpc apps could to connected to the server to one same ports....
For example frps binds on the port 7000 and frpc1 will connect to the port 7000 and put the RemotePort like 1000, then frpc2 will connect to the 7000 and put the RemotePort like 10001..... etc

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 @storm66-ag on GitHub (Jun 7, 2024). Original GitHub issue: https://github.com/fatedier/frp/issues/4270 ### Describe the feature request Hello Guys! Will be great if the lot of remote frpc apps could to connected to the server to one same ports.... For example frps binds on the port 7000 and frpc1 will connect to the port 7000 and put the RemotePort like 1000, then frpc2 will connect to the 7000 and put the RemotePort like 10001..... etc ### Describe alternatives you've considered _No response_ ### Affected area - [ ] Docs - [ ] Installation - [X] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 14:10:11 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:10:15 -06:00

Author

Owner

Copy link

@xqzr commented on GitHub (Jun 8, 2024):

无需额外配置，即可实现

@xqzr commented on GitHub (Jun 8, 2024): 无需额外配置，即可实现

gitea-mirror commented

2026-05-05 14:10:16 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Jun 30, 2024):

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

@github-actions[bot] commented on GitHub (Jun 30, 2024): Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

No Branch/Tag specified