Squid Proxy – Using Squid to Anonymize HTTP Traffic

httpPROXYsquid

I'm trying to set up a SQUID server on Ubuntu to anonymize all HTTP traffic.

The goal is to hide the source IP make all the requests appear to be generated from the SQUID porxy.

I tried with the deafult configuartion but is not working as expected. How should I edit the squid.conf file?

Thanks

Best Answer

Most likely, your problem is with the X-Forwarded-For: header that Squid inserts in the outgoing request. To remove it, use forwarded_for directive as described here:

http://www.squid-cache.org/Doc/config/forwarded_for/

Related Solutions

Squid 3.1 does not route traffic via ProxyChains

As a possible Rube Goldberg workaround, can't squid be configured to use a proxy itself? If so, and you want the various smart features of proxychains, you could run some other no-op proxy that works under proxychains. Maybe even an earlier version of squid installed in an alternate path and configured to do nothing:

squid-3.1 --> squid-3.0-noop --> proxychains

I.e. invoke proxychains /path/to/squid-3.0/bin/squid (with squid-3.0 configured to proxy request unmodified and listen on, say, port 12345), and then invoke squid-3.1 normally, but configure it to route all requests through localhost:12345.

It's convoluted, but it gets you the 3.1 features plus the proxychains features, at least until/unless some wiser soul figures out how to get it working directly.

Squid configuration change to accept http request on LAN

"No route to host" suggests that something else happened while you were configuring Squid. If you log into the machine running Squid (presumably 192.168.0.1), can you ping 192.168.0.16 from there?

Best Answer

Related Solutions

Squid 3.1 does not route traffic via ProxyChains

Squid configuration change to accept http request on LAN

Related Topic