Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi all
Hope some of you guys/girls can help me out with a problem that I have.
What I need to do is to get a SLES 9 server connect to a UK banks SSH/SFTP server over the public Internet to download bank statement data. But due to network restrictions, port 22 is closed and the only way to get out to the Internet is through an HTTP proxy server.
Now I know I could use something like Corkscrew to create the tunnel, which I have proved it works, but I am not allowed to install it in our production environment.
Netcat could be a possibility, but I have not manage to figure out how to get this working with the version of Netcat which ships with SLES 9. NC would do the job with its -X switch, but NC is not part of SLES 9.
Any help would be grately appriciated. Oh and opening port 22 on the firewalls is not an option and no desktop is installed on the server.
Very interesting constraints. Could you enlighten us a bit more about those? What governs or determines what risk outweighs other risks? In other words what's more important? Fascist network policy? Standard server configuration? Or toying with (customers?) bank data?
our firewall/proxy type is HTTP, listening on port 83. I think I've got close to solving it and will let you know when I do.
regards
Richard
Quote:
Originally Posted by JimCotoe
Hi all
Hope some of you guys/girls can help me out with a problem that I have.
What I need to do is to get a SLES 9 server connect to a UK banks SSH/SFTP server over the public Internet to download bank statement data. But due to network restrictions, port 22 is closed and the only way to get out to the Internet is through an HTTP proxy server.
Now I know I could use something like Corkscrew to create the tunnel, which I have proved it works, but I am not allowed to install it in our production environment.
Netcat could be a possibility, but I have not manage to figure out how to get this working with the version of Netcat which ships with SLES 9. NC would do the job with its -X switch, but NC is not part of SLES 9.
Any help would be grately appriciated. Oh and opening port 22 on the firewalls is not an option and no desktop is installed on the server.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.