Re: Dropbear cli-session

2014-11-08 Thread Matt Johnston
Hi Paul, TRACE (28333) 1415195715.978336: connection in progress: err = 99 TRACE (28333) 1415195715.978341: leave netconfdirect: err 99 socketfd (7) TRACE (28333) 1415195715.978347: enter send_msg_channel_failure What's printing this bit? It seems like something is treating a

Re: Dropbear cli-session

2014-11-05 Thread Paul Lemay
Hello again Matt, I finally made it worked with netcat as you suggested in earlier email. I therefore believe that I am not connecting properly in the dropbear server the RX and TX of the client and server. At what location should this be done? On 5 November 2014 09:09, Paul Lemay

Re: Dropbear cli-session

2014-09-25 Thread Paul Lemay
Hello Matt, Thanks for your reply. Let me provide additional information on what I am trying to do with Dropbear. There are several types of client applications (i.e., some running their own client version of SSH others running through the Dropbear SSH clients apps with prot forwarding). They

Re: Dropbear cli-session

2014-09-24 Thread Matt Johnston
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