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.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
At school, I'd like to be able to SSH home so I can get files from my computer (I won't be a breach of security), but because of the proxy (I think), it doesn't let me. I get an error when trying to connect using PuTTY: "Network error. Connection timed out." Or something of the same meaning. Is there any way to SSH through the proxy so that I can connect to my house? I'm using PuTTY v0.58 and SSH2.
ssh can run through an HTTP proxy ok, but your firewalls and such need to be configured to permit the destination outbound too. personally i've had good experiences running an ssh server on port 443 as this port has been unused as i don't server https and so you could get straight through that way. if your proxy will try to connect to port 22 directly then that's fine then.
I'm not sure I know what you mean. You can specify which port to use in the PuTTY GUI, or I think at the command-line by doing
This is what i mean :
- default port for ssh is 22.
- if the sys admin didn't change the default port to other port such as 443 then a command like this ssh hostname:443 will be failed.
- if your sys admin never change the default port to other port and has blocked a connection to port 22 or only specified ip can access to port 22 then u cant do anything, unless you know how to hack to the system.
if the OP wants to ssh "home" to me that suggests that he is the server admin, in which case he can make ssh listen wherever he wants to. Additionally an ADSL router or such like that is already sitting here can be configured to portward external 443 requests to port 22 on the server inside. Mind you, this is only my suggestion when i had no success with any other attempts...
if your school firewall has a policy to drop input/output by default and only allow selective connections then you have a problem. the administrator there must have rules in place for only the packets he wants in/out and that too at certain ports. all other packets are dropped by default in such conditions.
now when you ssh home, you connect to a ssh server running on certain port and a certain ip. your administrator must add a rule to allow this. your other option would be to configure your ssh server at home to use a global port which the administrator at school dare not block. see if you can find out a port that has global access to outside world and then use that port to connect home. that way you would be using a outgoing/incoming connection for which there already is an accept rule in your school firewall.