Multiple different SSH Secure Gateways don't load automatically if one is open already

Hi everyone,

I have multiple different data sources based on XML files and each models a different topic or customer network or stuff. I really often need to access hosts in some private network using SSH jump hosts and have created SSH Secure Gateways. That are SSH-tunnels acting as dynamic socks proxy on localhost and some port, like in the following example:


I have lots of e.g. browser sessions afterwards using those SSH-tunnels like in the following example:



This whole setup allows me to pretty conveniently access web-UIs of printers and stuff in otherwise private networks and is one of the major benefits of RDM for my use-cases compared to other software. When opening e.g. web-UI sessions, the SSH tunnel is even established automatically as necessary. Though, there's one thing which seems unnecessary annoying:

I have multiple different data sources with the same approaches and in ALL of them the one important SSH tunnel is named the same "SSH Secure Gateway". Simply because I don't need to care about the name too much and when configuring web-UI sessions to use SSH, the one and only available in the current data source is suggested only.

Though, when actually executing a web-UI session there seems to be some name-only check if the configured SSH Secure Gateway is established already and if so, some possibly different one is not anymore. This actually prevents me from easily accessing multiple different web-UIs in different private networks at the same time. Simply because some "SSH Secure Gateway" is open already, all web-UI session require a different one think that this is the correct one already and simply don't open the correct one anymore.

Would be great if this check could be enhanced like in the config dialog, where all web-UI sessions correctly know about their own SSH tunnel to use. Thanks!