Dropbear cli-session

Matt Johnston matt at ucc.asn.au
Thu Sep 25 07:35:50 WST 2014

Hi Paul,

Which SSH implementation are you using on the client side?
If you're using Dropbear then -B "netcat mode" will do what
I think you want. It's entirely client-side using standard
TCP forwarding from the spec, it just connects the SSH
client's input to that TCP forwarded channel.

Another option would be to send the command 
"nc localserver localport" in the SSH session.  You'll need
to make sure "nc" is installed on the server. In the past
when I've done that I've had problems with nc processes
hanging around which is why I added "netcat mode". 

I may be misunderstanding exactly how your setup fits
together, let me know.


On Wed, Sep 24, 2014 at 01:01:34PM -0400, Paul Lemay wrote:
> Hello there,
> I have a SSH client browser. It is connected to the Dropbear server. I
> would like to know if it is possible to tailor dropbear so that, once the
> dropbear authentication process is completed, a connection is establish to
> my local server ready to takeover TCP communication for this browser.
> I understand there is a cli-tcpfwd that seems to support this function but
> I do not know how to use it. Are there some examples available?

More information about the Dropbear mailing list