Package Manager / Unable to retrieve package information.
I have 3 pfsense devices* with none that can retrieve package information.
I can successfully ping files00.netgate.com from the devices, and normal internet appears to be working fine.
The operational device is at version 2.3.4, as is unable to check for updates (I assume this is related).
The other devices are at v2.4.4 -p2.
I'm at a lost as to what to do next to get this working.
Any help is appreciated.
*(my operational router/firewall, the other 2 I'm trying to setup from fresh. One of which is going to replacing the first device.)
If you run option 13 at the command line what error do you see?
This is what i get (on the 'new') 2.4.4. device, using option 13:
Enter an option: >>> Updating repositories metadata...
dating pfSense-core repository catalogue...
pkg-static: Repository pfSense-core load error: access repo file(/var/db/pkg/repo-pfSense-core.sqlite) failed: No such file or directory
pkg-static: https://firmware.netgate.com/pkg/pfSense_factory-v2_4_4_amd64-core/meta.txz: No address record
repository pfSense-core has no meta file, using default settings
pkg-static: https://firmware.netgate.com/pkg/pfSense_factory-v2_4_4_amd64-core/packagesite.txz: No address record
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg-static: Repository pfSense load error: access repo file(/var/db/pkg/repo-pfSense.sqlite) failed: No such file or directory
pkg-static: https://firmware.netgate.com/pkg/pfSense_factory-v2_4_4_amd64-pfSense_factory-v2_4_4/meta.txz: No address record
repository pfSense has no meta file, using default settings
pkg-static: https://firmware.netgate.com/pkg/pfSense_factory-v2_4_4_amd64-pfSense_factory-v2_4_4/packagesite.txz: No address record
Unable to update repository pfSense
Error updating repositories!
Seems to be a problem resolving it. Are you using Unbound in resolving mode?
What hardware is that?
Most likely you don't have a default gateway set, or if you have one set in the config, it isn't set in the OS. Check Diagnostics > Routes and System > Routing.
To Follow Up,
Out of hours, I removed the 2.3.4, I got the new 2.4.4 device online, and everything worked. I suspect the 2.3.4 device was so screwed up somehow, that it was stopping the devices getting updates & package info.
Thanks for the assistance.