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

    Squid3-dev not working

    Scheduled Pinned Locked Moved pfSense Packages
    12 Posts 3 Posters 1.8k 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.
    • J
      jakobeissler
      last edited by

      Ok, got it.

      • Disabled transparent proxy -> saved

      • Restarted service

      • Enabled transparent proxy -> saved

      • Restarted service

      Now it is working.

      Why to avoid this package? It has a "beta" status as has squid3… are there any other known problems?

      Thanks a lot.

      1 Reply Last reply Reply Quote 0
      • KOMK
        KOM
        last edited by

        Squid3-dev is marked as experimental and it seems to be pretty fragile.  There are lots of forum posts from people who got it into a situation where it was completely broken.  I had this same problem once and went back to Squid2.  I just recently moved up to Squid 3.1.20.

        However, if it is working for you then that's great.  I just wouldn't use it for production, or play with it too much once you have it stable.

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

          I was using squid3-dev for awhile myself but after a few firmware updates and other changes, it has been really been unstable. I've downgraded to squid3 and its been working fine for me.. The only feature I miss with squid3-dev is the built-in clamav. Other then that, I dont use any other features… Yeah, man-in-middle for SSL is nice if there is case for it but most networks probably wont been it...

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

            Squid3-dev is not longer marked as experimental, now it is beta as it is squid3.

            I have another question… since I got the transparent proxy working, it seems to not following my lan rules anymore. I have multi WAN, one for users and one for servers. Now all the traffic is getting through the default wangw.

            Any ideas?

            1 Reply Last reply Reply Quote 0
            • KOMK
              KOM
              last edited by

              Squid3-dev is not longer marked as experimental, now it is beta as it is squid3.

              Hmm, so it is.  I still wouldn't touch it.

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

                I'll take your advice and downgrade to squid3…. regarding the fw rules...  do you have any suggestions?

                1 Reply Last reply Reply Quote 0
                • KOMK
                  KOM
                  last edited by

                  I don't have any multiWAN experience, sorry, but I do know others have had issues sometimes.  Search these forums for 'squid multiwan' and see what comes up.

                  I know that transparent mode adds a hidden rule that redirects all port 80 traffic to port 3128 (Squid).

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

                    @jakobeissler:

                    Squid3-dev is not longer marked as experimental, now it is beta as it is squid3.

                    I have another question… since I got the transparent proxy working, it seems to not following my lan rules anymore. I have multi WAN, one for users and one for servers. Now all the traffic is getting through the default wangw.

                    Any ideas?

                    I'm not sure if it's possible using squid in transparent mode… I recall a couple of how-tos on the forum if you search but they were for non-transparent mode i believe

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

                      I downgraded to squid3, it is working fine as before. But I still have the problem with the lan rules… it was working before upgrading to squi3... now it does not.

                      Thanks.

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

                        Got it… in squid had to add a few custom opcions... like this:

                        acl LAN1 src 192.168.1.0/24;tcp_outgoing_address 164.67.234.231 LAN1;

                        All working now. Thanks.

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