Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I tried your instructions but I could not make them work for me. Assuming I followed your instructions correctly (and perhaps that is not a valid assumption!), I believe the reason it did not work is because I also need the data ports forwarded down the tunnel, and not just the control port.
The method I outlined above allows for the data ports to be known in advance and therefore forwarded down the tunnel.
Please let me know if I did not follow your method correctly and the data ports should have been forwarded down the tunnel as well?
I got this working using putty 0.60 for setting up a dynamic tunnel, with this kind of tunnel PuTTY provides a local SOCKS 4/4A/5 proxy on a local port. Your FTP client must be set to use this local SOCKS proxy and passive mode.
Not so detailed Instructions:
Open putty configuration.
Set up an SSH connection to your SSH server as usual (host, port, etc.)
Go to Connection > SSH > Tunnels.
Fill in source port, this is the port where SOCKS proxy will listen, so you FTP client should be set to use 127.0.0.1:<source port> as socks proxy.
Destination: empty, not used for dynamic tunnels.
Select Dynamic radio button.
(optional) Go back to session and save you settings.
Connect to your SSH server!
on FTP client:
Configure your FTP client to use a SOCKS proxy at 127.0.0.1:<source port>.
Configure your FTP client to use PASSIVE mode.
FTP connection must be opened to actual FTP server address and port, for example 192.168.0.1:21. Note that your SSH server must be able to reach your FTP server at that IP address and port.
PS: I'm a frequently visitor of this forums and got lot of help from here, just now i have this chance to help back so ... hope it helps!
Legend! Long story short I'm in IT, tunnelling etc is a frequent requirement in my role, I knew I wanted to use a dynamic tunnel in PUTTY to get around FTP's damn dual port set-up but hadn't considered adding a proxy to my FTP client!! You are a star, works like a charm!