Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow tcpmux (httpconnect) clients to set local_port #2566

Open
2 of 11 tasks
green-codes opened this issue Sep 5, 2021 · 2 comments
Open
2 of 11 tasks

Allow tcpmux (httpconnect) clients to set local_port #2566

green-codes opened this issue Sep 5, 2021 · 2 comments
Labels
Milestone

Comments

@green-codes
Copy link

Describe the feature request

Is it possible to allow httpconnect clients to set different local_port than tcpmux_httpconnect_port? This will open up frp to a lot more use cases, e.g. proxying port 22 to multiple SSH servers on the client side (each with different subdomains).

Describe alternatives you've considered

using static tcp port forwarding for each client-side tcp service, which is cumbersome

Affected area

  • Docs
  • Installation
  • Performance and Scalability
  • Security
  • User Experience
  • Test and Release
  • Developer Infrastructure
  • Client Plugin
  • Server Plugin
  • Extensions
  • Others
@fatedier
Copy link
Owner

fatedier commented Sep 6, 2021

We plan to support this options but it has low priority.

@fatedier fatedier added the todo label Sep 6, 2021
@green-codes
Copy link
Author

Thanks for replying! Really hope to see this feature at some point. I manage a number of servers (some at different locations so I can’t just cluster them) behind a single frps proxy, and the port configuration is a mess. Allowing TCP mux with subdomains will be a godsend.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants