I have a dec appliance(it's a couple of years olkdd) and for some reason it is refusing to upgrade:
***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 24.1.10_8 at Sat Aug 31 09:29:01 PDT 2024
Fetching changelog information, please wait... fetch: transfer timed out
fetch: /usr/local/opnsense/changelog/changelog.txz appears to be truncated: 0/144860 bytes
Updating OPNsense repository catalogue...
Waiting for another process to update repository OPNsense
All repositories are up to date.
Checking integrity... done (0 conflicting)
Your packages are up to date.
Checking for upgrades (0 candidates): . done
Processing candidates (0 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
Any ideas?
If the appliance does not get updates, it probably lacks an internet connection, maybe because you only connected it to your LAN and WAN has no connection.
You could manually add a default gateway over your actual router.
Disable IPv6.
Quote from: meyergru on August 31, 2024, 09:32:29 PM
If the appliance does not get updates, it probably lacks an internet connection, maybe because you only connected it to your LAN and WAN has no connection.
You could manually add a default gateway over you actual router.
the appliance is in California and i am accessing it from Maryland..:)
Quote from: hescominsoon on September 01, 2024, 05:24:23 AM
Quote from: meyergru on August 31, 2024, 09:32:29 PM
If the appliance does not get updates, it probably lacks an internet connection, maybe because you only connected it to your LAN and WAN has no connection.
You could manually add a default gateway over you actual router.
the appliance is in California and i am accessing it from Maryland..:)
that's an odd fix...do i have to have ipv6 off all the time? there are several sites the client accesses that are ipv6 only...aka they do not have an ipv4 address.
It is not a fix, it is a workaround for those situations where IPv6 is not fully operational. The OS sees there's something IPv6 available and it fails to fetch the data - which is what you're seeing.
Botttom line, first you apply the updates over IPv4 (as there could be relevant IPv6 fixes there too that may apply to your ISP), then when fully up to date you reenable IPv6 and start troubleshooting if needed.