Issue with SquidGuard LDAP Filtering
-
Re: squidguard stopped after activating LDAP
I have the exact same issue as the above posted back in October 2021 i.e. SquidGuard filters are working fine with standard blocking rules on the Common ACL and also tied down to IP addresses / usernames with the Group ACL rules.
However, as soon as I tick the box to enable the LDAP filter, populating the fields with relevant LDAP binding credentials, all filtering stops.
Although the services say they are still started in the GUI, I can see the SquidGuard service is set to stopped in the log files. This is without changing the rules in the Common or General ACL - basically all users can access any website.
If I then disable LDAP filtering, everything works again and I can see the SquidGuard service has started again.
So enabling LDAP filterting seems to stop the SquidGuard service from working, but there's no indication in the logs as to what the issue is. I have checked the config file and it looks identical to other config files I've seen on the internet where LDAP filtering is confirmed to be working.
Screenshot below shows the log file. Has anyone seen this? Is SquidGuard even still supported on pfSense any more?
pfSense version 22.05 (latest version using pfSense Plus)
Many thanks,
Antony
-
FYI - if anyone else has this issue, the package is not supported by Netgate and there doesn't seem to be any obvious answer as to why this happens. I've given up now and gone with a DNS filtering solution instead of using Squid Guard.
