I've replaced my Bering/sshd firewall with a Bering uClibc/dropbear combo and I don't seem to be able to make tunnels like I used to from an outside location using PuTTY. (For instance, I used to connect with Windows/PuTTY to my firewall and open a shell while forwarding a local port. Then I could connect local port xyz on my work desktop to port 22 on my home desktop through the firewall and open a shell there. And then on to my SL-5500 which is connected and left running. All great fun. I often demo these abilities to amazed engineers in the office whose only computer experience is MS Office on MS Windows)
Now, I can open the shell but the tunnel doesn't seem to happen. If I try to use it, the original session crashes. The man page for the full-up version of dropbear indicates that forwarding ports is the default behavior and a switch is used to disable it. But when Bering-uClibc 2.01 was introduced, dropbear port forwarding evidently only "partly" worked. Has anyone sucessfully used dropbear 0.41 for port forwarding? Is there a diagnostic that will show the forwarding is active? netstat -a shows the server listening and the established connection but would a forwarded port show up there? -John ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
