Problem using reverse ssh tunnel (remote port forwading)
Matt Johnston
matt at ucc.asn.au
Tue May 29 21:45:17 AWST 2018
Hi Ben,
Does the device log anything from Dropbear in /var/log/auth.log or similar? If you "telnet localhost 10022" does it print anything?
Cheers,
Matt
> On Fri 25/5/2018, at 11:05 pm, Ben Kinsella <BKinsella at advantech-bb.com> wrote:
>
> I have various devices on a private network behind a router, and I typically use “ssh -R” to access them.
> i.e. On the device I run
> $ ssh -fN -R :10022:localhost:22 user at relayserver
> Then I can ssh in via relayserver.
>
> This works for several different device types.
> However, it is not working for a particular device with dropbear v2017.75.
> The initial “ssh -R” command works (I can confirm with netstat on relayserver), but when I attempt to connect I get an error:
> $ ssh -p 10022 root at localhost
> ssh_exchange_identification: Connection closed by remote host
>
> Any suggestions?
>
> Regards,
> Ben.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ucc.gu.uwa.edu.au/pipermail/dropbear/attachments/20180529/8b6b5a21/attachment.htm
More information about the Dropbear
mailing list