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

    22.05-RELEASE (amd64) Unable to check for updates?

    Scheduled Pinned Locked Moved
    General pfSense Questions
    6
    61
    14.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.
    • S
      SteveITS Rebel Alliance @TAC57
      last edited by

      @TAC57 if you’re forwarding to Quad9 it sounds like that isn’t working…Snort block maybe? Try turning off forwarding or use a different DNS.

      Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
      When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
      Upvote 👍 helpful posts!

      TAC57T 2 Replies Last reply Reply Quote 0
      • TAC57T
        TAC57 @SteveITS
        last edited by

        @SteveITS In System / General Setup / DNS Servers I changed 9.9.9.9 to 1.1.1.1 and ran the command above with @1.1.1.1 and got the following:

        ;; communications error to 1.1.1.1#53: timed out
        ;; communications error to 1.1.1.1#53: timed out
        ;; communications error to 1.1.1.1#53: timed out
        ;; no servers could be reached

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

          Can you query either of those from a host behind pfSense?

          TAC57T 1 Reply Last reply Reply Quote 0
          • TAC57T
            TAC57 @stephenw10
            last edited by

            @stephenw10
            This from my windows command prompt:
            Microsoft Windows [Version 10.0.19045.3031]
            (c) Microsoft Corporation. All rights reserved.

            C:\Users\Tom>ping 9.9.9.9

            Pinging 9.9.9.9 with 32 bytes of data:
            Reply from 9.9.9.9: bytes=32 time=266ms TTL=57
            Reply from 9.9.9.9: bytes=32 time=15ms TTL=57
            Reply from 9.9.9.9: bytes=32 time=15ms TTL=57
            Reply from 9.9.9.9: bytes=32 time=16ms TTL=57

            Ping statistics for 9.9.9.9:
            Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
            Approximate round trip times in milli-seconds:
            Minimum = 15ms, Maximum = 266ms, Average = 78ms

            C:\Users\Tom>ping 1.1.1.1

            Pinging 1.1.1.1 with 32 bytes of data:
            Reply from 1.1.1.1: bytes=32 time=267ms TTL=57
            Reply from 1.1.1.1: bytes=32 time=16ms TTL=57
            Reply from 1.1.1.1: bytes=32 time=15ms TTL=57
            Reply from 1.1.1.1: bytes=32 time=15ms TTL=57

            Ping statistics for 1.1.1.1:
            Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
            Approximate round trip times in milli-seconds:
            Minimum = 15ms, Maximum = 267ms, Average = 78ms

            C:\Users\Tom>ping 8.8.8.8

            Pinging 8.8.8.8 with 32 bytes of data:
            Reply from 8.8.8.8: bytes=32 time=14ms TTL=115
            Reply from 8.8.8.8: bytes=32 time=13ms TTL=115
            Reply from 8.8.8.8: bytes=32 time=14ms TTL=115
            Reply from 8.8.8.8: bytes=32 time=14ms TTL=115

            Ping statistics for 8.8.8.8:
            Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
            Approximate round trip times in milli-seconds:
            Minimum = 13ms, Maximum = 14ms, Average = 13ms

            C:\Users\Tom>ping acb.netgate.com

            Pinging acb.netgate.com [208.123.73.212] with 32 bytes of data:
            Reply from 208.123.73.212: bytes=32 time=39ms TTL=51
            Reply from 208.123.73.212: bytes=32 time=39ms TTL=51
            Reply from 208.123.73.212: bytes=32 time=38ms TTL=51
            Reply from 208.123.73.212: bytes=32 time=39ms TTL=51

            Ping statistics for 208.123.73.212:
            Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
            Approximate round trip times in milli-seconds:
            Minimum = 38ms, Maximum = 39ms, Average = 38ms

            1 Reply Last reply Reply Quote 0
            • TAC57T
              TAC57 @SteveITS
              last edited by TAC57

              @SteveITS I have DNS resolver enabled. What is the easiest way to turn all this off?

              And this has to be related:
              An error occurred while uploading the encrypted Netgate pfSense Plus configuration to https://acb.netgate.com/save ( Unable to resolve acb.netgate.com ) @ 2023-05-28 16:49:05

              2988e27e-e34c-4d91-9a68-b6c85b940b33-image.png

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

                Do you have the DNS resolver set to forwarding mode though?

                If you do try just unchecking that so it resolves directly.

                TAC57T 1 Reply Last reply Reply Quote 0
                • TAC57T
                  TAC57 @stephenw10
                  last edited by

                  @stephenw10 It was, unchecking made no difference.

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

                    Hmm. Just to be clear is that failing to resolve any host? Even when resolving directly?

                    That sounds like it must be something blocking DNS requests from the firewall. But I expect anything doing that to apply to NAT'd traffic from clients behind it also. 🤔

                    TAC57T 1 Reply Last reply Reply Quote 0
                    • TAC57T
                      TAC57 @stephenw10
                      last edited by TAC57

                      @stephenw10 I'm sorry but I don't understand your question. Is there a screenshot you'd like to see or some setting I can change that might solve this issue.

                      BTW I ran the dig command from a Raspberry Pi on my network:
                      crites@raspberrypi:~ $ dig +short @9.9.9.9 firmware.netgate.com
                      208.123.73.207
                      208.123.73.209

                      crites@raspberrypi:~ $ dig +short @9.9.9.9 acb.netgate.com
                      208.123.73.212

                      I have a basic homelab setup with some desktop computer, TrueNAS server running Plex, and some IOT stuff.

                      S 1 Reply Last reply Reply Quote 0
                      • S
                        SteveITS Rebel Alliance @TAC57
                        last edited by

                        @TAC57 You’ve posted DNS to third party servers works from devices on LAN but not pfSense. Which implies something is blocking it. Can you post your LAN rules and any floating rules, and routes (diagnostics menu)?

                        Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                        When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                        Upvote 👍 helpful posts!

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

                          I meant does Diag > DNS Lookup fail for any host or just firmware.netgate.com?

                          Are you running Snort or Suricata?

                          TAC57T 1 Reply Last reply Reply Quote 0
                          • TAC57T
                            TAC57 @stephenw10
                            last edited by

                            @stephenw10 Before rebooting I'd get the Unable to check for updates and DNS Lookup would not report anything from any host. On rebooting pfsense it now reports on the latest version. And DNS Lookup does report back (see below) and it reports back from google.com

                            I am running Snort.

                            31e9cab6-c456-4848-9682-f1caa3127335-image.png

                            1 Reply Last reply Reply Quote 0
                            • TAC57T
                              TAC57 @SteveITS
                              last edited by

                              @SteveITS I'm not running any floating rules. Can DM you my routes?

                              LAN rules:
                              da46e5d9-911d-4efc-87bd-eeeece0bca70-image.png

                              S 1 Reply Last reply Reply Quote 0
                              • S
                                SteveITS Rebel Alliance @TAC57
                                last edited by

                                @TAC57 and were those DNS IPs on the Snort alert page? That’s why I asked about Snort above. Reading back it sounds like a restart fixed it in January also. Restarting would empty the Snort block table.

                                Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                                When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                                Upvote 👍 helpful posts!

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

                                  Yup, disable Snort. Reboot. Retest.

                                  TAC57T 1 Reply Last reply Reply Quote 0
                                  • TAC57T
                                    TAC57 @SteveITS
                                    last edited by

                                    @SteveITS
                                    I've been running Snort forever. 😕 I'll disable it and see what happens.

                                    50ecb943-0d90-4c29-88e0-95d154455d8b-image.png

                                    1 Reply Last reply Reply Quote 0
                                    • TAC57T
                                      TAC57 @stephenw10
                                      last edited by

                                      @stephenw10 I disabled Snort, rebooted and still unable to check for updates. Also, DNS Look up doesn't return any IPs.

                                      dacac14b-69ca-4d81-be86-1fe8d819bbff-image.png

                                      ed097953-4737-47eb-acf6-e3203536a286-image.png

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

                                        Make sure the Snort block table is actually cleared, assuming you had Snort in blocking mode. Check Diag > Tables > Snort2c.

                                        Snort pulls new signatures automatically. It can start alerting/blocking things that were previously fine without warning!

                                        TAC57T 1 Reply Last reply Reply Quote 0
                                        • TAC57T
                                          TAC57 @stephenw10
                                          last edited by

                                          @stephenw10 Snort2c table is empty.

                                          I've disabled Snort and have rebooted pfsense.

                                          pfsense is still reporting 'Unable to check for updates'.

                                          Diag / DNS Lookup times out with firmware.netgate.com, google.com, 8.8.8.8. It took about 3 minutes to get the message 'Host "firmware.netgarte.com" cound not be resolved.'

                                          I can ping any of these host from a Raspberry Pi and replys.

                                          To switch from the Status / Dashboard screen to the System / Update screen takes 1.5 minutes and then about another 30 seconds to report that it's Unable to check for updates.

                                          I'm also still getting the notice "An error occurred while uploading the encrypted Netgate pfSense Plus configuration to https://acb.netgate.com/save ( Unable to resolve acb.netgate.com ) @ 2023-05-30 16:53:11"

                                          I'm running pfsense on a Zima SBC:
                                          Intel(R) Celeron(R) CPU N3450 @ 1.10GHz
                                          4 CPUs : 1 package(s) x 4 core(s)
                                          AES-NI CPU Crypto: Yes (active)
                                          IPsec-MB Crypto: Yes (inactive)
                                          QAT Crypto: No

                                          These are my installed packages / Services:
                                          d285f565-18c8-44e6-8d17-fc6275dad070-image.png

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

                                            Oh you're not using the resolver (Unbound) at all. You're using the forwarder (DNSMasq).

                                            In that as a test I would try disabling DNSMasq and enabling Unbound and see if that makes any difference. With that it should resolve directly.

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