It is not possible to connect to an SSH server with a port other than the default 22

[henriquesebastiao]

Describe the bug: It is not possible to connect to an SSH server that is running on a port other than the default port 22.

Steps To Reproduce:

1. Connect to a Wi-Fi network.
2. Go to the Wi-Fi menu and select the SSH option.
3. Please provide the SSH server address (IP address or hostname).
4. Specify the SSH port.
5. Enter the user.
6. Enter the password.
7. Press enter.

• Device used: M5 Stack Cardputer

Expected behavior: It should be possible to connect to the server normally, just as it happens when using the standard SSH port.

Actual behavior: Pressing between the lines will cause a red bar to flash on the screen, returning you to the Bruce's main menu.

Additional context / logs: I tested both a local and a remote server, using either an IP address or hostname, but it was only possible to connect when using the standard SSH port. Bruce version: 1.11.1

Video:

https://github.com/user-attachments/assets/ccaa6610-2b22-414c-ba63-5734913bc1e8

[bmorcelli]

does your target have this other port opened for connection?

[henriquesebastiao]

does your target have this other port opened for connection?

Yes, I checked if the ports were open.

A little more context.

The devices I tried to access were:

• Mikrotik RB960PGS Router (tested with ports 3522, 8022 and 22)
• Mikrotik CHR x64 Router (Cloud Hosted Router) (tested with ports 3522, 8022 and 22)
• Ubuntu Server x64 (tested with port 22)

On all devices, access was only possible through port 22.

[henriquesebastiao]

After checking the router's logs and firewall rules following the connection attempt with Bruce via the custom port, I verified that the rule didn't register and nothing is visible in the logs either. This leads me to believe that perhaps Bruce is unable to initiate the connection attempt through a custom port.