5 ms·
Or just ssh -D localport -fN user@vps Then for chrome/chromium: chromium --proxy-server="socks5:localhost:localport" If you need multiple instances running
by yogo 12y ago
Or just
ssh -D localport -fN user@vps
Then for chrome/chromium:
chromium --proxy-server="socks5:localhost:localport"
If you need multiple instances running different proxy connections use different data directories like:
chromium --user-data-dir="other-dir" --proxy-server="socks5:localhost:localport"
Edit: sshuttle covers more than port forwarding but the article was geared at browsing the web through a vps hence my comment.
- tlongren 12y agoThat's a good option as well! So, if sshuttle ever stops working, this. Thanks for pointing this out.
- derwiki 12y agoI've been using this method to Internet from China with better success than paid VPN solutions. So simple, and I can debug myself! Hint: if things are mysteriously hanging, add `-vvv` to turn on super verbose logging: `ssh -vvvfND localport user@vps`
- bluedino 12y agoGUI version of doing the same thing: https://calomel.org/firefox_ssh_proxy.html https://calomel.org/firefox_ssh_proxy.html
- tlongren 12y agoWhere's the GUI?
- rahimnathwani 12y agoI gave up using SOCKS, and now just use SSH to map a local port to a remote squid3 instance. This way my DNS queries are done on the VPS, and aren't subject to interference by my ISP.
- Dylan16807 12y agoDoes that actually proxy the connections opened by flash these days?
- meowface 12y agoIt does not. For that, you need to change your routing table so that anything destined for 0.0.0.0 goes through the tunnel. This is basically what sshuttle does. One downside is that SSH tunnels can only forward TCP, not UDP, traffic. sshuttle adds special handling for DNS (which is UDP) but any other UDP communication will not work.