Buggy squidGuard on a so called high end firewall, yea right! Please HELP
-
Dear, PF users,
I am having all sorts of problems with squid3/squidguard.
I am using Shallalist and even though I had it working before before my upgrade to x64, at the moment the filtering itself doesn't respond to what I have denied or allowed.
I tested it with deny access to all but even then, it blocks websites without a specific target group defined, tried to clear web browser cache, restart the webbrowser, cleared the local squid cache, might have helped, but who knows, right?I tried to disable squidguard and/or squid to watch the difference, and it stills trying to play games with me, till I have enough and disable the whole thing.
Now I can hear you saying, save this, save that, then apply, maybe you should have done that first then enable the daemon, bla, bla bla,…
The thing is that the whole picture doesn't feel right. >:(
Who really wants this sort of crap on a so called Enterprise grade firewall, unless I get it somehow to work so it doesn't get too embarrassing? :-[
;D ;DCreate a custom Dummy target categorie :D :D
Well yeah, it's dumb.
Does anyone have a clue how I can sort this one out?
Thank you
-
So, you've made a custom Target Category and you made sure to hit Apply on the General tab after making all of your changes?
-
This is an example of the error.
Even the cisco website seems to be blocked.
Don't know to which category that applies to ::)
Plain stupid ???
-
Click on "Common ACL".
Click on "Target Rules List".
Scroll all the way down and change your "Default Access [all]" from Deny to Allow. -
That gets rid of the errors, but also defeats its purpose.
Why should I do that?
Thank you