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

    pfSense and Linksys Velop config - not working properly

    Scheduled Pinned Locked Moved General pfSense Questions
    linksysvelop
    18 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.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      All of those lines showing NONE/409 are that issue.

      make sure both Sqiud and clients are using the same DNS. And preferably that should be Unbound in pfSense so the results are cached and both get the same thing.

      Steve

      R 1 Reply Last reply Reply Quote 0
      • R
        rheritier @stephenw10
        last edited by

        @stephenw10
        OMG...I really feel you'll hate me and think I'm so dumb...Just want to let you know that I have no background in computer and started to use pfsense about 1 month ago but I learn a lot, especially with each of your comments, so thanks!

        I've looked for DNS in both Squid and General Configuration...I think -but am not sure- that they are the same since there is nothing filled in Squid/Use Alternate DNS Servers for the Proxy Server... Below screenshot.

        Regarding "make sure client DNS is same as Squid" comment. Is the "Client" the device?
        If so, my device Wifi says "Configure DNS - Automatic".

        So so sorry for being that bad :(

        Sceensht 3.JPG Sceensht 4.JPG

        1 Reply Last reply Reply Quote 0
        • stephenw10S
          stephenw10 Netgate Administrator
          last edited by

          Mmm, do you have the DNS Resolver in forwarding mode? Check: Services > DNS Resolver.

          By default it's in resolving mode so it resolves directly and ignores whatever you have set there in general setup.
          If it's in forwarding mode it will use the servers configured there (Google's DNS) except you have
          'DNS Server Override' enabled so you would be using whatever your ISP is passing you.

          I would try setting 127.0.0.1 in the Squid DNS settings to be sure it is using Unbound (the Resolver) and not Google.

          Steve

          R 1 Reply Last reply Reply Quote 0
          • R
            rheritier @stephenw10
            last edited by

            So no, the forwarding mode isn't enabled.
            Should I enable it?
            Should I disable the "DNS Server Override" in the General Setup?
            And/or
            Add 127.0.0.1 in the Squid "Use Alternate DNS Servers for the Proxy Server"?

            I feel I'm close here thanks to you!

            Screenshot5.JPG

            1 Reply Last reply Reply Quote 0
            • stephenw10S
              stephenw10 Netgate Administrator
              last edited by

              No resolving mode should work fine.

              I would expect it to work with those settings but I would try setting the DNS in Squid to 127.0.0.1 to force it to also use Unbound.

              Steve

              R 2 Replies Last reply Reply Quote 0
              • R
                rheritier @stephenw10
                last edited by

                @stephenw10 Great, I'll put 127.0.0.1 in the Squid "Use Alternate DNS Servers for the Proxy Server" and run some test to see if this solves my issue.

                Thanks again Steve for your time, I really appreciated it!

                1 Reply Last reply Reply Quote 0
                • R
                  rheritier @stephenw10
                  last edited by

                  @stephenw10
                  Hi Steve,

                  So unfortunately it didn’t change anything.
                  When Squid server is enabled, I still have connectivity issues. Have to turn off wifi, use data, turn on wifi and I can access the website or app.

                  As said before, it is irregular and happen from time to time.

                  Any other idea?

                  Thanks!

                  1 Reply Last reply Reply Quote 0
                  • stephenw10S
                    stephenw10 Netgate Administrator
                    last edited by

                    Hmm, well if you're seeing those 409 errors it's because of a DNS resolution mismatch so you need to ensure both Squid the clients are resolving to the same IPs.

                    However I would argue you don't need Squid at all and should just disable it.

                    Steve

                    R 1 Reply Last reply Reply Quote 0
                    • R
                      rheritier @stephenw10
                      last edited by

                      @stephenw10
                      Hey!
                      So I don’t have error 409 or at least don’t see it often but have this error:
                      NONE/000 error:transaction-end-before-headers

                      Magbe it helps?

                      My issue is that squid is the main reason I use pfsense!

                      1 Reply Last reply Reply Quote 0
                      • stephenw10S
                        stephenw10 Netgate Administrator
                        last edited by

                        Mmm, well that's something else. I'm not aware of anything in particular that might cause that.
                        Check the Squid logs.

                        What are you using Squid for?

                        Steve

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