Problem whit squidGuard

pozolero

Hello dvserg, I was checking what the buttons save and apply do, at some point the apply button stops the service, it says:
"squidGuard 1.4 started", then, "db update done" and then appears "squidGuard stopped" I mean, as if the button would do the opposite.

Otherwise, if I go to the tab "Status + Services" and restart the service, i get up to four messages that say "squidGuard 1.4 started" and "squidGuard ready for requests"

Is there a way to reverse what the apply button does? I mean, at some point in the upgrade, this button function was changed and was wrong, the service starts and then stops, instead of stop service, and start. :o

Kind regards

dvserg

Must be fixed
Pls reinstall XML and try the test.

kelsen

It's working now, thank you!

mauricioniñoavella

Hi, dvserg

It's working now, very well

thank for your colaboration and working

regards.

Mauricio Niño

kelsen

But XMLRCP Sync is giving an error.

Warning: Invalid argument supplied for foreach() in /usr/local/www/pkg_edit.php on line 423

Warning: fopen(/usr/local/pkg/squidguard_sync.xml): failed to open stream: No such file or directory in /etc/inc/xmlparse.inc on line 175

mauricioniñoavella

Hi dvserg,

The SquidGuard configuration changes are applied correctly using the Save and Apply buttons.

The problem, at least in 2.0.2, is that the Proxy filter SquidGuard: Groups Access Control List (ACL) on the Squid (Proxy server) configuration
Transparent proxy mode port 80 not filter

For example, if I uncheck the "Allow users on interface" on Squid (Proxy server). no filter SquidGuard
if I "Enabled" "Allow users on interface" if filtered SquidGuard

but it should work on Proxy server: Access control if I add "Allowed subnets", if I uncheck the "Allow users on interface" should filtered SquidGuard, but does not filter

Regards

Mauricio Niño

Thanks for your understanding.

pozolero

@dvserg:

Must be fixed
Pls reinstall XML and try the test.

Thanks a lot dvserg, it's working again…

I just have this question: If i update from 2.0.1 to 2.0.2 it's automatically gonna be working or i need to reinstall xml once updated?

Kindly regards

Nachtfalke

If you update pfsense, then all packages will be reinstalled automatically.
Further all changes are on pfsense server. Every new install will have the fix dvserg provided.

@kelsen
I tried that on two VMs 2.0.1 and didn't get that problem.
The code is the same as on freeradius2 package or on pfblocker. Just the files which should be synced are different.

Further I updated pfsense 2.0.1 to 2.0.2 and it was still working.
Try to reinstall the squidguard package - perhaps something is missing.

pozolero

Thanks for the info Nachtfalke :D

kelsen

Reinstalling the xml worked at least in one installation. Thx!