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

    Squid Returned to Packages *** PLEASE TEST ***

    pfSense Packages
    46
    226
    138.4k
    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.
    • B
      bender
      last edited by

      I am testing pfSense 1.0.1-SNAPSHOT-12-28-2006 and squid 2.6.5_1-p6

      Everything seemed to be working fine until I tried adding some access control lists ;)  I tried entering a mac address in the "Unrestricted MAC Addresses" text box.

      Now when I enter: /usr/local/sbin/squid status
      at a shell prompt, I get:

      2007/01/04 20:50:37| aclParseAclLine: Invalid ACL type 'arp'
      FATAL: Bungled squid.conf line 40: acl unrestricted_macs arp "/var/squid/acl/unrestricted_macs.acl"
      Squid Cache (Version 2.6.STABLE5): Terminated abnormally.

      I believe that this error would occur when the configuration parameter: –enable-arp-acl
      was not included when squid was compiled.

      I haven't had a chance to dig through the php code yet to see if or where this might be missing but wanted to know if maybe I have missed something obvious before I do.

      Thanks.

      1 Reply Last reply Reply Quote 0
      • J
        Justinw
        last edited by

        To Sullrich:

        Webconfigurator is running on an off-port right around 38000

        1 Reply Last reply Reply Quote 0
        • S
          sullrich
          last edited by

          @Justinw:

          To Sullrich:

          Webconfigurator is running on an off-port right around 38000

          Strange.  Then I am not sure why it is giving that error.  Another squid guru would have to chime in.

          1 Reply Last reply Reply Quote 0
          • J
            Justinw
            last edited by

            well after the rc.d file is removed, squid still starts, and the errors for the most part disappear, I think its because it starts once, then it tries to start again, but it can't bind because those ports are already in use by the previous instance of squid.

            1 Reply Last reply Reply Quote 0
            • B
              bender
              last edited by

              @Justinw,

              Did you install squid from the command line, or did you use pfSense's package manager (latest version)? I didn't encounter the problem that you are seeing even when using the same versions. Have you tried resinstalling everything from scratch? As long as you save your config first, maybe that would be the fastest way to resolve your issue?

              1 Reply Last reply Reply Quote 0
              • S
                sullrich
                last edited by

                The rc.d problem was fixed in a recent snapshot.  Make sure your running something recent.

                1 Reply Last reply Reply Quote 0
                • J
                  Justinw
                  last edited by

                  The last attempt for me was on 1.0.1-SNAPSHOT-12-28-2006, latest squid package availble on the package manager.  I will try a scratch install again though and see if that fixes it.

                  Did you install squid from the command line, or did you use pfSense's package manager (latest version)? I didn't encounter the problem that you are seeing even when using the same versions. Have you tried resinstalling everything from scratch? As long as you save your config first, maybe that would be the fastest way to resolve your issue?

                  Are you running squid in transparent mode?

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

                    Install a version from http://snapshots.pfsense.com/FreeBSD6/RELENG_1/ to test with.

                    1 Reply Last reply Reply Quote 0
                    • J
                      Justinw
                      last edited by

                      I just tested it, I already had download the snapshot  ;) I've been keeping up on my reading.  I got it from the above address under updates and pfSense-Full-Update-1.0.1-SNAPSHOT-12-28-2006.tgz.  I got the same result (unless the image has been changed within the last 45 min), I'm going to switch back and work with it a little more.  Here is what I did so far.  I installed the 1.0.1 release, then I uploaded the newest snapshot (12-28), changed my webgui to 443 (https), installed squid from the package manager, turned on transparent mode.

                      I'll give you an update after I look at it a little more.

                      1 Reply Last reply Reply Quote 0
                      • S
                        sullrich
                        last edited by

                        @Justinw:

                        I just tested it, I already had download the snapshot  ;) I've been keeping up on my reading.  I got it from the above address under updates and pfSense-Full-Update-1.0.1-SNAPSHOT-12-28-2006.tgz.  I got the same result (unless the image has been changed within the last 45 min), I'm going to switch back and work with it a little more.  Here is what I did so far.  I installed the 1.0.1 release, then I uploaded the newest snapshot (12-28), changed my webgui to 443 (https), installed squid from the package manager, turned on transparent mode.

                        I'll give you an update after I look at it a little more.

                        You are right on.  Then there is some other issue lurking.  BTW: Those snapshots rebuild every hour, but no changes have been made.  You can check cvstrac for changes, then 45-60 minutes later you will have an updated snapshot that can be tested.

                        1 Reply Last reply Reply Quote 0
                        • J
                          Justinw
                          last edited by

                          Added to the steps in my previous post I added DNS servers to the general settings.  The messages I was recieving in prior posts still persists with the stock install with transparent mode running.

                          1 Reply Last reply Reply Quote 0
                          • B
                            bender
                            last edited by

                            @Justinw

                            Ya that is a weird one… I am also now using pfSense 1.0.1-SNAPSHOT-12-28-2006 and squid 2.6.5_1-p6 and yes I am running in transparent mode, but I tried it both ways and it still works for me:

                            Transparent:

                            2007/01/05 02:35:33| Loaded Icons.
                            2007/01/05 02:35:33| Accepting transparently proxied HTTP connections at 127.0.0.1, port 80, FD 12.
                            2007/01/05 02:35:33| Accepting proxy HTTP connections at 192.168.1.33, port 3128, FD 13.
                            2007/01/05 02:35:33| WCCP Disabled.
                            2007/01/05 02:35:33| Ready to serve requests.

                            Transparent off:

                            2007/01/06 02:40:19| Loaded Icons.
                            2007/01/06 02:40:19| Accepting proxy HTTP connections at 192.168.1.33, port 3128, FD 12.
                            2007/01/06 02:40:19| WCCP Disabled.
                            2007/01/06 02:40:19| Ready to serve requests.

                            Did you use the .iso image to install pfSense from scratch or are you installing it on an existing FreeBSD rig?

                            1 Reply Last reply Reply Quote 0
                            • N
                              nimda79
                              last edited by

                              I have my webgui on HTTPS, and put the proxy port on 80. I have a couple sites on the blacklist and they still come up. When I take it out of transparent proxy and enable proxy in my web browser I can't get to HTTPS websites unless I put them in my whitelist but I still can access sites in my blacklist. 1.0.1-SNAPSHOT-07-01-2007 is what I am running. Is there something that I am missing here or is this just broke still?

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

                                There have been no changes since p6. That is, I have not had time to troublshoot the acls since then.

                                1 Reply Last reply Reply Quote 0
                                • I
                                  ivanjong
                                  last edited by

                                  squid acls is still not working for now so the black list and whitelist should be not working for now. 1 more point on my system the squid start up is still buggy. it starts squid 2 times. and thus wont be able to auto start when pfsense boot. i need to click save on the webgui of pfsense for squid to make it run. i'll try to look into the problem later when i have time

                                  1 Reply Last reply Reply Quote 0
                                  • J
                                    Justinw
                                    last edited by

                                    @bender:

                                    @Justinw

                                    Ya that is a weird one… I am also now using pfSense 1.0.1-SNAPSHOT-12-28-2006 and squid 2.6.5_1-p6 and yes I am running in transparent mode, but I tried it both ways and it still works for me:

                                    Transparent:

                                    2007/01/05 02:35:33| Loaded Icons.
                                    2007/01/05 02:35:33| Accepting transparently proxied HTTP connections at 127.0.0.1, port 80, FD 12.
                                    2007/01/05 02:35:33| Accepting proxy HTTP connections at 192.168.1.33, port 3128, FD 13.
                                    2007/01/05 02:35:33| WCCP Disabled.
                                    2007/01/05 02:35:33| Ready to serve requests.

                                    Transparent off:

                                    2007/01/06 02:40:19| Loaded Icons.
                                    2007/01/06 02:40:19| Accepting proxy HTTP connections at 192.168.1.33, port 3128, FD 12.
                                    2007/01/06 02:40:19| WCCP Disabled.
                                    2007/01/06 02:40:19| Ready to serve requests.

                                    Did you use the .iso image to install pfSense from scratch or are you installing it on an existing FreeBSD rig?

                                    Thanks for the update bender, the install comes from the 1.0.1 release iso.  I will work with it more, it sounds like some other people are having a problem with it while others are not.  If I find out anything new I'll post an update.

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

                                      Afaik you have to use something newer than 1.0.1 release for squid to work correctly. Please update to a recent snapshot from http://snapshots.pfsense.com/FreeBSD6/RELENG_1/ and test again.

                                      1 Reply Last reply Reply Quote 0
                                      • J
                                        Justinw
                                        last edited by

                                        My snapshot at the time of the previous posts was 12-28, however bender wanted to know what my base load was from, that being the 1.0.1 release version and then I upgraded to the snapshot via the firmware upgrade…

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

                                          Since the squid.sh is used by the start, stop and restart service I will not remove that one.

                                          What I have done instead is implement a delay in the proxy monitor script to wait 5 seconds after launhing to trigger a squid start or not.

                                          This is reflected as version p7. I have also moved the proxy start script after our attempt to start it.

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

                                            Enter version p8.

                                            This should have working blacklist support.
                                            MAC acls are removed since they do not work with 2.6

                                            Please Test.

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post