3 ms·
I use the following configuration: I run two tinyproxy instances on my home server and I point all browser traffic to the first instance. The first instance ru
by kuon 9y ago
I use the following configuration:
I run two tinyproxy instances on my home server and I point all browser traffic to the first instance. The first instance run with the default routing table on port 8888 and has entries like upstream localhost:8889 ".somesite.com" the second instance, which run on port 8889 is run with the vpn as default route (I use setfib under FreeBSD).
With this setup, traffic goes by default directly on the net, but the tinyproxy config file can be used to redirect some traffic through the VPN.
Of course, you can do it the other way around to have traffic by default on the VPN and direct some traffic.
- jopsen 9y agoWon't this leak DNS and won't lots of system process go avoid the HTTP_PROXY settings?
- kuon 9y agoI have my own DNS server on my local network. And yes, this is only for my browser. But this is intended. If you want to route all traffic to a vpn for a specific machine, you can use pf rules to forward an ip through another routing table.