You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is very useful if the target address is a fixed one, but that target has many other services listening on it with dynamic ports.
Describe the solution you'd like
Add a new flag to boundary connect something like -target-port.
Add optional target port when clicking "connect" in the desktop client.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Explain any additional use-cases
If there are any use-cases that would help us understand the use/need/value please share them as they can help us decide on acceptance and prioritization.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Via the Desktop client, there isn't a way to set a user defined default listening port or address at session establishment time, but that's an interesting feature request that I can share with folks internally.
Via the Desktop client, there isn't a way to set a user defined default listening port or address at session establishment time, but that's an interesting feature request that I can share with folks internally.
Hope this helps!
If I understand the doc correctly, -listen-port should be the port in local machine to proxy request right? This feature request is asking a port used by workers connecting to the target.
Is your feature request related to a problem? Please describe.
I'm not sure if this feature is in place or not, but I didn't find it from the docs.
When creating a target, there's a default port (the target port, not proxy port), e.g. 1234 for a generic tcp target.
I want the worker connect to a different port when do
boundary connect
, something likeThis is very useful if the target address is a fixed one, but that target has many other services listening on it with dynamic ports.
Describe the solution you'd like
boundary connect
something like-target-port
.Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Explain any additional use-cases
If there are any use-cases that would help us understand the use/need/value please share them as they can help us decide on acceptance and prioritization.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: