Hacker News Reader

Comment by vegardx | Hacker News Reader

My trick is usually just to setup a socks5 tunnel to a remote machine running OpenSSH. The nice thing about this is that you don't have to install anything on your system, and most people have access to a remote Linux/BSD-based server.

Nifty one-liner to set it properly up: "ssh user@host -D 8080". Then you just point your system wide proxy to localhost:8080 and magically see all your data be tunneled.

View on HN

You should try sshuttle. It doesn't require any system-wide proxy configuration.

I have read the documentation, and it's pretty nifty. But I rarely have to use it anyway, so I've stuck with a solution that is not dependant on any other software than what ships nativly with my OS.

Came in to talk see if anyone had already posted this. Hadn't heard of the sshuttle command mentioned a couple times in this thread. Like you mention below it's nice to just have everything built in ready to rock and roll.

Used the command for years to my own boxes. The amazon spin up version I guess is cool. I'll spin one up at some point just in case. Never know.

If the wifi network is blocking all traffic on port 22, you won't be able to tunnel all your traffic over port 22.

But if your ssh server is running on port 80 or 443, this will work (-p {80,443} to your `ssh' command).

How do you set up a system wide proxy under linux?

Depends on what system you're on really. You should be able to do it in network preferences or you could export it in your local shell.

Debian. How would you do it on the shell?

The typical environment variable for socks proxies is SOCKS_SERVER, so: export SOCKS_SERVER=127.0.0.1:8000 in conjunction with ssh -D8000

Unfortunately many utilities don't support SOCKS or have non-standard flags, so you would need a wrapping program like tsocks to force TCP through your proxy.

Reply on news.ycombinator.com