$DYNAMIC_PORT$ variable for entries using gateway tunnel

0 vote

Published 2 years ago

Hello,

Would it be possible to extend the use of the variable called $DYNAMIC_PORT$ to return the local bind point port for gateway tunnel connections? Currently it appears to only be applicable to entries that use an SSH VPN with dynamic port configured.

The use case is to be able to reference a dynamic gateway tunnel bind point (i.e. 127.0.0.1:$DYNAMIC_PORT$) as an argument for an entry of type 'Powershell (local)'. This would accomodate using PowerShell remoting from a machine that needs to indirectly connect to a target via a gateway server.

Please let me know if you would like more info.

Thanks

Joe

All Comments (21)

Hubert Mireault

Published 2 years ago

Hello Joe,

Thanks for the request. We will analyse this and get back to you when possible. This is interesting and as you say it would make using the Gateway easier with this versatility.

Regards,

Hubert Mireault

Richard Markiewicz

Published 2 years ago

Hello

The problem here in the simple case is that the gateway tunnel supports multiple listeners in a single tunnel; so there might be multiple local ports listening. This doesn't align well with DYNAMIC_PORT which obviously only works with a single listener.

I'm going to investigate ways we can support this, as I agree with my colleague that this would be very useful, but ultimately the solution might not use the dynamic port variable.

I'm guessing that you typically just have a single TCP listener in your tunnel connections?

Thanks and kind regards,

Richard Markievicz