Getting basic Squid running wasn't too hard at all, but there are some issues that make it not ready to use. Hopefully we can work through those issues here. But if you want to test it out at least, following these instructions.

Referred to Built on top of [http://www.redhatmagazine.com/2007/04/11/squid-in-5-minutes/ this articleapproach] for the approach. But note that there is a correction to the ''acl intranet src 192.168.0.0/24'' line, included above. He was missing ''src'' in that line.

In web browser, goto its settings or preferences and enter a '''Proxy Server''' using host/server URL as: hda. No username or password required. It may require setting the port number to 3128 (default Squid port), and setting the checkmark for all protocols to use the proxy.

*<s>Browsing to our custom HDA domains doesn't work, e.g. http://wiki or http://calendar.</s>There are various approaches to fixing this, but I don** '''SOLVED:''' adding ''dns_defnames on''t know how to do them so far.configuration did the trick

* Making it transparent, so clients don't need any web browser proxy server settings, is also very possible. You use iptables (also already installed and running) to forward port 80 traffic to the squid server port 3128. I tried but didn't get it working. I was sure how to remove the iptables entries, so I just turned that service off and all was back to normal.** Referring to [http://tldp.org/HOWTO/TransparentProxy-5.html TransparentProxy howothowto]** And more details from [http://wiki.squid-cache.org/SquidFaq/InterceptionProxy#head-182f30adede2d8daf8569aef5027629ed799b0d4 the Squid FAQ] and [http://wiki.squid-cache.org/SquidFaq/InterceptionProxy#head-935dbe4ef8ea8e21c1e04cc7753a09095c0d8285 here]** others say you can use DHCP or DNS to forward to the proxy too** more ipchains rules are listed [http://www.linuxhomenetworking.com/wiki/index.php/Quick_HOWTO_:_Ch32_:_Controlling_Web_Access_with_Squid here], haven't test it yet