SSH tcpforwarding dropbear

Networking Solutions
1

I got the same issue on my TRB500 mentioned 2 years ago : Ssh tcp forwarding not working - #2

I have tried to add option GatewayPorts '1' which makes no difference.

Any of you successful on that one ?

I don’t see a way to use an encrypted ssh private key stored on the unit, so I prefer to use tcpforwarding instead.

Many thanks

3

Greetings,

Could you please clarify what your network topology looks like? A simple sketch including IP addresses and ports would be very helpful. Additionally, could you explain the use case and what you are trying to reach?

Best Regards,
Justinas

4

I would like to use Teltonika as a ssh jump server to access another server.

So, from my computer (ssh client) doing a : ssh -J root@ip_trb500 mysername@ip_myserver

option GatewayPorts '1' should be what I need, but it doesn’t work, any other suggestion ?

5

Greetings,

Could you please clarify your network topology? A simple diagram including IP addresses (excluding any sensitive information) would be very helpful.

From your description, I understand that you are accessing the TRB500 remotely via its public IP address and would like it to forward the connection to a server on its LAN. If that is correct, I have tested this setup and confirmed that it works without any additional configuration beyond enabling remote SSH access under System → Administration → Access Control.

image
image621×278 5.21 KB

In my test environment, I connected a TRB device (with a public IP address) from its LAN port to the WAN port of a RUT device (which received IP address 192.168.1.210). Using the ssh -J option, I was able to establish the connection successfully.

Could you please confirm the following:

  • Are you able to run ssh username@ip_myserver directly from the TRB500 CLI? Does it connect successfully?
  • Are you able to SSH into the TRB500 remotely via its public IP?
  • Could you share a screenshot of Network → Firewall → Zones?

Please clarify the setup if I misunderstood

Best Regards,
Justinas

6

Thanks for your response, it was a firewall issue on my side… So I confirm it is working fine, sorry for the noise, as I found the first article with the same issue I thought it was the reason

7

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.