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

    Amd64 thinks v2.4.2-p1 is latest version

    Scheduled Pinned Locked Moved General pfSense Questions
    7 Posts 3 Posters 633 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.
    • M
      markn6262
      last edited by

      Amd64 router thinks v2.4.2-p1 is latest version. Any suggestions why?

      JKnottJ 1 Reply Last reply Reply Quote 0
      • JKnottJ
        JKnott @markn6262
        last edited by

        @markn6262

        Here's what I have:

        2.4.4-RELEASE-p3 (amd64)
        built on Wed May 15 18:53:44 EDT 2019
        FreeBSD 11.2-RELEASE-p10

        PfSense running on Qotom mini PC
        i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
        UniFi AC-Lite access point

        I haven't lost my mind. It's around here...somewhere...

        M 1 Reply Last reply Reply Quote 0
        • M
          markn6262 @JKnott
          last edited by

          @JKnott Right, thats the latest update. My question is why three of four routers recognize the latest firmware but one router does not. They are all amd64 and one is an exact copy of the problem router both hardware and config. Do I have to reinstall pfsense over or is there a simple fix?

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

            Run at the command line: pkg -d update Report what errors it shows.

            It is probably unable to connect to the package repo for some reason.

            Steve

            M 1 Reply Last reply Reply Quote 0
            • M
              markn6262 @stephenw10
              last edited by

              @stephenw10 My 2.4.4 router fetches from: https://files00.netgate.com/pfSense_v2_4_4_amd64-pfSense_v2_4_4. The spare 2.4.2 router gets it from https://pkg.pfsense.org/pfSense_v2_4_2_amd64-core. How is this best corrected?

              [2.4.2-RELEASE][admin@TowerRouter.rebus]/root: pkg -d update
              DBG(1)[71891]> pkg initialized
              Updating pfSense-core repository catalogue...
              DBG(1)[71891]> PkgRepo: verifying update for pfSense-core
              pkg: Repository pfSense-core load error: access repo file(/root/var/db/pkg/repo-pfSense-core.sqlite) failed: No such file or directory
              DBG(1)[71891]> PkgRepo: need forced update of pfSense-core
              DBG(1)[71891]> Pkgrepo, begin update of '/root/var/db/pkg/repo-pfSense-core.sqlite'
              DBG(1)[71891]> Fetch: fetching from: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-core/meta.txz with opts "i"
              DBG(1)[71891]> Fetch: fetching from: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-core/meta.txz with opts "i"
              DBG(1)[71891]> Fetch: fetching from: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-core/meta.txz with opts "i"
              pkg: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-core/meta.txz: No address record
              repository pfSense-core has no meta file, using default settings
              DBG(1)[71891]> Fetch: fetching from: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-core/packagesite.txz with opts "i"
              DBG(1)[71891]> Fetch: fetching from: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-core/packagesite.txz with opts "i"
              DBG(1)[71891]> Fetch: fetching from: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-core/packagesite.txz with opts "i"
              pkg: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-core/packagesite.txz: No address record
              Unable to update repository pfSense-core
              Updating pfSense repository catalogue...
              DBG(1)[71891]> PkgRepo: verifying update for pfSense
              pkg: Repository pfSense load error: access repo file(/root/var/db/pkg/repo-pfSense.sqlite) failed: No such file or directory
              DBG(1)[71891]> PkgRepo: need forced update of pfSense
              DBG(1)[71891]> Pkgrepo, begin update of '/root/var/db/pkg/repo-pfSense.sqlite'
              DBG(1)[71891]> Fetch: fetching from: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-pfSense_v2_4_2/meta.txz with opts "i"
              DBG(1)[71891]> Fetch: fetching from: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-pfSense_v2_4_2/meta.txz with opts "i"
              DBG(1)[71891]> Fetch: fetching from: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-pfSense_v2_4_2/meta.txz with opts "i"
              pkg: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-pfSense_v2_4_2/meta.txz: No address record
              repository pfSense has no meta file, using default settings
              DBG(1)[71891]> Fetch: fetching from: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-pfSense_v2_4_2/packagesite.txz with opts "i"
              DBG(1)[71891]> Fetch: fetching from: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-pfSense_v2_4_2/packagesite.txz with opts "i"
              DBG(1)[71891]> Fetch: fetching from: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-pfSense_v2_4_2/packagesite.txz with opts "i"
              pkg: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-pfSense_v2_4_2/packagesite.txz: No address record
              Unable to update repository pfSense
              Error updating repositories!

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

                It looks like it cannot resolve the repo addresses. That's the correct repo for CE.

                Go to Diag > DNS Lookup. Can it resolve any FQDN, netgate.com for example? pkg.pfsense.org itself uses SRV records.
                https://docs.netgate.com/pfsense/en/latest/install/upgrade-troubleshooting.html?#pkg-pfsense-org-has-no-a-aaaa-record

                If it cannot resolve anything check it has a route out itself. If you use policy routing you might find clients behind the firewall have internet access but the firewall itself does not.

                Steve

                M 1 Reply Last reply Reply Quote 0
                • M
                  markn6262 @stephenw10
                  last edited by

                  @stephenw10 Turned out to be a gateway issue. Had a little trouble getting the gateway off one adapter and onto another. Wanted to create a new duplicate gateway if changes were made in the wrong order. So took a couple runs through restoring the desired config then modifying the adapter ip/gw, deleting an associated vlan, disabling monitor action, and reassigning the gateway to get update working. Confirmed in backup router that "pkg -d updates" produces the same results as the in-service router. Left the packages behind but they can be manually reinstalled easy enough. Now golden. Thanks so much Stephen for your assistance. Much appreciated.

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