Squid3 and squidguard not intercepting traffic or blocking blacklist
-
I have squid 3 installed and squidguard with squid3 installed. Squid is in transparent mode and squidguard has default access set to deny.
Nothing is being denied, I'm assuming traffic isn't even going through the proxy. I have tried to uninstall/reinstall squid several times and nothing is ever blocked via squidguard.
Any ideas?
-
Not sure if there are any differences between squid(guard)2 and 3 but in general you should do the following on squidguard:
On the "Common ACL" - if you do not have any other Group ACLs - you have to select the target categories and set it to "deny" or "allow". After that you need to click "Save" on "Common ACL".
After that you have to click "Save" and then "Apply" on the "General settings". This is important as far as I know.
-
Had the same issue today with squidguard3-squid. The issue was the path being used for squidguard.conf was not correct. A workaround:
ln -s /usr/pbi/squidguard-squid3-amd64/etc/squidGuard/squidGuard.conf /usr/pbi/squidguard-squid3-amd64/etc/squid/squidGuard.conf
Then rebuild blocklist DB manually with:
squidGuard -db -C all
-
With 2.1 in beta testing for such a long time its surprising to see the packages never really been tested on it to ensure they are compatible with other linked or dependent packages.
One thing I dont like is some dependent packages are pulled from FreeBSD servers or some other non dependable servers. Packages and all dependent files need to be stored on the same server for easier troubleshooting.
-
Had the same issue today with squidguard3-squid. The issue was the path being used for squidguard.conf was not correct. A workaround:
ln -s /usr/pbi/squidguard-squid3-amd64/etc/squidGuard/squidGuard.conf /usr/pbi/squidguard-squid3-amd64/etc/squid/squidGuard.conf
Then rebuild blocklist DB manually with:
squidGuard -db -C all
I had had ineffective squidGuard set up for a while. Investigating today and this fixed it. I'm not sure if I had some config sitting around from messing with different combinations of squid 2 and 3 and their respective squidguards over time and something hanging around. But anyway, I also had a messed up squidGuard.conf path and the ln -s fixed it.