On 15/02/2012 7:54 p.m., Yucong Sun (叶雨飞) wrote:
Tor (without the browser part) basically provides a socks proxy ,
Vidalia translate socks proxy to http proxy, and the browser use that
http proxy to work.
So, to get your squid use it too, just launch tor and vidalia as
usual, have squid configure a cache_peer parent to that proxy
(localhost:<someport>), also never_direct allow all , and you will be
going through tor any minute.
The key to all of this is that the traffic goes from point A inside your
network where the clients can reach to some point B outside from which
the domains can be reached.
You could do this with any sort of relay or tunnel service. Squid only
handles HTTP, so the clients other traffic will stay broken. The type of
service you are looking for is usually seen with two Squid operating
with a VPN or TLS tunnel between them, using cache_peer to pass traffic
over it (works just as well as a routed packet path too if you add NAT).
SOCKS proxy is a good idea, as would be a VPN-like tunnel with yoru
routing sending packets to some outside server acting as a relay router.
Amos
On Tue, Feb 14, 2012 at 10:33 PM, Nguyen Hai Nam wrote:
Hi Squid guys,
We're using Squid 3.2 on Solaris 11 system smoothly, but few days ago our
ISP has had troubles with external Internet routing so we can't reach many
websites. I discovered that if I use Tor's browser I can open that websites
normally (yes, it's slow btw), at least we can open the website. So I think
we should cooperate between Squid and Tor to bring the Internet back for
users.
I'm not familiar with Tor switching network except using Tor's browser, so
it's great to hear your opion and if you guys know the already
configurations, I highly appreciate it.
Thank you,
~Neddy.
