#Ubuntu putty ssh tunnel not working install
#Ubuntu putty ssh tunnel not working update

without having them fail.Īs a bonus, you can detach the tmux session (CTRL-b,d) and come back to it later (ssh back in, then tmux a).įor raspberrypi's, it works if you change 'us.' to '', and for random debian you might have luck with 'ftp.us.'įor me, the use case is things like raspi's on a isolated static ip network, where I have another server with two network connections (one with internet access, another to the isolated lan) where it does not route: It's running trueNAS, and the lan is staying isolated.īut it does have opensshd that I can ssh into, and then ssh along to the pi. Now, configure /etc/nf: sudo nano /etc/nfĬhange the last line from socks4 127.0.0.1 9050 to socks5 127.0.0.1 17471.įinally, you can now run things like sudo proxychains apt upgrade -y and proxychains pip install. You can see it with ps aux |grep ssh or so. This doesn't seem like it's done anything, because it's running in the back ground. Next, we'll make a ssh connection from the isolated computer back to any computer it can SSH to which does have internet access, lets call it server.

(quick primer, uses CTRL-B than another key, 'c' for another new shell, 'n/p' for cycling between shells, 'd' to detach and leave things running). Notice the last line there undid the apt proxy configuration?Īfter you have proxychains and tmux, you can get much more reliable operation, and without funky apt configuration changes, and pip / curl etc works too.įirst, start up tmux.

#Ubuntu putty ssh tunnel not working install

Install proxychains and tmux: you might have luck with something like: sudo ssh -R 8080:us.:80 'Acquire::http::Proxy ' | sudo tee /etc/apt//nf

Configure your session as you normally would.

When starting the session, select SSH -> Tunnels.

This can also be achieved using Putty (assuming that Computer A is the Windows machine).

You DON'T have to use the same ssh connection to utilize the tunnel (meaning if you have multiple ssh connection into Computer B, they should all work).

You HAVE to keep the original session of ssh from Computer A to Computer B active while using Computer B to access apt-get repositories.

#Ubuntu putty ssh tunnel not working update

Run your apt-get update or install or upgrade on Computer B and it should work. Ssh into Computer B from Computer A sudo ssh -R :us.:80 Computer B's /etc/apt/apt.conf to include the following lines: Acquire::http::Proxy ' Acquire::https::Proxy '