utilizing $HOST$ variable in a port forward entry appends a ":" to the end of the host string
utilizing $HOST$ variable in a port forward entry appends a ":" to the end of the host string
I am attempting to create a port forward entry using the $HOST$ variable, however it appends a ":" to the end of the host entry, this effectively attempts to use this string (xxx.xxx.xxx.xxx::80) to open a port forward which fails.
Output from tunnel session:
[8/2/2017 10:03:46 AM] Looking up host "10.240.1.19"
[8/2/2017 10:03:46 AM] Connecting to 10.240.1.19 port 22
[8/2/2017 10:03:46 AM] We claim version: SSH-2.0-PuTTY_Release_0.67
[8/2/2017 10:03:46 AM] Server version: SSH-2.0-OpenSSH_4.3
[8/2/2017 10:03:46 AM] We believe remote version has SSH-2 channel request bug
[8/2/2017 10:03:46 AM] Using SSH protocol version 2
[8/2/2017 10:03:46 AM] Doing Diffie-Hellman group exchange
[8/2/2017 10:03:46 AM] Doing Diffie-Hellman key exchange with hash SHA-1
<APPENDED ENTRY>
[8/2/2017 10:03:46 AM] Access granted
[8/2/2017 10:03:46 AM] Opening session as main channel
[8/2/2017 10:03:46 AM] Opened main channel
[8/2/2017 10:03:46 AM] Service lookup failed for destination port ":80"
[8/2/2017 10:03:46 AM] Allocated pty (ospeed 38400bps, ispeed 38400bps)
[8/2/2017 10:03:46 AM] Started a shell/command
to reproduce, create a port forward entry as a sub connection:
source = 127.0.0.1
Source Port = 80
Destination = $HOST$
Destination Port = 80
Mode = Local
I have attempted similar with Dynamic Mode, however that fails as well, but I believe that is a seperate issue.
Manually inputting the host works without issue.
All Comments (5)
Hello,
I'm unable to reproduce the issue, there isn't a ":" appended for me by using the $HOST$ variable. Can you try doing the same thing with your portforward entry not being a subconnection, as a test? I'm wondering if there's an issue because of that.
Regards,
Hubert Mireault
It does work as a stand alone entry.
I am attempting to utilize this as a sub connection, or even a template.
Is the parent entry of the Host type? If so, what are its settings, since they might affect how the $HOST$ variable is resolved?
Regards,
Hubert Mireault
I will test and get back to you. Additionally I believe the issue may stem from my error (but could be a bug as well).
Under the SSH Settings (second tab when creating a SSH Port Forward Entry), I was using $HOST$:$PORT$ since the end goal was to have a template. The reason for this is that our access port for the ssh service can vary from system to system and I did not see a way to define just the port as a variable for the entries.
I have since removed the port variable and simply used $HOST$, which seems to be more consistent and is giving me the expected results.
You would be right, I'm not sure if RDM is able to support sending the port in this way which is why it fails.
It's good that you could work around this limitation.
Regards,
Hubert Mireault