etc/inittab, to have access to a box shipped and installed in another country, behind NAT, without port forwarding to the box, you can configure it to create an ssh tunnel back to you: tun1:2345:respawn:/usr/bin/ssh -i /path/to/rsaKey -f -N -o "ServerAliveInterval 180" -R 55002:localhost:22 'sleep 365d' sleep 5 done) do not remove the sleep command, ssh may fail quickly and you'll respawn too many processes Just get an ssh.exe for your windows machine.Always use ServerAliveInterval SSH option in case the tunnel issues are generated by expired NAT sessions.Īlways use a respawning method in case the connectivity goes down entirely, you have at least three options here: If public machine does not allow to run unknown *.exe files then you won't be able to run ssh/winscp/bitvise client that you brought on your USB stick either.Īnd as a final thought there is no difference between reverse ssh tunnelling on *nix and windows.You can find VPN clients that can be run without installations (portable *.exe file) You don't need to install software to run it.If you want reliable and versatile way to open connections on any port in any direction from anywhere including public places and networks with security restrictions, VPN is a go-to solution. Why would they? Is there a chance that you misunderstood them? Could it be that a router provided by your ISP blocks incoming connections on port 22? In this case, assuming that router is in your posession, you can just set up port forwarding and achieve desired behavior.ĭon't write off VPN so easily. I have not heard of ISPs specifically blocking incoming connections on port 22 anywhere on network level. What exactly are you trying to achieve in the frist place? Just to be able to remotely access your home PC? Reverse SSH tunnel may or may not be a solution to your problem but there are simpler things that I would recommend trying first. Any other PC is fine being Linux, but not the home one. I can not and will not change the home PC to Linux. I did find a tutorial on how to do it if both machines were using Ubuntu. A lot of SFTP clients run on a USB stick, which makes it simple. Plus, having to install software on a PC every time I want to connect is a hassle. I don't think a VPN will solve this, since I do not have direct control over the school, library, friends, public PC to install software onto it to connect to the VPN. I'm guessing I would need something like putty or bitvise client to create a connection, keep said connection on all the time, then somehow configure the VPS to relay the SSH to my home machine. I do not know how to do this with Windows 10. For example, if I am at a library on their PC, I could plug in my USB drive that has winscp or bitvise client on it, SSH to my VPS, which in turn relays the SSH session to my home server through the tunnel that was originally created. Since my home PC can connect to a outside server just fine, I want my home SSH server to connect to the VPS and then have the VPS, reverse any SSH connections to it (VPS) back to my home PC. What I have done is created myself a new VPS from Amazon, free tier for a year, with no storage. Connecting to an online SFTP server for testing, works just fine. I have confirmed this by calling my ISP and they do indeed block SSH. My ISP blocks ssh from coming IN, but I can connect to other SSH servers outside my LAN no issue. I am running Windows 10 for my home PC with bitvise SSH server, and a VPS Ubuntu ec2 instance from Amazon.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |