Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Is the squidguard package stable at the moment…..

    Scheduled Pinned Locked Moved pfSense Packages
    38 Posts 6 Posters 18.3k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • H
      heiko
      last edited by

      Hello,
      last Test:

      First of all, i think the acl page have problems. If i delete ACL Lines, the Line shows a blank config. If i restarted squidguard errors appears.

      -  Source not found….

      Now i edit the acl line and filling a few words in it and checked disable. After that, i have made a restart at the generel page with clicing the apply button.

      For me it looks Ok, but also nothing content was blocked...

      /var/squidGuard/log/sg_configurator.log
      17.02.2008 20:10:25 : sg_reconfigure_user_db: -- add moskau expressions ''spiegel|gmx''
      17.02.2008 20:10:25 : sg_rebuild_db: Begin with path '/var/db/squidGuard'.
      17.02.2008 20:10:25 : sg_create_rebuild_config: Begin with dbhome='/var/db/squidGuard'.
      17.02.2008 20:10:25 : sg_create_rebuild_config: -- added item 'usr_moskau' = '/var/db/squidGuard/moskau'.
      17.02.2008 20:10:25 : sg_redirector_base_url: select redirector base url (https://192.168.6.1:61003/sgerror.php?url=404&a=%a&n=%n&i=%i&s=%s&t=%t&u=%u)
      17.02.2008 20:10:25 : sg_redirector_base_url: End.
      17.02.2008 20:10:25 : sg_create_rebuild_config: End.
      17.02.2008 20:10:25 : sg_rebuild_db: Create temporary config '/tmp/squidGuard_rebuild.conf_usrdb'.
      17.02.2008 20:10:25 : sg_rebuild_db: Started SH script '/tmp/squidGuard_db_rebuild.sh_usrdb'.
      17.02.2008 20:10:25 : sg_rebuild_db: End.
      17.02.2008 20:10:25 : sg_remove_unused_db_entries: begin
      17.02.2008 20:10:25 : sg_remove_unused_db_entries: end
      17.02.2008 20:10:25 : sg_reconfigure_user_db: end.
      17.02.2008 20:10:25 : sg_build_config: create squidGuard config.
      17.02.2008 20:10:25 : sg_build_config: checking configuration data.
      17.02.2008 20:10:25 : sg_build_config: add times
      17.02.2008 20:10:25 : sg_build_config: add sources
      17.02.2008 20:10:25 : sg_build_config: add blacklist entries
      17.02.2008 20:10:25 : sg_build_config: added:
      ads; aggressive; audio-video; drugs; gambling; hacking; mail; porn; proxy; violence; warez;

      17.02.2008 20:10:25 : sg_build_config: add destinations
      17.02.2008 20:10:25 : sg_build_config: added:
      moskau;

      17.02.2008 20:10:25 : sg_build_config: add ACL
      17.02.2008 20:10:25 : sg_build_config: added:
      test1; test;

      17.02.2008 20:10:25 : sg_build_config: add Default
      17.02.2008 20:10:25 : sg_redirector_base_url: select redirector base url (https://192.168.6.1:61003/sgerror.php?url=http://www.google.ru&a=%a&n=%n&i=%i&s=%s&t=%t&u=%u)
      17.02.2008 20:10:25 : sg_redirector_base_url: End.
      17.02.2008 20:10:26 : sg_redirector_base_url: select redirector base url (https://192.168.6.1:61003/sgerror.php?url=404%20overtime&a=%a&n=%n&i=%i&s=%s&t=%t&u=%u)
      17.02.2008 20:10:26 : sg_redirector_base_url: End.
      17.02.2008 20:10:26 : sg_reconfigure: generate squidGuard config and save to /usr/local/etc/squidGuard/squidGuard.conf.
      17.02.2008 20:10:26 : squid_reconfigure: begin
      17.02.2008 20:10:26 : squid_reconfigure: remove old redirector options from Squid config.
      17.02.2008 20:10:26 : squid_reconfigure: add new redirector options to Squid config.
      17.02.2008 20:10:29 : sg_reconfigure: end.
      17.02.2008 20:10:29 : sg_init: ext initialization squidguard_config
      17.02.2008 20:11:14 : sg_init: ext initialization squidguard_config
      17.02.2008 20:11:14 : sg_init: ext initialization squidguard_config
      17.02.2008 20:16:49 : sg_init: ext initialization squidguard_config
      17.02.2008 20:17:01 : sg_init: ext initialization squidguard_config
      17.02.2008 20:17:01 : sg_init: ext initialization squidguard_config
      17.02.2008 20:17:23 : sg_init: ext initialization squidguard_config
      17.02.2008 20:17:26 : sg_init: ext initialization squidguard_config
      17.02.2008 20:18:10 : sg_init: ext initialization squidguard_config
      17.02.2008 20:18:10 : sg_init: ext initialization squidguard_config

      I don´t know where my config is buggy. Maybe, take a look at the screenshots
      I don´t use the transparent proxy feature but local user authentication.

      Greetings
      Heiko

      ScreenShot003.jpg
      ScreenShot003.jpg_thumb
      ScreenShot004.jpg
      ScreenShot004.jpg_thumb
      ScreenShot005.jpg
      ScreenShot005.jpg_thumb

      1 Reply Last reply Reply Quote 0
      • C
        ColdFusion
        last edited by

        I'm getting something similar…all was well until recently..... After awhile the error stops showing and Squidguard is apparently running, but no content gets blocked. If I re-install I get the same issue.

        Warning: implode(): Bad arguments. in /usr/local/pkg/squidguard_configurator.inc on line 367 Warning: Cannot modify header information - headers already sent by (output started at /usr/local/pkg/squidguard_configurator.inc:367) in /usr/local/www/pkg_edit.php on line 35

        1 Reply Last reply Reply Quote 0
        • D
          dvserg
          last edited by

          Thanks. I will test this too.

          SquidGuardDoc EN  RU Tutorial
          Localization ru_PFSense

          1 Reply Last reply Reply Quote 0
          • A
            aaron
            last edited by

            I occasionally get the implode type of error when I've deleted a destination group or blacklist group and haven't gone through all the ACLs to update them.  Perhaps it's a similar problem?

            Also, heiko, I am using squidGuard in a production environment and am happy with the results.

            1 Reply Last reply Reply Quote 0
            • C
              ColdFusion
              last edited by

              This happens on fresh install with no destination groups deleted. It happens after uploading Blacklist or hitting apply changes. Then error goes away and no content is blocked.

              1 Reply Last reply Reply Quote 0
              • D
                dvserg
                last edited by

                Thanks for previous bug-report's.
                I fix it (may be  >:( ) and update sources.
                If possible check this bugs now.

                Also i remake ACL-ordering code for more stable.

                SquidGuardDoc EN  RU Tutorial
                Localization ru_PFSense

                1 Reply Last reply Reply Quote 0
                • C
                  ColdFusion
                  last edited by

                  Seems to be working now. Since the last few changes, I can no longer access the blocked log report tab….I get block_log report disabled. The other thing I'm trying to figure out is how to whitelist certain sites that are in the blacklist...

                  1 Reply Last reply Reply Quote 0
                  • D
                    dvserg
                    last edited by

                    I can no longer access the blocked log report tab....I get block_log report disabled.
                    

                    I disable this function. After short time i return to renew this code with more quick algorithm (i houpe).
                    If you need this now - you can modify squidGuard.php:

                    • comment with '#' line 710
                    #                                $slog .= 'block_log report disabled';  
                    
                    • delete '/' and '/' symbols in  711 and 747 lines.

                    ps this actual on today time; in next time code can changed.

                    SquidGuardDoc EN  RU Tutorial
                    Localization ru_PFSense

                    1 Reply Last reply Reply Quote 0
                    • H
                      heiko
                      last edited by

                      Sorry dvserg, i wouldn´t set off an avalanche with my question.
                      Greetings
                      Heiko

                      1 Reply Last reply Reply Quote 0
                      • C
                        ColdFusion
                        last edited by

                        I finally figured out how to whitelist a url that's blacklisted. In destination tab I created a whitelist and blacklist. When I put a url that I want to add to the blacklist it worked. However when I put a url that I want to whitelist it still didn't work. I looked in the squidgaurd config and found this:
                        dest whitelist {
                        domainlist whitelist/domains
                        urllist whitelist/urls
                        log block.log
                        }

                        dest Blacklist {
                        domainlist Blacklist/domains
                        urllist Blacklist/urls
                        redirect http://192.168.0.1/sgerror.php?url=http://www.yahoo.com&a=%a&n=%n&i=%i&s=%s&t=%t&u=%u
                        log block.log
                        }

                        acl {
                        default {
                        pass !blk_BL_adv !blk_BL_aggressive !blk_BL_chat !blk_BL_drugs !blk_BL_gamble !blk_BL_hacking !blk_BL_porn !blk_BL_redirector !blk_BL_spyware !blk_BL_tracker !blk_BL_warez whitelist !Blacklist all
                        redirect http://192.168.0.1/sgerror.php?url=http://www.yahoo.com&a=%a&n=%n&i=%i&s=%s&t=%t&u=%u
                        }
                        }

                        However the my whitelist and blacklist were added to the back of the config. I edited my xml config and replaced it with this:
                        dest whitelist {
                        domainlist whitelist/domains
                        urllist whitelist/urls
                        log block.log
                        }

                        dest Blacklist {
                        domainlist Blacklist/domains
                        urllist Blacklist/urls
                        redirect http://192.168.0.1/sgerror.php?url=http://www.yahoo.com&a=%a&n=%n&i=%i&s=%s&t=%t&u=%u
                        log block.log
                        }

                        acl {
                        default {
                        pass whitelist !Blacklist !blk_BL_adv !blk_BL_aggressive !blk_BL_chat !blk_BL_drugs !blk_BL_gamble !blk_BL_hacking !blk_BL_porn !blk_BL_redirector !blk_BL_spyware !blk_BL_tracker !blk_BL_warez all
                        redirect http://192.168.0.1/sgerror.php?url=http://www.yahoo.com&a=%a&n=%n&i=%i&s=%s&t=%t&u=%u
                        }
                        }

                        I put my whitelist and blacklist in front of the file…..it now works.

                        1 Reply Last reply Reply Quote 0
                        • D
                          dvserg
                          last edited by

                          @ColdFusion:

                          I put my whitelist and blacklist in front of the file…..it now works.

                          You wanted say, what SG dest order has important meaning?
                          I not found information in manuals about this
                          If you can - please help find it fo me - this is really important.
                          Thanks.

                          SquidGuardDoc EN  RU Tutorial
                          Localization ru_PFSense

                          1 Reply Last reply Reply Quote 0
                          • C
                            ColdFusion
                            last edited by

                            Maybe I should clarify. The order seems important. If you look at the example above I just moved the whitelist to the front. The additional blacklist created doesn’t matter the order. I found the info at http://squidguard.shalla.de/Doc/configure.html

                            1. Whitelisting

                            Sometimes there is a demand to allow specific URLs and domains although they are part of the blocklists for a good reason. In this case you want to whitelist these domains and URLs.
                            Defining a whitelist
                            dest white {
                            domainlist white/domains
                            urllist white/urls
                            }

                            acl {
                                    default {
                                            pass    white !adv !porn !warez all
                                            redirect http://localhost/block.html
                                            }

                            }

                            Basically the whitelist works before the blacklist.

                            1 Reply Last reply Reply Quote 0
                            • C
                              ColdFusion
                              last edited by

                              I guess one would get the same result if you named your whitelist something like AA….first order seems to be ads.....Example AA ads aggressive......

                              acl {
                              default {
                              pass AA !blk_adv !blk_BL_aggressive !blk_BL_chat !blk_BL_drugs !blk_BL_gamble !blk_BL_hacking !blk_BL_porn !blk_BL_redirector !blk_BL_spyware !

                              didn't try this though but should work.

                              John

                              1 Reply Last reply Reply Quote 0
                              • D
                                dvserg
                                last edited by

                                Thanks!!!
                                English causes some difficulties for me, and nuances sometimes disappear  :-\

                                A chnange config generator AS:
                                pass <allow_rules><block_rules>all|none</block_rules></allow_rules>

                                SquidGuardDoc EN  RU Tutorial
                                Localization ru_PFSense

                                1 Reply Last reply Reply Quote 0
                                • A
                                  acidrop
                                  last edited by

                                  After a de-install and reinstallation of SG i get the following error each time i press apply in the general settings tab:

                                  Warning: implode(): Bad arguments. in /usr/local/pkg/squidguard_configurator.inc on line 312 Warning: Cannot modify header information - headers already sent by (output started at /usr/local/pkg/squidguard_configurator.inc:312) in /usr/local/www/pkg_edit.php on line 35

                                  ..and nothing is blocked anymore :(

                                  pls help!

                                  1 Reply Last reply Reply Quote 0
                                  • C
                                    ColdFusion
                                    last edited by

                                    @acidrop:

                                    After a de-install and reinstallation of SG i get the following error each time i press apply in the general settings tab:

                                    Warning: implode(): Bad arguments. in /usr/local/pkg/squidguard_configurator.inc on line 312 Warning: Cannot modify header information - headers already sent by (output started at /usr/local/pkg/squidguard_configurator.inc:312) in /usr/local/www/pkg_edit.php on line 35

                                    ..and nothing is blocked anymore :(

                                    pls help!

                                    I had the same problem. I had to reinstall the package xml…then that cleared up the error and everything is working fine.

                                    1 Reply Last reply Reply Quote 0
                                    • C
                                      ColdFusion
                                      last edited by

                                      Well, I spoke to soon….There were changes to SquidGuard today, so  I downloaded it again on a test box to see if I get the error....and I am.......Warning: implode(): Bad arguments. in /usr/local/pkg/squidguard_configurator.inc on line 312 Warning: Cannot modify header information - headers already sent by (output started at /usr/local/pkg/squidguard_configurator.inc:312) in /usr/local/www/pkg_edit.php on line 35

                                      1 Reply Last reply Reply Quote 0
                                      • D
                                        dvserg
                                        last edited by

                                        Fixed Please update package.  :-[

                                        SquidGuardDoc EN  RU Tutorial
                                        Localization ru_PFSense

                                        1 Reply Last reply Reply Quote 0
                                        • A
                                          acidrop
                                          last edited by

                                          thnx for the quick fix!  ;D

                                          1 Reply Last reply Reply Quote 0
                                          • D
                                            dvserg
                                            last edited by

                                            @acidrop:

                                            thnx for the quick fix!  ;D

                                            I have found this yesterday and has corrected, but has forgotten to save to pfsense.com

                                            SquidGuardDoc EN  RU Tutorial
                                            Localization ru_PFSense

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.