[GH-ISSUE #2515] 是否支持多个客户端共用一个服务端端口配置 #1996

New issue

Closed

opened 2026-05-05 13:17:28 -06:00 by gitea-mirror · 4 comments

gitea-mirror commented

2026-05-05 13:17:28 -06:00

Owner

Originally created by @danileyang on GitHub (Aug 6, 2021).
Original GitHub issue: https://github.com/fatedier/frp/issues/2515

场景需求描述：
已在阿里云ECS上搭建frps集群，目前有多客户端(假设有10000+)，按照文档给出的frpc.ini配置：
每个client的配置如下：
[common]
server_addr = serverIpHere
server_port = serverPortHere

[spynote]
type = tcp
local_ip = 127.0.0.1
local_port = 8080
remote_port = remotePort1 (当客户端非常多的时候，这个服务端的端口是不够用的)
并且好像并不能配置成和其它客户端相同的remote_port端口

请问这个如何解决？

Originally created by @danileyang on GitHub (Aug 6, 2021). Original GitHub issue: https://github.com/fatedier/frp/issues/2515 场景需求描述：已在阿里云ECS上搭建frps集群，目前有多客户端(假设有10000+)，按照文档给出的frpc.ini配置：每个client的配置如下： [common] server_addr = serverIpHere server_port = serverPortHere [spynote] type = tcp local_ip = 127.0.0.1 local_port = 8080 remote_port = remotePort1 (当客户端非常多的时候，这个服务端的端口是不够用的) 并且好像并不能配置成和其它客户端相同的remote_port端口请问这个如何解决？

gitea-mirror

2026-05-05 13:17:28 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:17:31 -06:00

Author

Owner

@fatedier commented on GitHub (Aug 6, 2021):

你想如何解决？

@fatedier commented on GitHub (Aug 6, 2021): 你想如何解决？

gitea-mirror commented

2026-05-05 13:17:31 -06:00

Author

Owner

@IndustrialCommunication commented on GitHub (Aug 11, 2021):

tcp的端口还真解决不了，因为共用一个端口时没有一个可以区分的标志，http端口能共用，是因为可以用域名做为区分标志，不然不知道哪个转哪个。

@IndustrialCommunication commented on GitHub (Aug 11, 2021): tcp的端口还真解决不了，因为共用一个端口时没有一个可以区分的标志，http端口能共用，是因为可以用域名做为区分标志，不然不知道哪个转哪个。

gitea-mirror commented

2026-05-05 13:17:33 -06:00

Author

Owner

@xilu0 commented on GitHub (Aug 12, 2021):

you can use multiple ip address.

@xilu0 commented on GitHub (Aug 12, 2021): you can use multiple ip address.

gitea-mirror commented

2026-05-05 13:17:34 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 12, 2021):

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

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