Inconsistent Support for the DYNAMIC_PORT Variable

Inconsistent Support for the DYNAMIC_PORT Variable

avatar

Hello,

I am using Remote Desktop Manager version 2026.3.13.0, and I would like to report an inconsistency in the support for the DYNAMIC_PORT variable across different session types.

This variable is used to retrieve the dynamically allocated local port of an SSH tunnel established by a VPN connection. It is particularly useful when the local port is assigned randomly, as it allows other applications to connect to the correct port without requiring a fixed port configuration.
However, DYNAMIC_PORT appears to be supported by some session types, such as Command line application, but not by others. Specifically, I am unable to use this variable with the official DBeaver plugin.

I found an older discussion on your forum, dating back approximately eight years, where this functionality was already addressed for DBeaver: $DYNAMIC_PORT$ is always 0
At the time, support for this use case appears to have been added when DBeaver was used through a different session configuration. However, with the introduction of the official DBeaver plugin, this functionality seems to have been overlooked or is no longer available.

Could you please clarify why DYNAMIC_PORT is not supported by the DBeaver plugin, while it works with other session types such as Command line ?
More importantly, could you consider adding support for DYNAMIC_PORT to the official DBeaver plugin, so that it can dynamically connect to SSH tunnels using randomly assigned local ports?
Ideally, this variable should be consistently available across all relevant session types and plugins, wherever the underlying connection mechanism supports it.

Thank you for your time and consideration. I look forward to your feedback.

All Comments (0)