Internet Related/Filtering/Firewall Thread, Squid physical configuration in Technical; Originally Posted by Ignatius
EDIT - I've now noticed that https traffic is blocked if I have the Squid box ...
7th February 2011, 11:53 PM #16
This thread might come in handy:
Originally Posted by Ignatius
I'd love to report that the above was produced after a careful study of the IPTables documentation, and came from my deep understanding of all things routing and filtering related, but as it happens I seem to remember spending a weekend cutting-and-pasting stuff cobbled together from assorted Google searches until it worked...
Edit: the above is now 3 years old, glennda's idea might well now work if support for filtering HTTPS has been added to Squid.
Thanks to dhicks from:
Ignatius (8th February 2011)
IDG Tech News
8th February 2011, 12:34 PM #17
Thank you both for your input. As far as I know, Squid doesn't work with https. I'll check out the thread from 2007. I figured that I'd have to have some iptables rules to check the destination ports. If they're 25, 110 or 443, send the traffic straight to the real DG (172.19.0.1) but, if the destination port is 80, send the traffic to port 3128 of the same box (I have the Squid and iptables on the same box).
If this logic is correct, I might need some help with the iptables syntax!
By Duke5A in forum Internet Related/Filtering/Firewall
Last Post: 13th August 2013, 04:20 PM
By Number6 in forum Internet Related/Filtering/Firewall
Last Post: 10th August 2010, 01:31 PM
By bart21 in forum Internet Related/Filtering/Firewall
Last Post: 23rd April 2010, 10:12 AM
By Cragzman in forum *nix
Last Post: 22nd October 2008, 03:59 PM
By JamesC in forum Thin Client and Virtual Machines
Last Post: 27th February 2008, 12:11 AM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)