[GH-ISSUE #4631] [Feature Request] Support binding to multiple specific IPv4 and IPv6 interfaces at the same time. #3655

Closed
opened 2026-05-05 14:20:49 -06:00 by gitea-mirror · 4 comments
Owner

Originally created by @Flightkick on GitHub (Jan 11, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/4631

Describe the feature request

Not sure if this is already possible, I did not find any examples in the docs or example configuration.
It would be nice if it was possible to bind to specific IPv4 and IPv6 interfaces at the same time.

I have found examples where 0.0.0.0 or :: was specified. But this binds to all interfaces.
I would expect something alike:

# frps.toml
bindAddresses = ["xxx.xxx.xxx.xxx", "xxxx:xxxx::etc."] 

Describe alternatives you've considered

Running two separate instances of frps/frpc.

Affected area

  • Docs
  • Installation
  • Performance and Scalability
  • Security
  • User Experience
  • Test and Release
  • Developer Infrastructure
  • Client Plugin
  • Server Plugin
  • Extensions
  • Others
Originally created by @Flightkick on GitHub (Jan 11, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/4631 ### Describe the feature request Not sure if this is already possible, I did not find any examples in the docs or example configuration. It would be nice if it was possible to bind to specific IPv4 and IPv6 interfaces at the same time. I have found examples where `0.0.0.0` or `::` was specified. But this binds to all interfaces. I would expect something alike: ```toml # frps.toml bindAddresses = ["xxx.xxx.xxx.xxx", "xxxx:xxxx::etc."] ``` ### Describe alternatives you've considered Running two separate instances of frps/frpc. ### 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:20:49 -06:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 26, 2025):

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

<!-- gh-comment-id:2614151751 --> @github-actions[bot] commented on GitHub (Jan 26, 2025): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.
Author
Owner

@Flightkick commented on GitHub (Jan 27, 2025):

Not stale

<!-- gh-comment-id:2615857507 --> @Flightkick commented on GitHub (Jan 27, 2025): Not stale
Author
Owner

@fatedier commented on GitHub (Feb 7, 2025):

There are no plans to support this, but you can achieve similar functionality by starting multiple instances with different configuration files.

<!-- gh-comment-id:2641833660 --> @fatedier commented on GitHub (Feb 7, 2025): There are no plans to support this, but you can achieve similar functionality by starting multiple instances with different configuration files.
Author
Owner

@github-actions[bot] commented on GitHub (Feb 22, 2025):

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

<!-- gh-comment-id:2675879200 --> @github-actions[bot] commented on GitHub (Feb 22, 2025): 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#3655
No description provided.