GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
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 work from a variety of computers, and to keep my notes centralised and privately accessible wherever I am, I use putty as a socks5 server to login to my home (ubuntu) pc that serves local (behind a router) web pages. I can tell Firefox to use the socks5 connection, but there are two problems:
1. This directs all Firefox traffic through the proxy
2. I don't normally use Firefox
Is there a way, on a system wide level, to redirect specific traffic through my ssh/socks proxy?
Why not just port tunnel the port you want to your home connection through putty, no need to use a proxy server within firefox, etc. Unless you're trying to accomplish something differently.
Ah, putty is more featureful than I realised. I had a dynamic tunnel set up for port 9000, which I used with Firefox's socks proxy configuration. I did more reading and found the better way. I didn't understand "destination" is relative to the remote machine, so localhost is the remote machine. Source port is what you connect to, so in my case, I put localhost:9999 iuto my browser, and get to 192.168.1.2:80 on the remote machine.
Thought I'd give an update.. Found what I was really looking for with Privoxy. Putty still opens a socks connection to my home server, but Privoxy routes all system network traffic (based on some simple pattern matching) through it. So, doesn't matter that Opera and Chrome don't have native socks support, and I can decide which traffic goes where. As an added bonus, Privoxy comes with sweet ad filters out of the box.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.