[GH-ISSUE #3984] [Feature Request] Ability to expose entire port ranges.

gitea-mirror commented

2026-05-05 14:02:39 -06:00

Owner

Originally created by @MaximalCats on GitHub (Feb 9, 2024).
Original GitHub issue: https://github.com/fatedier/frp/issues/3984

Describe the feature request

Hey!

Let me start by saying that i have been using frp for almost 6 months now, and i really like it.
However, i couldn't find a feature in the documentation that would allow me to expose entire port ranges, eg: ports 8000-9000
Is this a planned feature?
Thanks

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 @MaximalCats on GitHub (Feb 9, 2024). Original GitHub issue: https://github.com/fatedier/frp/issues/3984 ### Describe the feature request Hey! Let me start by saying that i have been using frp for almost 6 months now, and i really like it. However, i couldn't find a feature in the documentation that would allow me to expose entire port ranges, eg: ports 8000-9000 Is this a planned feature? Thanks ### Describe alternatives you've considered _No response_ ### Affected area - [X] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [X] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 14:02:39 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:02:42 -06:00

Author

Owner

@Kamycz3q commented on GitHub (Feb 9, 2024):

would be really great

@Kamycz3q commented on GitHub (Feb 9, 2024): would be really great

gitea-mirror commented

2026-05-05 14:02:43 -06:00

Author

Owner

@xqzr commented on GitHub (Feb 12, 2024):

cf025d6320/conf/legacy/frpc_legacy_full.ini (L196-L202)

@xqzr commented on GitHub (Feb 12, 2024): https://github.com/fatedier/frp/blob/cf025d63207b4a2872ba946dc32ab56b3f98053a/conf/legacy/frpc_legacy_full.ini#L196-L202

gitea-mirror commented

2026-05-05 14:02:44 -06:00

Author

Owner

@fatedier commented on GitHub (Feb 19, 2024):

For the current architecture, exposing a large number of ports simultaneously on a frpc is not friendly and will have obvious performance issues.

In the future, other implementation methods may be considered.

@fatedier commented on GitHub (Feb 19, 2024): For the current architecture, exposing a large number of ports simultaneously on a frpc is not friendly and will have obvious performance issues. In the future, other implementation methods may be considered.

gitea-mirror commented

2026-05-05 14:02:44 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 12, 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 (Mar 12, 2024): Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

gitea-mirror commented

2026-05-05 14:02:45 -06:00

Author

Owner

@rtsui-harmonicinc commented on GitHub (Jun 26, 2024):

cf025d6320/conf/legacy/frpc_legacy_full.ini (L196-L202)

I couldn't do this for the TOML format

json: cannot unmarshal string into Go struct field ClientConfig.visitors of type int

@rtsui-harmonicinc commented on GitHub (Jun 26, 2024): > https://github.com/fatedier/frp/blob/cf025d63207b4a2872ba946dc32ab56b3f98053a/conf/legacy/frpc_legacy_full.ini#L196-L202 I couldn't do this for the TOML format ``` json: cannot unmarshal string into Go struct field ClientConfig.visitors of type int ```