Current Base System: 2.4.5_1 Status: Up to date.
-
Thanks, here is the output from the commands above:
Shell Output - pkg-static info -x pfSense-upgrade pfSense-upgrade-0.86 ================================================= Shell Output - pkg-static clean -ay; pkg-static install -fy pkg pfSense-repo pfSense-upgrade Updating pfSense-core repository catalogue... pkg-static: https://pkg.pfsense.org/pfSense_v2_4_5_amd64-core/meta.txz: Network is unreachable repository pfSense-core has no meta file, using default settings pkg-static: https://pkg.pfsense.org/pfSense_v2_4_5_amd64-core/packagesite.txz: Network is unreachable Unable to update repository pfSense-core Updating pfSense repository catalogue... pkg-static: https://pkg.pfsense.org/pfSense_v2_4_5_amd64-pfSense_v2_4_5/meta.txz: Network is unreachable repository pfSense has no meta file, using default settings pkg-static: https://pkg.pfsense.org/pfSense_v2_4_5_amd64-pfSense_v2_4_5/packagesite.txz: Network is unreachable Unable to update repository pfSense Error updating repositories!
-
@eskild said in Current Base System: 2.4.5_1 Status: Up to date.:
pkg-static: https://pkg.pfsense.org/pfSense_v2_4_5_amd64-core/meta.txz: Network is unreachable
Yeah without internet, there can be no update!
-
@eskild said in Current Base System: 2.4.5_1 Status: Up to date.:
Network is unreachable
what do you see here?
dig @1.1.1.1 firmware.netgate.com
+++edit:
or 8.8.8.8 or 9.9.9.9 or what you want -
@jegr said in Current Base System: 2.4.5_1 Status: Up to date.:
Yeah without internet,
does the OP use the NGFW for something?
would he / she notice if there was no internet or not? -
Ran into a problem like this on an SG-1100 I was attempting to update for testing builds of Snort and Suricata on ARM hardware. This particular SG-1100 had been in storage for quite a while and still contained the 2.4.4_p2 image. When powered on, it would not show an update to either 2.4.5 nor 2.5 (21.02 for ARM appliances). No matter what I tried, it would not show an available update.
The only solution that worked was to request a current system image from Netgate Support and perform a fresh install. Since this was a testing box, I did not import a previous config and just started over from defaults.
-
@bmeeks said in Current Base System: 2.4.5_1 Status: Up to date.:
Ran into a problem like this on an SG-1100
Hi Bill,
Did you have a similar output?Network is unreachable
PS:
the current FW 2.4.5-p1 (0.86) - it looks good -
@daddygo said in Current Base System: 2.4.5_1 Status: Up to date.:
@bmeeks said in Current Base System: 2.4.5_1 Status: Up to date.:
Ran into a problem like this on an SG-1100
Hi Bill,
Did you have a similar output?Network is unreachable
PS:
the current FW 2.4.5-p1 (0.86) - it looks goodI don't recall the exact error, but
pkg
appeared to be attempting to find the repo using a bad name (or maybe a deprecated one). But yes, I did get errors on the command line when trying to runpkg-static
and other similar commands as it tried to grab the repo metadata. -
@bmeeks said in Current Base System: 2.4.5_1 Status: Up to date.:
pkg appeared to be attempting to find the repo using a bad name (or maybe a deprecated one).
perhaps the OP could see something of this from the history
cat /conf/upgrade_log.latest.txt
-
@daddygo said in Current Base System: 2.4.5_1 Status: Up to date.:
@bmeeks said in Current Base System: 2.4.5_1 Status: Up to date.:
pkg appeared to be attempting to find the repo using a bad name (or maybe a deprecated one).
perhaps the OP could see something of this from the history
cat /conf/upgrade_log.latest.txt
Some of this may also be related to the particular manner in which the pfSense/Netgate team "pulled" the update for the SG-3100. For me it was an issue only on my ARM appliance (the SG-1100). All of my x86 virtual machines can see the updates.
-
@bmeeks said in Current Base System: 2.4.5_1 Status: Up to date.:
Netgate team "pulled" the update for the SG-3100.
Yep,
I have already asked the OP (above) if it uses an SG-3100
there is no answer yet -
Thank you for all the input.
"Network is unreachable" got me thinking of the GW settings. The FW have dual WAN with policy-based routing and the default GW was set to "Automatic".
After I manually selected a WAN interface as the default gateway, the FW managed to get information about the new 2.5 version.Thanks for all the input and help!