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.
I have a SSH server on my linux system running on port 6192..
I have been connecting to it from over my LAN and also over the internet.
However i am facing a problem while connecting from my workplace. My workplace system is connected to the internet from behind a proxy server. When i try accessing my linux system from there i am getting an error "Connection Timed Out".
I have the Privacy.net analyzer on network-tools.com, i got the info that ports 554, 443 and 80 were allowing outbound traffic. Does using any of these ports allow me to access my linux system using SSH...
The setup i have is:
Fedora 7
Internet thru ADSL and wireless router.
SSH is running on port 6192
It looks like your work is only letting Real Time Streaming Protocol, HTTPS and HTTP outbound respectively. You can make your router/firewall at home forward one of those ports to 6192 (if it's halfway decent), but that's a little risky because those three ports are constantly scanned by jerks and SSH has been exploited before.
I would suggest (bear with me here) a DynDNS.org or no-ip.org address that will forward a request to a non-standard port on your firewall that is forwarded to 6192. That way, you send out a request on 80, and the dyndns redirects from there without having those vulnerable ports open on your network. My setup is a dynamic domain name that redirects to myhomeip.org:8980 (with cloaked redirect), with my firewall set to forward requests on 8980 to my server's SSH port. Of course there is a chance that someone will stumble upon either of the addresses and make a SSH request, but it works very well as long as you have a good password and you choose a higher up port number.
I've never used it to get out of a proxy though, but I don't see why it wouldn't work. Let us know if it does.
I was just trying out sending the SSH request on port 80 through my dyndns.org address and getting no luck, so I guess my suggestion is no good for your situation. Sorry.
I was looking around though, and if you have a web server on your machine you could install a Java SSH applet that you could access through a web page you set up. Or you could set up an HTTP SSH proxy of your own, but I've never done that...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.