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

    can't update pfsense or install packages

    Scheduled Pinned Locked Moved General pfSense Questions
    148 Posts 9 Posters 27.3k 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.
    • N
      nimrod
      last edited by

      I dont have any DNS servers on my WAN interface either. But i have no issues.

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

        They only show there if the WAN is being passed DNS servers by the upstream connection method. So PPPoE or DHCP usually.

        1 Reply Last reply Reply Quote 1
        • L
          Leonardo 5
          last edited by

          I did a clean install of version 2.7 (I was using 2.6), before configuring something it was already blocked.

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

            Hmm, so on a clean install you were still seeing those errors? That really does look like an upstream issue then.

            L 1 Reply Last reply Reply Quote 0
            • L
              Leonardo 5 @stephenw10
              last edited by Leonardo 5

              @stephenw10 Yes, I'm now seeing how packet capture works.

              17:01:11.934116 IP 179.16.0.4.65535 > 208.123.73.212.443: tcp 0
              17:01:12.057763 IP 208.123.73.212.443 > 179.16.0.4.65535: tcp 0
              17:01:12.057779 IP 179.16.0.4.65535 > 208.123.73.212.443: tcp 0
              17:01:12.063808 IP 179.16.0.4.65535 > 208.123.73.212.443: tcp 517
              17:01:12.185245 IP 208.123.73.212.443 > 179.16.0.4.65535: tcp 1428
              17:01:12.185262 IP 179.16.0.4.65535 > 208.123.73.212.443: tcp 0
              17:01:12.185365 IP 208.123.73.212.443 > 179.16.0.4.65535: tcp 1428
              17:01:12.185369 IP 179.16.0.4.65535 > 208.123.73.212.443: tcp 0
              17:01:12.185463 IP 208.123.73.212.443 > 179.16.0.4.65535: tcp 1240
              17:01:12.185466 IP 179.16.0.4.65535 > 208.123.73.212.443: tcp 0
              17:01:12.186727 IP 208.123.73.212.443 > 179.16.0.4.65535: tcp 1035
              17:01:12.186735 IP 179.16.0.4.65535 > 208.123.73.212.443: tcp 0
              17:01:12.187326 IP 179.16.0.4.65535 > 208.123.73.212.443: tcp 80
              17:01:12.187400 IP 179.16.0.4.65535 > 208.123.73.212.443: tcp 491
              17:01:12.303401 IP 208.123.73.212.443 > 179.16.0.4.65535: tcp 271
              17:01:12.303417 IP 179.16.0.4.65535 > 208.123.73.212.443: tcp 0
              17:01:12.303420 IP 208.123.73.212.443 > 179.16.0.4.65535: tcp 271
              17:01:12.303421 IP 179.16.0.4.65535 > 208.123.73.212.443: tcp 0
              17:01:12.306885 IP 208.123.73.212.443 > 179.16.0.4.65535: tcp 238
              17:01:12.306896 IP 179.16.0.4.65535 > 208.123.73.212.443: tcp 0
              17:01:12.306990 IP 179.16.0.4.65535 > 208.123.73.212.443: tcp 24
              17:01:12.307386 IP 179.16.0.4.65535 > 208.123.73.212.443: tcp 0
              17:01:12.321463 IP 179.16.0.4.59588 > 208.123.73.80.53: UDP, length 56
              17:01:12.321528 IP 179.16.0.4.41858 > 208.123.73.80.53: UDP, length 44
              17:01:12.423343 IP 208.123.73.212.443 > 179.16.0.4.65535: tcp 24
              17:01:12.423356 IP 179.16.0.4.65535 > 208.123.73.212.443: tcp 0
              17:01:12.423359 IP 208.123.73.212.443 > 179.16.0.4.65535: tcp 0
              17:01:12.437823 IP 208.123.73.80.53 > 179.16.0.4.59588: UDP, length 138
              17:01:12.437847 IP 208.123.73.80.53 > 179.16.0.4.41858: UDP, length 60
              17:01:12.437923 IP 179.16.0.4.60631 > 208.123.73.80.53: UDP, length 56
              17:01:12.437970 IP 179.16.0.4.64708 > 208.123.73.80.53: UDP, length 44
              17:01:12.554299 IP 208.123.73.80.53 > 179.16.0.4.64708: UDP, length 60
              17:01:12.554371 IP 208.123.73.80.53 > 179.16.0.4.60631: UDP, length 138

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

                If you set the view level higher or download that and open it in Wireshark does it show the TCP terminations or permission denied errors?

                I don't see any icmp traffic there.

                L 1 Reply Last reply Reply Quote 0
                • L
                  Leonardo 5 @stephenw10
                  last edited by Leonardo 5

                  @stephenw10 Most of the time it ends with TCP RST.
                  I executed pkg-static -d4 update and that was the result.
                  4bbd67a6-15f6-4ec0-9f0e-4afc43548099-image.png

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

                    That looks OK. What was the result of running the command?

                    1 Reply Last reply Reply Quote 0
                    • L
                      Leonardo 5
                      last edited by

                      Look how funny. I changed the DNS Resolution Behavior to "Use remote DNS Servers, ignore local DNS" and I put a totally different DNS server that I never used, 9.9.9.9. Everything is working normally. Let's see if it will be a permanent solution or the problem will come back in a while. I had never been able to reach this update stage, so it's already a step forward.
                      344449b7-67ef-46d0-a171-5882a8cd8358-image.png

                      1 Reply Last reply Reply Quote 0
                      • L
                        Leonardo 5
                        last edited by

                        The update was a success, but now pfSense is crashing on boot.
                        The same thing happened when I made the clean install of 2.7 and restored the backup (it was normal before backup).
                        I am making a clean 2.7 install again and config it from zero.

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

                          Where does it crash? Do you have a kernel panic log?

                          L 1 Reply Last reply Reply Quote 0
                          • L
                            Leonardo 5 @stephenw10
                            last edited by

                            @stephenw10 I have, but everything is working normal after I did the install from scratch. If you want me to send you the file, I can look at it. But that problem is solved now.

                            1 Reply Last reply Reply Quote 1
                            • L
                              Leonardo 5
                              last edited by

                              @mrrobot . I managed to solve the problem, but what exactly is going on? I can't say.
                              Change DNS Resolution Behavior to "Use remote DNS Servers" and put 9.9.9.9 as your first DNS server.

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