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

    Squid and ACLs

    Scheduled Pinned Locked Moved Cache/Proxy
    squidupdatesaclip addressesprivate address
    19 Posts 3 Posters 3.1k 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.
    • JonathanLeeJ
      JonathanLee @mcury
      last edited by

      @mcury thanks for the information

      Make sure to upvote

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

        @mcury is port 8080 used by something else? My GUI is currently set to port 8080.

        Make sure to upvote

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

          @JonathanLee said in Squid and ACLs:

          @mcury is port 8080 used by something else? My GUI is currently set to port 8080.

          No, not by default.
          But some websites use that port, so it is usual to see users include that port in the allowed ports in the Squid settings.

          If its not there, then, I don't think this is the problem.

          Just to be clear, my suspicious is that the NAT that transparent proxy creates is intercepting that port when you are accessing the GUI, and sending it to the proxy 3128.

          dead on arrival, nowhere to be found.

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

            @mcury I got it. It should also work to add bypass 192.168.1.1:8080 on the Squid bypass settings right 👍

            Make sure to upvote

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

              @JonathanLee said in Squid and ACLs:

              It should also work to add bypass 192.168.1.1:8080 on the Squid bypass settings right 👍

              Yes, just bypass connections to destination 192.168.1.1.

              Usually, most of the times if not always, you don't want to proxy connections to local networks, so I would bypass everything to:

              10.0.0.0/8
              172.16.0.0/12
              192.168.0.0/16

              As far as I remember, you said a few weeks ago when we were trying to fix your Nintendo Switch problem, that you use both modes, transparent and explicit.

              So, you need to make sure that you bypass these networks for both methods.

              For transparent mode, you need to include those networks in Squid configuration, or if you created the NAT manually, include those networks there, you can use that reverse destination alias as previously mentioned in that thread.

              For explicit mode, you would need to set it in the browser settings, or through the PAC file.

              dead on arrival, nowhere to be found.

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

                Thanks I got the PAC file working. I bet 23.05.01 had some default Netgate proxy rules that 23.09 doesn't include.

                Make sure to upvote

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

                  @JonathanLee said in Squid and ACLs:

                  Thanks I got the PAC file working. I bet 23.05.01 had some default Netgate proxy rules that 23.09 doesn't include.

                  hm.. 🤔 could be but I don't think so.

                  dead on arrival, nowhere to be found.

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

                    It was this old separators that were deleted however still listed in the 23.05.01 config.xml file.

                    It mixed up every rule on the config.xml side and left it looking correct on the GUI side. I just deleted them and it fixed it for my 23.09.01

                    Screenshot 2023-12-15 at 10.19.31 PM.png

                    Screenshot 2023-12-15 at 10.53.07 PM.png

                    Make sure to upvote

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

                      @JonathanLee said in Squid and ACLs:

                      It was this old separators that were deleted however still listed in the 23.05.01 config.xml file.

                      It mixed up every rule on the config.xml side and left it looking correct on the GUI side. I just deleted them and it fixed it for my 23.09.01

                      Screenshot 2023-12-15 at 10.19.31 PM.png

                      Screenshot 2023-12-15 at 10.53.07 PM.png

                      Oh, that certainly wasn't a easy shot, good work =)

                      dead on arrival, nowhere to be found.

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

                        @mcury I also had to disable some ethernet rules that all the sudden showed a lot of activity

                        Screenshot 2023-12-16 at 8.38.44 AM.png

                        Make sure to upvote

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