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

    After Update to 22.05 Squid is no longer getting traffic

    Cache/Proxy
    2
    7
    1.8k
    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.
    • ghostshellG
      ghostshell
      last edited by ghostshell

      I only get ERROR: Directive 'dns_v4_first' is obsolete., after updating to 22.05 squid is enabled, its running, but I see no traffic from any device going through it. It not blocking anything in the blacklist and all categories in squidguard are not working either. I see in status that 1 client is connected, should be more and HTTP requests are happening, but blocking is no longer working, I came from CE 2.6 and it was working perfectly. At least pfblocker will block some, but I was using squid as if I change my laptop DNS that no longer works so squid was a backup in case someone did that to bypass the filter.

      1 Reply Last reply Reply Quote 0
      • ghostshellG
        ghostshell
        last edited by

        found a bug with some of the fields, if I add one item to one of the lists it works, if I add 2 it stops, also the ACLs are not working, one of the blocked sites will be blocked, but all others will work

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

          @ghostshell did you clear the cache on squid ? Also what does the logs say in squid guard?

          Make sure to upvote

          ghostshellG 1 Reply Last reply Reply Quote 0
          • ghostshellG
            ghostshell @JonathanLee
            last edited by

            @jonathanlee I went as far as disabling the cache which is what its at currently, right now if I add more that one domain to the bypass it stops, remove all but one it started taking traffic

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

              @ghostshell is this bypass list set up as an aliases? That works better because the DNS lookups can be looked at in the logs that way.

              Make sure to upvote

              ghostshellG 1 Reply Last reply Reply Quote 0
              • ghostshellG
                ghostshell @JonathanLee
                last edited by

                @jonathanlee looks like the streaming services domains has changed, i looked them up outside my net and they do not resolve, found them using squid a while back, looks like the newest version of squid actually tries to resolve them so I verified each one and back to working

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

                  @ghostshell Amazons Prime changed yesterday for me it was the same for 3 years now it has .am in the domain. I can see them resolve in logs under DNS resolver it will show them pull and resolve every 5 mins.

                  resolver.PNG

                  Make sure to upvote

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