[GH-ISSUE #5107] [Feature Request] Support precise specification of multiple server listening addresses #4005

Closed
opened 2026-05-05 14:32:43 -06:00 by gitea-mirror · 2 comments
Owner

Originally created by @bigsk05 on GitHub (Dec 30, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/5107

Describe the feature request

Support precise specification of multiple server listening addresses
For example:
My server has 254 IPv4 addresses and 10 IPv6 addresses, now I hope use a single IPv4 and a single IPv6 for this FRPS server. If I use the [::] mark, it will listen to all my addresses, but if I do not use the [::] mark, then there is no other method to achieve this goal.

Describe alternatives you've considered

Support a string array to specify multiple addresses in the bindAddr field. With type reflection?

Affected area

  • Docs
  • Installation
  • Performance and Scalability
  • Security
  • User Experience
  • Test and Release
  • Developer Infrastructure
  • Client Plugin
  • Server Plugin
  • Extensions
  • Others
Originally created by @bigsk05 on GitHub (Dec 30, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/5107 ### Describe the feature request Support precise specification of multiple server listening addresses For example: My server has 254 IPv4 addresses and 10 IPv6 addresses, now I hope use a single IPv4 and a single IPv6 for this FRPS server. If I use the [::] mark, it will listen to all my addresses, but if I do not use the [::] mark, then there is no other method to achieve this goal. ### Describe alternatives you've considered Support a string array to specify multiple addresses in the bindAddr field. With type reflection? ### Affected area - [ ] Docs - [ ] Installation - [x] Performance and Scalability - [ ] Security - [x] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others
gitea-mirror 2026-05-05 14:32:43 -06:00
Author
Owner

@fatedier commented on GitHub (Jan 4, 2026):

You can work around this by running two frps instances.

<!-- gh-comment-id:3707564158 --> @fatedier commented on GitHub (Jan 4, 2026): You can work around this by running two frps instances.
Author
Owner

@github-actions[bot] commented on GitHub (Jan 19, 2026):

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

<!-- gh-comment-id:3765967972 --> @github-actions[bot] commented on GitHub (Jan 19, 2026): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/frp#4005
No description provided.