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

    SquidGuard Target Categories and Groups ACL Sorting Problem

    Scheduled Pinned Locked Moved Cache/Proxy
    7 Posts 4 Posters 432 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.
    • W
      w.hackl
      last edited by

      Hi there ,
      on PfSense 2.7.2 with Squid Package 0.4.46 and SquidGuard Package 1.16.19 the following problem occurs :
      If you edit either Target Categories or Group ACL entries they are put on top of the list after saving the entry.
      This behaviour is new to me and is a error so I think.

      Could this be a incompatibility with the new php version used on 2.7.2 ?

      Regards Wolfgang

      JonathanLeeJ C 2 Replies Last reply Reply Quote 1
      • JonathanLeeJ
        JonathanLee @w.hackl
        last edited by JonathanLee

        @w-hackl you have to edit them in order that you want, I have seen this, should make a redmine for it. Again I am happy it works the order issues was not a problem to me, I just edit them until I get the order I want.

        Any time I edit anything I have to resave them each so I get my order back for target categories

        Screenshot 2024-06-22 at 17.06.06.png

        Make sure to upvote

        1 Reply Last reply Reply Quote 0
        • JonathanLeeJ
          JonathanLee
          last edited by JonathanLee

          https://redmine.pfsense.org/issues/15580

          I opened a Redmine ticket for it, Squid right now does not have any maintainers for pfSense, so it might take a while to get fixed.

          Bug #15580

          @marcosm @MatthewA1
          Have you also seen this when you fixed the php errors a couple years ago? MatthewA1 have you ever used Squid it’s a challenging set of code and has lots of puzzles if you want to attempt to maintain it with me, I take my C class next semester, I had to do many pre requisites to get to it so I should be able to help very soon with in the next year.

          Make sure to upvote

          M 1 Reply Last reply Reply Quote 0
          • JonathanLeeJ
            JonathanLee
            last edited by JonathanLee

            Also I found a couple other bugs 🐛

            https://redmine.pfsense.org/issues/15410

            https://redmine.pfsense.org/issues/15381

            Make sure to upvote

            1 Reply Last reply Reply Quote 0
            • M
              MatthewA1 @JonathanLee
              last edited by

              @JonathanLee I've not ever really used Squid, so not sure I would be much help. From the other thread, however, it seems like Squid itself is still maintained, it's just someone needs to take charge of it for pfSense specifically. I'm not sure what all problems it has working with pfSense right now, but probably that's more PHP frontend and configuration file generation stuff than C.

              JonathanLeeJ 1 Reply Last reply Reply Quote 1
              • JonathanLeeJ
                JonathanLee @MatthewA1
                last edited by

                @MatthewA1 yes it is all generic PHP based stuff, it’s updated just simple things like Squid changed how to access the status page, there is also an issue with certificates but I am still confused as what the underline change is that causes the errors.

                It’s my favorite package you can do URL blocking and you can block specific sub URLs for websites, keywords all sorts of stuff. I am glad it is still accessible, again the developers of squid always respond to email questions also from the email server they have. My main concern is the status page.

                I am so happy 6.6 is part of pfSense 24 however some small changes are made in 6.6

                cache_object://URL Scheme is not removed in Squid-6
                cache_object://hostname/request@password

                Is used to check status inside the pfSense GUI for this package

                It has been replaced with
                http://hostname/squid-internal-mgr URL-prefix.

                Therefore it will now say access denied when checking status

                The status page needs to be updated to reflect the new URL scheme

                I spoke with Squid user support and they have confirmed the new URL scheme.

                Again thanks for taking the time to look at the NTP thing. I am taking a C class very soon I finally can enroll in it now.

                Ref:
                https://wiki.squid-cache.org/Features/CacheManager/CacheObjectScheme

                I have a redmine for this one open

                https://redmine.pfsense.org/issues/15410

                Make sure to upvote

                1 Reply Last reply Reply Quote 0
                • C
                  CZvacko @w.hackl
                  last edited by

                  @w-hackl said in SquidGuard Target Categories and Groups ACL Sorting Problem:

                  put on top of the list

                  I can confirm that, it didnt happen in 2.6.x ver and appear on 2.7.x

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