starred/electerm

Fork 0

mirror of https://github.com/electerm/electerm.git synced 2026-04-26 05:55:55 +03:00

[GH-ISSUE #3701] Illogical ssh-jump settings #2540

New issue

Closed

opened 2026-02-27 00:53:21 +03:00 by kerem · 4 comments

kerem commented

2026-02-27 00:53:21 +03:00

Owner

Originally created by @mbzik on GitHub (Dec 7, 2024).
Original GitHub issue: https://github.com/electerm/electerm/issues/3701

Electerm Version and download file extension(Electerm版本和下载文件后缀)

electerm-1.50.59-win-x64-installer.exe

Platform detail (平台详情)

Microsoft Windows NT 10.0.22631.0 x64

What steps will reproduce the bug?(重新问题的详细步骤)

Set up a connection through SSH-jump. Specify address A as the address in the bookmark, and address B as the address in the "Connection Hopping" tab.

What should have happened?(期望的结果)

The connection should be made to address B first and then to address A. Currently, it happens the other way around.

Would this happen in other terminal app(是否能够在其他同类软件重现这个问题)

In clients like SecureCRT, MobaXterm, and others, the connection to address B occurs first, followed by the connection to address A.

Additional information(其他任何相关信息)

Thank you for developing and supporting your product!

The logic of configuring ssh-jump differs from all other clients, such as SecureCRT, MobaXterm, etc. The discrepancy lies in the fact that when creating a bookmark, the main address specified is the initial address, and further hops are configured in the "Connection Hopping" tab. According to the logic of all other clients, it should be the opposite. The address specified on the main tab when creating a connection should be the last in the chain, and the ssh jumps that need to be made before connecting to the main address. Because of this, there is an illogical display; if you have multiple connection addresses through a terminal server, it will appear as several different connections but all with the same name. There is a strong request to change the connection order so that the hops from "Connection Hopping" occur first, and then the connection to the main address from the bookmark takes place.

Originally created by @mbzik on GitHub (Dec 7, 2024). Original GitHub issue: https://github.com/electerm/electerm/issues/3701 ### Electerm Version and download file extension(Electerm版本和下载文件后缀) electerm-1.50.59-win-x64-installer.exe ### Platform detail (平台详情) Microsoft Windows NT 10.0.22631.0 x64 ### What steps will reproduce the bug?(重新问题的详细步骤) Set up a connection through SSH-jump. Specify address A as the address in the bookmark, and address B as the address in the "Connection Hopping" tab. ### What should have happened?(期望的结果) The connection should be made to address B first and then to address A. Currently, it happens the other way around. ### Would this happen in other terminal app(是否能够在其他同类软件重现这个问题) In clients like SecureCRT, MobaXterm, and others, the connection to address B occurs first, followed by the connection to address A. ### Additional information(其他任何相关信息) Thank you for developing and supporting your product! The logic of configuring ssh-jump differs from all other clients, such as SecureCRT, MobaXterm, etc. The discrepancy lies in the fact that when creating a bookmark, the main address specified is the initial address, and further hops are configured in the "Connection Hopping" tab. According to the logic of all other clients, it should be the opposite. The address specified on the main tab when creating a connection should be the last in the chain, and the ssh jumps that need to be made before connecting to the main address. Because of this, there is an illogical display; if you have multiple connection addresses through a terminal server, it will appear as several different connections but all with the same name. There is a strong request to change the connection order so that the hops from "Connection Hopping" occur first, and then the connection to the main address from the bookmark takes place.

kerem

2026-02-27 00:53:21 +03:00

closed this issue
added the
need investigate

enhancement
labels

kerem commented

2026-02-27 00:53:22 +03:00

Author

Owner

@zxdong262 commented on GitHub (Dec 7, 2024):

Thank you for the feedback, it make sense! Just need think a way to be compatible with user's old jump settings.

@zxdong262 commented on GitHub (Dec 7, 2024): Thank you for the feedback, it make sense! Just need think a way to be compatible with user's old jump settings.

kerem commented

2026-02-27 00:53:22 +03:00

Author

Owner

@zxdong262 commented on GitHub (Dec 8, 2024):

@mbzik Thank you for the support! Would update in next release

@zxdong262 commented on GitHub (Dec 8, 2024): @mbzik Thank you for the support! Would update in next release

kerem commented

2026-02-27 00:53:22 +03:00

Author

Owner

@mbzik commented on GitHub (Dec 8, 2024):

@mbzik Thank you for the support! Would update in next release

Thank you for your product and its development!

@mbzik commented on GitHub (Dec 8, 2024): > @mbzik Thank you for the support! Would update in next release Thank you for your product and its development!

kerem commented

2026-02-27 00:53:22 +03:00

Author

Owner

@zxdong262 commented on GitHub (Dec 10, 2024):

In latest release now

@zxdong262 commented on GitHub (Dec 10, 2024): In latest release now