Squidguard Problem

Nachtfalke

To disable squidguard do the following:
1.) On squidguard –> general settings disable the service, click save and then click apply. It should now be stopped.
2.) Check on squid --> custom options if the squidguard redirector program line was deleted

To filter websites you should remember the follwoing:
squid in transparent mode just filters port 80 (http). So squidguard can only block http websites.
squid in non-transparent mode filters port 80, 443 (https). So squidguard can block http and https websites.

So dependent on what you want to do you must configure squid the correct way.

dbt816

I have noticed that since upgrading to 2.02, making changes to the SquidGuard configuration and using either the "Apply" or "Save" buttons do not take effect unless I go and click the "Save" button on the Squid configuration page. It seems like all of the changes to SquidGuard are properly applied, but the Squid service is not being restarted, so SquidGuard is not getting restarted.

Nachtfalke

@dbt816:

I have noticed that since upgrading to 2.02, making changes to the SquidGuard configuration and using either the "Apply" or "Save" buttons do not take effect unless I go and click the "Save" button on the Squid configuration page. It seems like all of the changes to SquidGuard are properly applied, but the Squid service is not being restarted, so SquidGuard is not getting restarted.

You should not use "the one or the other" - you must use both. First "Save" and then "Apply".
But it could be correct - that on the first installation of squid and squidguard, or perhaps after a reboot, you have to click one time "Save" on squid config that the redirector_program command will be written to squid.conf. On pfsense 2.0.1 you do not have to do that. doing the steps on squidguard is enough. Didn't try 2.0.2

dbt816

You should not use "the one or the other" - you must use both. First "Save" and then "Apply".
But it could be correct - that on the first installation of squid and squidguard, or perhaps after a reboot, you have to click one time "Save" on squid config that the redirector_program command will be written to squid.conf. On pfsense 2.0.1 you do not have to do that. doing the steps on squidguard is enough. Didn't try 2.0.2

The SquidGuard configuration changes are applied correctly using the Save and Apply buttons. The problem, at least in 2.0.2, is that no changes actually take effect until you click the Save button on the Squid (Proxy server) configuration page or restart Squid from the command line.

For example, if I uncheck the "Enabled" checkbox in the SquidGuard configuration and click the Apply button, in 2.0.1 it would remove the redirector_program directive from the Squid configuration and stop the SquidGuard service (which would be reflected on the SquidGuard page by changing the "SquidGuard service state" to STOPPED in red letters). In 2.0.2, the redirector_program directive is properly removed, but the SquidGuard service is not actually stopped… the "SquidGuard service state" text is still STARTED and you can verify this from the command line. Only when you go over to the Squid configuration and click the Save button does the SquidGuard service actually stop.

This is the case for any changes you make to the SquidGuard configuration... the Save and Apply buttons successfully change the configuration, but the SquidGuard service is never restarted to pick up the changes until you click Save on the Squid configuration page.

Hopefully that's clear now :-)

mauricioniñoavella

same thing happens to me

The SquidGuard configuration changes are applied correctly using the Save and Apply buttons. The problem, at least in 2.0.2, is that no changes actually take effect until you click the Save button on the Squid (Proxy server) configuration page or restart Squid from the command line.

For example, if I uncheck the "Enabled" checkbox in the SquidGuard configuration and click the Apply button, in 2.0.1 it would remove the redirector_program directive from the Squid configuration and stop the SquidGuard service (which would be reflected on the SquidGuard page by changing the "SquidGuard service state" to STOPPED in red letters). In 2.0.2, the redirector_program directive is properly removed, but the SquidGuard service is not actually stopped… the "SquidGuard service state" text is still STARTED and you can verify this from the command line. Only when you go over to the Squid configuration and click the Save button does the SquidGuard service actually stop.

This is the case for any changes you make to the SquidGuard configuration... the Save and Apply buttons successfully change the configuration, but the SquidGuard service is never restarted to pick up the changes until you click Save on the Squid configuration page.

urgent help

thanks,

dbt816

for the description

Regards

Mauricio Niño

Nachtfalke

@dbt816
Of course, now it is ;D

Which version of squid do you use. squid2 or squid3 ?

mauricioniñoavella

the packages I use is

squid Network 2.7.9 pkg v.4.3.1
squidGuard Network Management 1.3_1 pkg v.1.9.1

thanks

Nachtfalke

dbt816

@mauricioniñoavella:

the packages I use is

squid Network 2.7.9 pkg v.4.3.1
squidGuard Network Management 1.3_1 pkg v.1.9.1

thanks

Nachtfalke

My package versions are the same

mauricioniñoavella

Hi dbt816,

Must be fixed
Pls reinstall XML and try the test.

Regards

Mauricio Niño

dbt816

@mauricioniñoavella:

Hi dbt816,

Must be fixed
Pls reinstall XML and try the test.

Regards

Mauricio Niño

Reinstalled and it upgraded to 1.4_4 pkg v.1.9.2. Problem solved :-) Many thanks to all!

svenv

Hello,

I still have a problem with my squidguard config.
The traffic is not blocked when it passes the FW. (Transparent mode- Bridged)

I have pushed all thev Save and Apply buttons on Squid and Squidguard but it seems that he dfoes not want to listen to me.

Any ideas ?

Thanks
Sven